Modify

Ticket #481 (closed enhancement: fixed)

Opened 4 years ago

Last modified 4 years ago

freezing the model ordering information

Reported by: mstamat@… Owned by: andrew
Priority: minor Milestone: 0.7.2
Component: migrations Version: mercurial
Keywords: Cc:

Description

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.

Attachments

Change History

comment:1 Changed 4 years ago by andrew

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone set to 0.7.2

Fixed in [788ef3e9c20a].

View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.