Changes between Version 170 and Version 171 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Jun 30, 2008, 5:28:29 AM (16 years ago)
Author:
Malcolm Tredinnick
Comment:

Documented change to exact.

Legend:

Unmodified
Added
Removed
Modified

  • BackwardsIncompatibleChanges

    v170 v171  
    5858 * [7773] June 26, 2008 [#ChangedWhereNodeInternals Changed Where Node Internals]
    5959 * [7794] June 30, 2008 [#RemovedOrderingField Removed OrderingField]
     60 * [7798] June 30, 2008 [#ExactComparisonsRespectCaseInMySQL Exact Comparisons Respect Case In MySQL]
    6061
    6162== Database constraint names changed ==
    … …  
    625626== Removed !OrderingField ==
    626627In [7794], a model field that had no use was removed (!OrderingField). It was introduced in the magic-removal branch to support a feature that was never completed, so the code isn't useful in Django any longer.
     628
     629== Exact Comparisons Respect Case In MySQL ==
     630
     631The 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.
Back to Top