Thanks people, we have decided to go with build in migrations. Just hoping
it should not corrupt the data when there is plenty changes in schema.
--
Regards
Mukesh Yadav
mukeshyadav.com
___
BangPypers mailing list
BangPypers@python.org
https://mail.pyth
On Fri, Jan 30, 2015 at 5:09 PM, Mukesh Yadav 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
On 30 January 2015 at 17:09, Mukesh Yadav 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 ta
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
