Changes between Version 23 and Version 24 of QuerysetRefactorBranch


Ignore:
Timestamp:
06/26/2008 06:42:43 AM (7 years ago)
Author:
mtredinnick
Comment:

Removed something that was a bug, rather than a backwards-incompatible change.

Legend:

Unmodified
Added
Removed
Modified
  • QuerysetRefactorBranch

    v23 v24  
    2828
    2929=== Most visible ===
    30  * You can no longer combine a queryset created with Model.objects.none() with another created with Model.objects.filter(...) using the "|" operator.
    3130 * The {{{OneToOneField}}} class has finally been updated, as the documentation has indicated would be happening for a long while. There are few externally visible changes, with one exception: a {{{OneToOneField}}} is no longer automatically the primary key for a model that includes it. It still accepts the {{{primary_key}}} attribute, however, so you should add {{{primary_key=True}}} to the declaration of any existing {{{OneToOneField}}} instances in your code to preserve backwards compatibility.
    3231 * If you pass a bad field name into a filter or {{{order_by()}}}, Django now raises {{{FieldError}}} (from {{{django.core.exceptions}}}), rather than Python's built in {{{TypeError}}}. Also, the list of legal field names is now sorted alphabetically for easier searching. This should have no effect on most production code, however some test suites may need to be updated to accommodate the changed traceback output.
Back to Top