#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
----------------------------+------------------------------------
Changes (by tomviner):
* owner: tomviner =>
* status: assigned => new
Comment:
After [https://groups.google.com/forum/#!topic/django-
developers/7pMxh2JF1lo a discussion on django-dev] it makes sense to leave
the resolution of this issue to
[https://github.com/django/deps/blob/indexes/drafts/indexes.rst Marc
Tamlyn's Advanced indexes DEP], which he says will involve user
specified/reproducible index names, as well as index renaming.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:6>
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.03bbe1b52064cc5f06dc251a081d961c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
