#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
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ae635cc365581889454d2b3c278b3e3a38bd7809" ae635cc]:
{{{
#!CommitTicketReference repository=""
revision="ae635cc365581889454d2b3c278b3e3a38bd7809"
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.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24757#comment:9>
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.7c00b50317b1b80197b4af4952dc7592%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
