#28573: Migrations create a bad index if creating and renaming the same foreign
key
in one migration
----------------------------------+--------------------------------------
Reporter: Jerome Leclanche | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.11
Severity: Normal | Resolution: duplicate
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 Tim Graham):
* status: new => closed
* resolution: => duplicate
* type: Uncategorized => Bug
Comment:
This looks like a duplicate of #25530 which is fixed in Django 2.0. Can
you test there and if your problem isn't fixed, reopen the ticket and
include a minimal project that reproduces the problem? Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/28573#comment:3>
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/062.37221cfe3a03afeb30d653a61f09c931%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
