Changes between Version 172 and Version 173 of BackwardsIncompatibleChanges
- Timestamp:
- Jun 30, 2008, 5:49:08 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BackwardsIncompatibleChanges
v172 v173 632 632 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. 633 633 634 == BooleanFields in newforms enforce "required" ==634 == !BooleanFields in newforms enforce "required" == 635 635 636 636 In [7799], a bug was fixed that meant `required=True` is now enforced by the `newforms.BooleanField`. In this case, "required" means "must be checked" (i.e. must be True). This has been documented for quite a while, but was inadvertently not enforced by the validation code.