On Mon, Aug 24, 2015 at 10:19 PM, Emmanuelle Delescolle < [email protected]> wrote:
> I've been using this solution on a couple projects (including ones with > several children to the same migration) and have never had troubles with > the migration solver, I guess I have been lucky. > > I'll throw a sample application today and try to reproduce the problem and > see how it can be fixed/worked around. And write the appropriate tests. > > That would be great - I've not actually tried it, so you're ahead of me there, just trying to think of things that might muck it up! I don't think it's too onerous to ask people to make merge migrations (as Shai says), or to say you need to manually jiggle round dependencies if you start using migrations like this, just want to work out what our options are in this department. I'm generally not very pro having apps mess with other apps' migrations - because down that path madness lies, at least in some form - but I've also come to accept that in larger projects it becomes a necessity, be it modeltranslations (which I also disagree with the approach of), or apps that encourage extension with models, etc. I still think Django should make it quite hard to do this and screamingly obvious that you're going down a dark path, but at the same time we should at least have it be possible. Andrew -- 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/CAFwN1upGRs_W-6bPkzgV7PvBUyia8%3D4sm_hbmX8-E1ynDpRNPw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
