Ticket #269 (closed enhancement: wontfix)
Support some kind of --refresh mechanism in 'startmigration'
|Reported by:||elsdoerfer@…||Owned by:||andrew|
If find that from time to time, I make a model change while working on a commit, create (and possibly apply) the migration, only to later find out I have to further amend the change, or make another one that fits the existing migration (i.e. adding another field to a new table).
It would be convenient if there were some kind of --refresh option that would replace the currently active migration.
This could go even further and also support rollback of the migration in question, if applied (though I'm not sure how that would best be implemented, command-design wise - doing so automatically may not be a good idea).