#24357: Renaming Foreignkey field leaves index
----------------------------+--------------------
Reporter: poirier | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------
Basically, if I start with a field 'field' that is a foreign key with
db_index=True (the default), rename it to 'field2', then add a new foreign
key named 'field', executing the migration fails when it comes to adding
the new field due to a db index already existing that it's trying to
create again.
I'll attach a tarball with a minimal Django project and script to recreate
it.
I've tried this with Postgres 9.3 and Django 1.7.3 and 1.7.4.
--
Ticket URL: <https://code.djangoproject.com/ticket/24357>
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/050.769158c4d592171bb32fed257564f89b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
