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/CAAuoY6PU62d7BCvGXfFR%3D-KUBQ9tRcKVPvJ1mfdE189CTViD-Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
