> > This is not an optional contrib add-on, it's a core part of the ORM. >
There are systems where Django is not a core, but it is used as lightweight app server. Database schema migrations are created and executed in the other way.. That's why is so important to not change any database schema. > > That said, if you don't want to use migrations, you don't have to Yes, of course. But somebody can still hit <enter> after "migration" command and execute something very bad. To prevent mistakes like this I would like to disable migrations for specified databases or for whole Django-based project. > That's what setting `managed = False` on the `Meta` of all your models > will accomplish. > > Yes, I'll try this. It should help me in my case, but this is not same as bypassing migrations subsystem. Built-in migrations should be optional. 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/b8bed9c6-08a6-4607-99cb-71a93004f4cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
