Code

Changes between Version 173 and Version 174 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
06/30/08 05:53:59 (6 years ago)
Author:
mtredinnick
Comment:

Default ordering removed from User

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v173 v174  
    6060 * [7798] June 30, 2008 [#ExactComparisonsRespectCaseInMySQL Exact Comparisons Respect Case In MySQL] 
    6161 * [7799] June 30, 2008 [#BooleanFieldsinnewformsenforcerequired BooleanFields in newforms enforce "required"] 
     62 * [7806] June 30, 2008 [#DefaultUserorderingremoved Default User ordering removed] 
    6263 
    6364== Database constraint names changed == 
     
    637638 
    638639Since `required=True` is the default behaviour for all form fields, if your code does not set `required=False` on a `BooleanField` and you do not require it to be checked in the HTML form, you will need to change you form definition. 
     640 
     641== Default User ordering removed == 
     642 
     643Since the `django.contrib.auth.models.User` class frequently has a lot of rows in the database and is queried often, we have removed the default ordering on this class in [7806]. If your code requires users to be ordered by their name, you will need to manually specify `order_by('name')` in your querysets. 
     644 
     645Note that the admin interface will still behave the same as prior to this change, since it automatically orders the users by their name, just as before. So no change will be noticable there.