Changes between Version 173 and Version 174 of BackwardsIncompatibleChanges

Timestamp:

Jun 30, 2008, 7:53:59 AM (16 years ago)

Author:

Malcolm Tredinnick

Comment:

Default ordering removed from User

BackwardsIncompatibleChanges

@@ -60 +60 @@
  * [7798] June 30, 2008 [#ExactComparisonsRespectCaseInMySQL Exact Comparisons Respect Case In MySQL]
  * [7799] June 30, 2008 [#BooleanFieldsinnewformsenforcerequired BooleanFields in newforms enforce "required"]
+ * [7806] June 30, 2008 [#DefaultUserorderingremoved Default User ordering removed]
 
 == Database constraint names changed ==
@@ -637 +638 @@
 
 Since `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.
+
+== Default User ordering removed ==
+
+Since 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.
+
+Note 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.