Ticket #927 (closed enhancement: wontfix)
|Reported by:||Fred Boyle <fred@…>||Owned by:||andrew|
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.