#24972: Removing unique_together constraint makes migration fail on Django 1.8.2
with MySQL
-------------------------------------+-------------------------------------
Reporter: adambrenecki | Owner:
| adambrenecki
Type: Bug | Status: closed
Component: Migrations | Version: 1.9
Severity: Release blocker | Resolution: fixed
Keywords: | 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 adamn):
I just tried replicating and couldn't get it to happen again.
Unfortunately I fried all of my previous migrations to get it to work on
the real project and my test project starting from scratch worked fine. I
guess we'll leave well enough alone.
--
Ticket URL: <https://code.djangoproject.com/ticket/24972#comment:11>
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/070.b8cda2753736f42f16625540be72e6e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
