Changes between Version 169 and Version 170 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Jun 30, 2008, 2:11:58 AM (16 years ago)
Author:
Malcolm Tredinnick
Comment:

Noted removal of OrderingField just in case anybody was actually using it.

Legend:

Unmodified
Added
Removed
Modified

  • BackwardsIncompatibleChanges

    v169 v170  
    5757 * [7574] June 4, 2008 [#TightenedupForeignKeyassignment Tightened up ForeignKey assignment]
    5858 * [7773] June 26, 2008 [#ChangedWhereNodeInternals Changed Where Node Internals]
     59 * [7794] June 30, 2008 [#RemovedOrderingField Removed OrderingField]
    5960
    6061== Database constraint names changed ==
    … …  
    621622
    622623Again, this will not affect most code, but people writing customised things will need to adjust. Fortunately, since the list is now one component longer, if you miss a change, your code will fail drastically so you will notice.
     624
     625== Removed !OrderingField ==
     626In [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.
Back to Top