Re: South's --update equivalent for Django 1.7 migrations

Shai Berger wrote: > On Thursday 09 October 2014 09:53:44 Andrew Godwin wrote: > > > > The logic is not too complex, but the feature would need to be > > dependency-aware and delete any migrations that depended on the updated > > migration before it re-ran makemigrations; in addition, if no

Re: South's --update equivalent for Django 1.7 migrations

On Thursday 09 October 2014 09:53:44 Andrew Godwin wrote: > > The logic is not too complex, but the feature would need to be > dependency-aware and delete any migrations that depended on the updated > migration before it re-ran makemigrations; in addition, if no migration > name is provided (as

Re: South's --update equivalent for Django 1.7 migrations

Either is fine, depends on the dynamic you want to take. Direct to me will probably get more attention; I don't read -developers nearly as often as I should. Andrew On Thu, Oct 9, 2014 at 12:03 AM, Petri Lehtinen wrote: > Andrew Godwin wrote: > > --update was a feature

Re: South's --update equivalent for Django 1.7 migrations

Andrew Godwin wrote: > --update was a feature contributed to South that I didn't write, but pulled in > and everyone found useful; I didn't get it in for the 1.7 release as there > were > time constraints, but I'd definitely be open to seeing it re-added. > > The logic is not too complex, but

Re: South's --update equivalent for Django 1.7 migrations

--update was a feature contributed to South that I didn't write, but pulled in and everyone found useful; I didn't get it in for the 1.7 release as there were time constraints, but I'd definitely be open to seeing it re-added. The logic is not too complex, but the feature would need to be