#24972: Removing unique_together constraint makes migration fail on Django 1.8.2
with MySQL
---------------------------------+----------------------------------------
Reporter: adambrenecki | Owner: adambrenecki
Type: Bug | Status: assigned
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+----------------------------------------
Changes (by adambrenecki):
* has_patch: 0 => 1
Comment:
OK, patch is here: https://github.com/django/django/pull/4859
Sorry it took so long; I had issues with djangocore-box on Friday and
didn't have time over the weekend :(
--
Ticket URL: <https://code.djangoproject.com/ticket/24972#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/070.ebc279c1622a61e8f2b756a84c4e88ba%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
