#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 timgraham):
Okay with me, although it would be nice to also recommend a solution for
users who have already created their schema with the current code and run
into this error.
--
Ticket URL: <https://code.djangoproject.com/ticket/24757#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.4be8f4e6f7553e6aa4b23bcdfc3f3819%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
