#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:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Made some minor edits and now running tests locally just to double check.

--
Ticket URL: <https://code.djangoproject.com/ticket/24972#comment:6>
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.b4b4def8f008a4e562713c6f8d290647%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to