Tim, I've just realised that there is no sql* commands in the newest Django. Generating SQL from models was very useful. Why do you decided to drop that functionality? Because of builit-in migrations? Can you just bring them back?
Thanks. Marcin. On Friday, May 29, 2015 at 7:26:26 PM UTC+2, Marcin Nowak wrote: > > Thanks, I didn't saw it. > > But I've found quick&dirty ad-hoc solution using monkey patching. > Just include this snippet in project`s __init__: > > from django.core.management import sql > > def check_for_migrations_bypassed(*args, **kw): > pass > > sql.check_for_migrations = check_for_migration_bypassed > > (Tested with v1.8) > > /BR > Marcin > > On Friday, May 29, 2015 at 6:38:11 PM UTC+2, Tim Graham wrote: >> >> There's a ticket waiting someone to implement what has been discussed: >> >> https://code.djangoproject.com/ticket/24481 >> >> On Friday, May 29, 2015 at 12:05:48 PM UTC-4, Marcin Nowak wrote: >>> >>> >>> >>> On Monday, March 30, 2015 at 1:58:02 AM UTC+2, Russell Keith-Magee wrote: >>>> >>>> >>>>> >>>>> *What is the new way to dump the sql schema of currently installed >>>>> django appz ?* It'd maybe be worth that I provide a doc patch to >>>>> inform users about it. >>>>> *If there is none, is there an agreement to restore at least sqlall >>>>> and sqlclear ?* >>>>> >>>> >>>> No, there isn't :-) >>>> >>> >>> We need old sql /sqlall behaviour. Currently we can't generate sql for >>> contrib apps. >>> Calling `sql auth` raises error: >>> >>> CommandError: App 'auth' has migrations. Only the sqlmigrate and >>> sqlflush commands can be used when an app has migrations. >>> >>> We're expecting SQL output instead. >>> >>> *We need to bypass migration mechanism for some specific projects*. >>> Please make life easier but not harder. Django is unusable from v1.7 for >>> some of us! >>> >>> Or please give us hint how to achieve old behaviour. >>> >>> /BR >>> 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ee82af74-ee72-4dbc-aa21-79070bcc4f79%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
