#24757: Removing unique_together constraint make Django 1.8 migration fail with
MySQL
-------------------------------------+-------------------------------------
Reporter: trecouvr | Owner: timgraham
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution: fixed
Keywords: migrations mysql | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>):
In [changeset:"6a0d9f068f9986c8c05e689e67be7bc22c59efc6" 6a0d9f0]:
{{{
#!CommitTicketReference repository=""
revision="6a0d9f068f9986c8c05e689e67be7bc22c59efc6"
[1.8.x] Fixed #24757 -- Recreated MySQL index when needed during combined
index removal
Thanks Thomas Recouvreux for the report and Tim Graham for the tests and
review.
Backport of ae635cc36 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24757#comment:10>
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/066.990e4b7f22798402fb163b18294c4bb0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
