Changes between Version 121 and Version 122 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
09/06/2007 11:19:53 PM (7 years ago)
Author:
gwilson
Comment:

Added note about removing of order_by() in archive_year, [6057].

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v121 v122  
    3535 * [5898] Aug. 16, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Changestomanagement.pycommands Changes to management.py commands ]
    3636 * (Multiple) Aug. 19, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Refactoreddatabasebackends Refactored database backends]
     37 * [6057] Sept. 6, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#archive_yeargenericviewnolongerperformsanorder_byonthepassedqueryset archive_year generic view no longer performs an order_by() on the passed queryset]
    3738
    3839
     
    356357|| {{{django.db.backend.uses_case_insensitive_names}}} || {{{django.db.connection.features.uses_case_insensitive_names}}} ||
    357358|| {{{django.db.backend.uses_custom_queryset}}}    || {{{django.db.connection.features.uses_custom_queryset}}} ||
     359
     360== archive_year generic view no longer performs an order_by() on the passed queryset ==
     361
     362For consistancy with the other date-based generic views, `archive_year` was changed to not perform an `order_by()` on the passed queryset.  Update your code by performing an explicit `order_by()` on the queryset you pass to `archive_year` or add an `ordering` option to your model's `class Meta`.
Back to Top