#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: closed
Component: Migrations | Version: 3.1
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: assigned => closed
* resolution: => duplicate
Comment:
OK, given Simon ans Mariusz' comments lets take this as a duplicate of
#31700 and aim to provide a better warning for this kind of case.
--
Ticket URL: <https://code.djangoproject.com/ticket/32206#comment:7>
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.941b2a209c09360d4d3105c91e695f11%40djangoproject.com.
