I have to admit I don't know the ins and outs of the new migration system in django1.7+, and I don't quite understand why it fails to handle circular dependencies which the old fashioned syncdb does. I would love to hear an explanation, but my main question is:
I*f the initial syncdb is actually capable of creating the database for the models despite of the circular dependencies, why not base the migrating mechanism simply on some kind of DIFF between the existing database and the one that would have been created by syncdb for the newly changed models?* -- 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/cef5b6e4-9f2e-4c81-aaee-0eede10d55b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
