#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 Mikko Ahonen):
Run into this as well, using django 3.1 and Postgres. Similar case as for
scholtalbers.
I wanted to switch to using a library that wanted to add field to model
which was conflicting with the existing name, used for similar purpose
(parent).
I renamed the field (to old_parent), ran migration, created migration,
added the library (which added the parent field), created migration, run
migration.
Locally migrations worked because I was using SQLite, but when installing
on staging it failed because of conflicting index name.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:33>
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/01070184f4447718-6f4b218c-873f-41b2-81c5-fe962b5dd944-000000%40eu-central-1.amazonses.com.
