On 25 August 2015 at 16:21, Tim Graham <timograham@gmail.com> 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.
BR,
Marcin
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CAB2m7CxBWsouYWmASv1gXQ%3DHyyqjnNenspkztv%3Dzv_f4P0uuZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment