#22275: unique_together with foreign keys fails migration ---------------------------------+------------------------------------ Reporter: ryanhiebert | Owner: bak1an Type: Bug | Status: assigned Component: Migrations | Version: master Severity: Release blocker | Resolution: Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 1 Easy pickings: 0 | UI/UX: 0 ---------------------------------+------------------------------------
Comment (by andrewgodwin): It looks good enough to me; the optimisation of where to put it can be addressed along with the same optimisation for ForeignKeys (it currently errs a bit on the "splitting up" side), but in the interest of getting the beta out I'm committing it right now, as it fixes the bug. -- Ticket URL: <https://code.djangoproject.com/ticket/22275#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/069.f68cfe91318eab51205bbbae8ec5f34b%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.