On Sun, Mar 29, 2015 at 4:57 PM, Russell Keith-Magee <russ...@keith-magee.com> wrote: > It would probably be *possible* to refactor manage.py sqlall to use the new > table creation logic; but the question would then be "why do you want it"?
Speaking from experience, I have found these commands to be a extremely helpful when migrating a legacy application to Django. In my situation, the legacy application would do whatever it wanted with the schema and was not very opinionated nor well maintained. When moving to Django having a quick way to dump Django's *ideal* SQL representation was a very useful way to debug what needed to change in the legacy application. There may even be a interim where SQL migrations are handled outside Django but with the goal of moving towards Django's representation. Having a way to diff actual vs expected is very useful for this situation. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/CADhq2b5x66TN1mky3PoZoJNd78RtVA0ee951kd7_k4Qy%3DVPHHg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
