>
> I'm also thinking it might be much helpful to detect the rename as much as
> possible and give warning message about developer has to modify the
> migration to rename field properly
>
sure, but how would you do this? And how would you cover all the possible
cases to detect whether the dev
On Sunday, September 9, 2018 at 12:48:52 AM UTC+8, Jason wrote:
>
> https://docs.djangoproject.com/en/1.11/ref/migration-operations/#alterfield
>
> There are AlterField and RenameField operations available with migrations,
> but you probably have to include them in your custom migrations. Reaso
https://docs.djangoproject.com/en/1.11/ref/migration-operations/#alterfield
There are AlterField and RenameField operations available with migrations,
but you probably have to include them in your custom migrations. Reason
being, how would django know that you're just renaming a field and not
Hi,
I have a model which contains a BooleanField. I changed its name to a new
one and updated help text as well. django generates operations RemoveField
and AddField in sequence for those changes. As a result of running this
migration, original data is lost. I was confused by this behavior why
4 matches
Mail list logo
