On Apr 27, 2015, at 7:01 PM, Mike Dewhirst <[email protected]> wrote: > >> On 27/04/2015 9:54 AM, [email protected] wrote: >> So what about that? I'm also interested in disabling migrations. > > Would it suffice to have all your models specify "managed = False" in the > Meta class? > > https://docs.djangoproject.com/en/1.7/ref/models/options/#managed
This is why top posting or at least failing to trim is bad for (at least) technical mailing lists. Threads end up looping. >From the very email quoted: >> On Saturday, September 20, 2014 at 6:37:59 AM UTC+2, Anthony Tuininga wrote: >> >> Hmm, the problem is that there doesn't appear to be any way to turn >> off the creation of the migrations table itself, even if all of the >> other models are set to managed=False as suggested by Nikolas. I've >> commented it out for now but it would be ideal to have some way of >> turning it off completely -- or simply doing nothing if there are no >> managed models. -- 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/64EF1371-9C9B-45DF-8161-37FE05A5BB44%40gmail.com. For more options, visit https://groups.google.com/d/optout.
