#23577: CREATE INDEX-related OperationalError on migrating renamed models with
colliding field names
----------------------------+--------------------------------------
Reporter: CrimsonZen | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by CrimsonZen):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
It is worth noting that if you use postgres instead, the error is
`django.db.utils.ProgrammingError: relation "sample_foo_4350f7d0" already
exists`.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:1>
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.4acb0d9f519adf249bf2d1601baa3a9e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
