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 to how makemigrations runs by default), the strategy > might change a bit. > There are a few other minor complications; for example, the script suggested might fail if the last migration depended on more than one migration in the local app (which naturally happens if you needed "makemigrations --merge").
Also, I'd be quite apprehensive about updating migrations which have dependents. It seems like a high potential for breakage. Shai. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/201410100733.14364.shai%40platonix.com. For more options, visit https://groups.google.com/d/optout.
