So what about that? I'm also interested in disabling migrations. I need to upgrade Django in big project (from 1.4 to newer version) because of lack of support for 1.4, but migrations included in v1.7 will complicate this process.
I want to disable everything related to migrations. We're using better migration solution, which is project-wide and related only to databases. Django is a only small part of the project and it should not modify any table and any record outside our migrations system. /BR Marcin 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. > > On Thursday, September 18, 2014 5:27:45 PM UTC-6, mike wrote: >> >> Hi, >> >> I feel your pain, but I think you can utilize something with --fake >> >> I have been using databases for many, many years, and honestly- >> migrations definitely make sense. I am able to add new fields within a >> few seconds without having to do any extra work. It takes 2 minutes to >> learn how to use migrations, and I will personally never look back. >> >> Mike >> >> >> >> On Thu, Sep 18, 2014 at 5:04 PM, Anthony Tuininga >> <[email protected]> wrote: >> > Hi, >> > >> > I just upgraded my test environment to Django 1.7 and immediately >> noticed >> > that mgirations appear to be a requirement. Searching the documentation >> and >> > the code itself seems to indicate that there is no way to disable it, >> > either. Did I miss something? I don't need or want Django to create or >> alter >> > any database objects and up to Django 1.6 I could quite happily ignore >> > syncdb but it seems I can't ignore migrations. Please advise! Thanks. >> > >> > Anthony >> > >> > -- >> > 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/9bdd258f-a21b-48a0-ab1b-b3a4123b40c1%40googlegroups.com. >> >> >> > For more options, visit https://groups.google.com/d/optout. >> > -- 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/1f03aaad-1beb-4b84-9ca3-c1ce097ad0ca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
