Changes between Version 233 and Version 234 of BackwardsIncompatibleChanges

Timestamp:

Aug 12, 2008, 3:02:11 AM (16 years ago)

Author:

Malcolm Tredinnick

Comment:

Changed "exact" filtering on MySQL (again)

BackwardsIncompatibleChanges

@@ -66 +66 @@
  * [8143] July 30, 2008 [#DecimalFieldconversiontightened DecimalField conversion tightened]
  * [8162] July 30, 2008 [#Passwordresetsystemchangedtoimprovesecurityandusability  Password reset system changed to improve security and usability ]
- * [8191] Aug. 1, 2008 [#Removedseveraldeprecatedfeaturesfor1.0 Removed several deprecated features for 1.0]
- * [8202] Aug. 3, 2008 [#Removeddictionaryaccesstorequestobject Removed dictionary access to request object]
- * [8211] Aug. 5, 2008 [#urltagnowallowsNoReverseMatchexceptionstopropagate url tag now allows !NoReverseMatch exceptions to propagate]                 
+ * [8191] Aug 1, 2008 [#Removedseveraldeprecatedfeaturesfor1.0 Removed several deprecated features for 1.0]
+ * [8202] Aug 3, 2008 [#Removeddictionaryaccesstorequestobject Removed dictionary access to request object]
+ * [8211] Aug 5, 2008 [#urltagnowallowsNoReverseMatchexceptionstopropagate url tag now allows !NoReverseMatch exceptions to propagate]                 
  * [8223] Aug 6, 2008 [#Signalrefactoring Signal/dispatch refactoring]
  * [8230] Aug 8, 2008 [#Peruvianlocalflavorchange Peruvian localflavor change]
  * [8244] Aug 8, 2008 [#Filestoragerefactoring File storage refactoring]
  * [8273] Aug 9, 2008 [#save_addandsave_changeRemovedfromModelAdmin save_add and save_change Removed from ModelAdmin]
- * [8291] Aug. 10, 2008 [#Removedseveralmoredeprecatedfeaturesfor1.0 Removed several more deprecated features for 1.0]
- * [8296] Aug. 11, 2008 [#RefactoredtheCreationandIntrospectionmodulesofthedatabasebackends Refactored the Creation and Introspection modules of the database backends]
+ * [8291] Aug 10, 2008 [#Removedseveralmoredeprecatedfeaturesfor1.0 Removed several more deprecated features for 1.0]
+ * [8296] Aug 11, 2008 [#RefactoredtheCreationandIntrospectionmodulesofthedatabasebackends Refactored the Creation and Introspection modules of the database backends]
+ * [8319] Aug 12, 2008 [#RestoredearlierexactmatchingforMySQL Restored earlier exact matching for MySQL]
 
 == Changed 'spaceless' template tag to remove all spaces ==
@@ -601 +602 @@
 == Exact Comparisons Respect Case In MySQL ==
 
+**This change is no longer applicable. See [#RestoredearlierexactmatchingforMySQL below] for details on when it was changed back.**
+
 The documented behaviour of the `__exact` comparison in Django's ORM is that it is case-sensitive. For case-insensitive searches, there is `__iexact`. On some MySQL installations (which includes most default installations), `__exact` was using case-''in''sensitive matching. This was changed in [7798] so that using `__exact` will respect the case of the argument, bringing it into line with all the other database backends.
 
@@ -1153 +1156 @@
 Lastly, any user that is maintaining an external database backend will need to update their code to use the new interface. The new class-based approach should make backend development much easier, as common behavior can be inherited from the base classes in django.db.backends; only database-specific behavior should require implementation.
 
+== Restored earlier exact matching for MySQL ==
+For MySQL users only: Due to a number of unintended side-effects and after carefully considering the alternatives, the changes from [7798] were reverted in [8319]. Thus, `__exact` filters in MySQL now use the database table's native collation setting to determine whether the match is case-sensitive or case-insensitive.
+
+[http://www.djangoproject.com/documentation/db-api/#exact The documentation] for `exact` has been updated to indicate how to control this behaviour.