#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 evenicoulddoit):
I tried to migrate to a new model and bumped into this one. To fix, I made
sure that I renamed my existing model to "old" first (e.g.
Model->ModelOld), create the new model with the previous name (e.g.
Model), migrate the data and then remove the old model. My previous
strategy of creating the new table migrating the data and then renaming it
broke due to the index issues.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.c4069abc15582ececfa8b942ff0b2114%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
