On 08/25/2015 08:42 AM, Marcin Nowak wrote: > > On 25 August 2015 at 16:21, Tim Graham <[email protected] > <mailto:[email protected]>> wrote: > > What does "turning off migrations" mean in practice? Is it not > enough to avoid the makemigrations and migrate management commands? > > > > Currently I'm replacing mgmt commands to avoid accidential calls, and > also replacing test runner. But, for example, `runserver` complains > about unapplied migrations (which is not true), and I don't know what > else and when other db alterations can be executed. > > "Global turn off" should give us assurance that nothing would be changed > in db automatically.
I thought we already covered this topic, and `managed=False` should work for your use case. That's the exact meaning of this flag: "I don't want Django to manage my database, please never touch it." Have you tried adding that flag to your models? Does something about that not work for you? Carl -- You received this message because you are subscribed to the Google Groups "Django users" 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-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/55DC817D.6070905%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
