On Tuesday, December 16, 2014 1:49:53 PM UTC+1, Andrew Godwin wrote: > > > Also bear in mind that, by doing your own schema management for the > contrib apps, you're kind of implicitly forking the schema; Django 1.8 will > ship with some migrations for these apps, and you're going to have to make > sure you manage those yourself and keep the database in sync with the code > (though of course the release notes will mention this kind of thing). >
Yes, I'm aware of that, and I want to control every schema change (this is specific requirement for this project) > > If you want to stub out migration operations, you can just make a custom > database backend that inherits from the one you use and define a new > SchemaEditor subclass with an execute() function that does nothing; that > should accomplish what you want. > Thanks! I will try this approach. > Alternatively, you could wrap all migration operations into the State side > of SeparateDatabaseAndState, but that's a bit cumbersome. > For this I need to do some research. Thanks for tips! As far as I can tell your only issue is the runserver warning that you > have unmigrated changes, which there's currently no plan to be able to > disable. I would like to bypass migrations to prevent accidental execution of `migrate` command, too. Generally speaking - I don't need builtin migrations (because executing them in my environment may be dangerous), but I need newer versions of Django. I will try your tips. Kind Regards, 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 [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/39e390e6-16a3-4591-8831-e73f281e615f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
