#23577: CREATE INDEX-related OperationalError on migrating renamed models with
colliding field names
----------------------------+------------------------------------
Reporter: CrimsonZen | Owner:
Type: Bug | Status: new
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 lwm):
Replying to [comment:8 ris]:
> Replying to [comment:4 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.
>
> FWIW I have worked around this in my migrations by doing two
AlterFields, dropping & re-creating the index by doing db_index=False then
db_index=True.
Confirmed. This worked for me also. I can use `manage.py sqlmigrate <app>
<migration>` to see which indexes are giving me conflicts (should be the
same as the error you get when you try to run migrate) and then used the
`db_index=False/True` trick with `AlterField`.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:11>
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.7ccda12942a9e5f514c66cb573986e7f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
