Well this is what we call as the downtime.
On Tuesday, 2 October 2018 06:17:10 UTC+5:30, martin_x wrote:
>
> Hi there,
>
> Thanks for making Django a great framework for starters :D
>
> Recently my team have run into problems when trying to remove a database
> column from the model without
>
> Won’t generate migration file, which means database wise, nothing has
> changed
>
You are the one generating migration files, Django is not forcing them.
The problem is not in Django, the problem is that this cannot be solved
with a single deploy, there is not way for the old code to know
On 10/02/2018 09:42 AM, martin_x wrote:
Hi there,
Thanks for making Django a great framework for starters :D
Recently my team have run into problems when trying to remove a database
column from the model without stopping our Django server, below is the
timeline:
There have been processes
Hello,
I don't think this is something Django can or should handle. You need to
make your change in smaller increments so it doesn't break.
The proper forum for discussing this is the Django users list (or IRC or
Google...).
Good luck!
Tobias
On Mon, Oct 1, 2018, 8:47 PM martin_x wrote:
>
Hi there,
Thanks for making Django a great framework for starters :D
Recently my team have run into problems when trying to remove a database
column from the model without stopping our Django server, below is the
timeline:
1. Before migration happens, we have column_A we want to remove, and
