On 9 בספטמבר 2015 13:29:58 GMT+03:00, Marten Kenbeek <[email protected]> wrote: > >> >> The order of migrations isn't something which is local to this >feature, it >> is something which isn't fixed (probably by design, correct me if I'm > >> wrong) and if it is not "the right way" to do it, maybe it should be >part >> of another issue. > > >The order of migrations within a single app is fixed.
No, actually it isn't. It is only constrained by dependencies. Merge migrations do not fix it either. The only thing they do is tell the warning-happy migration system : "yes, I have considered the situation here and it's OK to run these two migrations in either order ". Which raises two points : First, can we (do we want to ) handle this validation some other way, and would it buy us anything? Second, how common is Marten's misconception? Do we need to address it? Shai -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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/ADF331E4-8B2C-4F39-9AD4-5DEA0ECA5D74%40platonix.com. For more options, visit https://groups.google.com/d/optout.
