#23577: Rename operations should rename indexes, constraints, sequences and
triggers named after their former value
---------------------------------+------------------------------------
Reporter: Chris Woytowitz | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Jef D):
Just opened this issue: https://code.djangoproject.com/ticket/33488#ticket
which was apparently a duplicate of this one. I did a rename and quickly
after I reused the old name of the field which made this very visible.
However, I can imagine that it is a difficult error to find when it
happens with longer periods in between. The longer a project lasts, the
more likely it is that one will run into this kind of issues.
Unfortunately, the issue doesn't seem to have a high priority given that
it has been 7 years since it was opened. For now I will sandwich the
rename migration with unsetting and setting the index in two additional
migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:31>
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/068.6a07f3253ca6ae56c99e1aff33d0db3c%40djangoproject.com.
