Changes between Version 209 and Version 210 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
08/05/08 18:48:01 (7 years ago)
Author:
trevor
Comment:

added entry to table of contents

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v209 v210  
    6969 * [7971] July 18, 2008 [#Movednewformstoforms Moved django.newforms to django.forms]
    7070 * [8015] July 19, 2008 [#ChangedthewayURLpathsaredetermined Changed the way URL paths are determined]
     71 * [8131] July 29, 2008 [#intfield__infilterlookupsnolongerwork intfield__in=('',) filter lookups no longer work]
    7172 * [8143] July 30, 2008 [#DecimalFieldconversiontightened DecimalField conversion tightened]
    7273 * [8162] July 30, 2008 [#Passwordresetsystemchangedtoimprovesecurityandusability  Password reset system changed to improve security and usability ]
     
    583584obj = MyObj.objects.get(pk=1)
    584585form = MyForm(instance=obj)
     586
     587
     588
    585589}}}
    586590
     
    876880# NEW:
    877881# in admin.py
     882
     883
    878884
    879885
     
    1048105425 special cases for each webserver and installation possibility).
    10491055
     1056== `intfield__in=['']` filter lookups no longer work ==
     1057
     1058Before [8131], `MyModel.objects.filter(intfield__in=[''])` would return an empty `QuerySet`, where `intfield` represents an `IntegerField` or similar on `MyModel`. For example, if you had been unpacking a comma-separated list of IDs into a lookup such as:
     1059{{{
     1060#!python
     1061authors = Author.objects.filter(id__in=author_ids.split(','))
     1062}}}
     1063then your lookup will fail if author_ids is an empty string, as of [8131].
     1064
    10501065== !DecimalField conversion tightened ==
    10511066
     
    10781093
    10791094Previously !NoReverseMatch exceptions were silenced in the `{% url %}` tag.  This is very rarely useful, and usually just produced difficult to find bugs, and so was changed in [8211].  See #8031.
    1080 
    1081 == `intfield__in=['']` filter lookups no longer work ==
    1082 
    1083 Before [8131], `MyModel.objects.filter(intfield__in=[''])` would return an empty `QuerySet`, where `intfield` represents an `IntegerField` or similar on `MyModel`. For example, if you had been unpacking a comma-separated list of IDs into a lookup such as:
    1084 {{{
    1085 #!python
    1086 authors = Author.objects.filter(id__in=author_ids.split(','))
    1087 }}}
    1088 then your lookup will fail if author_ids is an empty string, as of [8131].
Back to Top