On 30 January 2015 at 17:09, Mukesh Yadav <mak....@gmail.com> wrote: > > Hi, > I recently moved my office one of the app to Django. Now its time for > this to go live. While development we faced many problems in terms of > conflicts in migrations file of Django. Due to this I'm not confident that > django should take control of database (migrate and makemigrations command) > on live server.
Would strongly recommend using migrations, rather than changing the schema manually. I presume that you are using the built-in support for migrations with Django 1.7. You do not explain details of the issues that you faced with using migrations, so it is difficult to comment further, but manual schema changes are more prone to errors. Have not yet had occasion to use Django 1.7's migrations, but South has been part of our Django setup for quite some time, and we have not faced significant issues with it besides glitches when support for a custom user was added to Django. Regards, Gora _______________________________________________ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
