Ticket #568 (closed enhancement: wontfix)

Opened 5 years ago

Last modified 5 years ago

maintain project-wide viable 'order of migrations' file

Reported by: forensic7278@… Owned by: andrew
Priority: major Milestone: 0.7.3
Component: commands Version: unknown
Keywords: project-wide Cc:


a file like this would be useful outside of the database's schemamigrationhistory logs, as it would transfer easier from environment to environment (i.e. from dev to staging to production). it would be a good reference for when you have to figure out how to rebuild the database to where it's at on perhaps a different database, and all you have is the order of migrations per application. Also/alternatively, is there any way to output the schemamigrationhistory in a readable format?

Change History

comment:1 Changed 5 years ago by andrew

  • Status changed from new to closed
  • Resolution set to wontfix
  • Milestone set to 0.7.3

Migration order is already fixed - it's ascii sort order inside apps on migration filenames, and then the dependencies between apps are used to linearise it into one big global history. I don't see what the advantage of a new place to put ordering is, especially when it's tied to the project and thus quite fragile.

You can see what's been applied and what exists with "./manage.py migrate --list" - there's no view that shows you that with timestamps, however.

Note: See TracTickets for help on using tickets.