Hi, I have a working set of squashed migrations for my program that consists of some 15 applications. The old migration set works fine. The newly created squashed migrations work fine. But when I keep them together (as required for deployment), I run into circular dependency problems when running 'migrate'.
My guess is that the manage 'migrate' command considers all the OLD dependencies. It should of course decide which initial migration it will apply per application and then only look at the dependencies for those migrations. I am worried it considers the old migrations. I have a work-around, but this could be an improvement to Django (using 3.0). Ramon -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/0b103211-b4c2-4866-92c2-c341de46bce6n%40googlegroups.com.
