#23577: CREATE INDEX-related OperationalError on migrating renamed models with
colliding field names
----------------------------+------------------------------------
Reporter: CrimsonZen | Owner: tomviner
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7
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 tomviner):
I've found an associated case where a field with {{{db_index=True}}}, is
renamed, and another db_indexed field created with the original's name.
Just discussed this with @andrewgodwin, I've agreed to write a test case
for the field rename case, and then post about a solution on django-dev,
with his preference being to make index names randomised.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.71c7afb6862515276e71d3866f84b988%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
