#24757: Removing unique_together constraint make Django 1.8 migration fail with
MySQL
----------------------------------+-------------------------------------
Reporter: trecouvr | Owner: timgraham
Type: Bug | Status: assigned
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution:
Keywords: migrations mysql | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+-------------------------------------
Comment (by claudep):
Wow, MySQL awesomeness!
Read http://bugs.mysql.com/bug.php?id=37910
So we have now the choice of reverting [2ceb10f3b02cbeb] and accepting
that some indexes are duplicated, or try to be clever and recreate
"implicit" indexes when dropping other indexes. Frankly, I now tend to
choose the revert!
--
Ticket URL: <https://code.djangoproject.com/ticket/24757#comment:4>
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.777b63087999ceaf5f4e6cd3ef7ea4de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
