#35176: Renaming a field and its verbose name results in deleting and
recreating a
new column in django 4.2
----------------------------------+--------------------------------------
Reporter: Corentin Bettiol | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 4.2
Severity: Normal | Resolution:
Keywords: rename, renaming | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by Corentin Bettiol):
* Attachment "0003_remove_mymodel_another_field_and_more.py" added.
Nonworking migration: the field "another_field" was deleted, and a new
field named "another_field_renamed" was created. Only difference with the
previous migration is that the verbose_name of the field also changed.
--
Ticket URL: <https://code.djangoproject.com/ticket/35176>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d885897ba-0b8f850b-a1be-44eb-a6c3-2c9596bb8d99-000000%40eu-central-1.amazonses.com.
