#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 added a schema test case:
https://github.com/tomviner/django/compare/ticket/23577
This should currently fail on all backends except sqlite (which doesn't
rename fields - it drop/creates the whole table). When this bug is fixed,
it should pass for all backends, for that reason I haven't added any
unittest.skip decorator.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:5>
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.0987b77a13b7faa587861656df99fc67%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
