Marcin, what are you hoping to accomplish with your latest mail? As Aymeric said in another thread, repeated complaining is not going to help. There's already an accepted ticket for this feature. If you want to be productive and helpful, pick up Andrew's patch and try to complete it. Alternatively, if the business needs justify it, you could offer to pay someone to implement it if that suits you better. Tim
On Tuesday, June 21, 2016 at 8:39:54 AM UTC-4, Marcin Nowak wrote: > > > > On Monday, June 1, 2015 at 5:11:27 PM UTC+2, Andrew Godwin wrote: >> >> OK, so I've just gone ahead and done the initial work on this: >> https://github.com/django/django/pull/4729 >> >> > They shot not only in my head - > http://stackoverflow.com/questions/35455706/equivalent-of-sqlall-in-django-1-9 > > Generating sql from migrations is useful for translating python migrations > into SQL (the only one good way to handle database schema). > But old `sql` command generates SQL directly from models, so an > application must not have new migrations defined. > > The old-style commands are still required. I heard from my fellows that > they are downgrading their projects from Django 1.9 to 1.8 due to missing > sql commands. Not so funny. > > Marcin > -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c8591966-f49c-47ed-8cd1-82fcb74a360d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
