Ticket #927 (closed enhancement: wontfix)

Opened 4 years ago

Last modified 4 years ago

Migration groups/series

Reported by: Fred Boyle <fred@…> Owned by: andrew
Priority: major Milestone:
Component: migrations Version: 0.7.3
Keywords: Cc:


The ability to group migrations in separate series would be great. This would help avoid conflicting migration numbers in an app when multiple devs are working on the same app.

App has two major model groups, Game + Player. Each Game may have related models as will Player.

Dev 1 works on Game and it's models. Would be great if dev 1 could do:
schemamigrations --auto app_name/group_name
schemamigrations --auto app_name --group=group_name

This would create a migration series of group_name with it's own numbering sequence preventing any collisions with any migrations for group_name2 (Player models).

Big benefit for teams working together and keeping things separate and clean.

Change History

comment:1 Changed 4 years ago by andrew

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

I'm not sure this is easily possible - South is entirely written on a per-app basis, and it assumes that each app has all of its model data present in each migration. To change that would be a massive effort, all for saving a little bit of developer coordination - something you'd still need if these "groups" had things like ForeignKeys? which spanned multiple groups.

I'm afraid I'm going to WONTFIX this, on the basis that it's changing what South _is_ fundamentally - if you want separate migration series for different models, they should probably be different apps.

Note: See TracTickets for help on using tickets.