#32206: Incorrect migration generated if field has been renamed when it has
verbose_name set
-------------------------------------+-------------------------------------
Reporter: Peter Inglesby | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: assigned
Component: Migrations | Version: 3.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hi All — thanks for the input.
Can I ask, can we **warn** in these kind of cases somehow?
So, a user **should** do it in two steps, and users **should** review
generated migrations to make sure the operations are what's required, but
I think this probably counts as a loaded foot-gun.
Perhaps we should re-open #31700 which suggested adding additional output
for destructive operations? (Mailing list summary there was "Yes, maybe
something at the `makemigrations` stage...) — What do we think? (Thanks!)
--
Ticket URL: <https://code.djangoproject.com/ticket/32206#comment:6>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.0643fadce66117105e4a4b3dbaf8607d%40djangoproject.com.
