Ticket #481 (closed enhancement: fixed)
freezing the model ordering information
|Reported by:||mstamat@…||Owned by:||andrew|
I noticed that South does not freeze the ordering information for the models (i.e. the 'ordering' attribute of the 'Meta' inner class of each model)
This shouldn't cause any problems or undetected data corruption. But it still is quite confusing and counter-intuitive, because a loop on the frozen model in the migration code will return the objects in different order than the equivalent loop in the application code.