#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 scholtalbers):
Encountered this (django 3.2) when trying to add a field with the same
name of a field I renamed in a few migrations before. The original index
is still existing. It should have been renamed as part of the AlterField
migration.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:32>
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/0107018437e17f8e-a0426515-d170-447b-8d5f-eb77373f52a7-000000%40eu-central-1.amazonses.com.
