#26149: Invalid migration generated when using order_with_respect_to and a unique_together constraint ----------------------------+-------------------------------------- Reporter: richardxia | Owner: anabelensc Type: Bug | Status: assigned Component: Migrations | Version: 1.9 Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 1 Easy pickings: 0 | UI/UX: 0 ----------------------------+-------------------------------------- Changes (by timgraham):
* needs_better_patch: 0 => 1 * needs_tests: 1 => 0 Comment: [https://github.com/django/django/pull/7053 PR] with the attached patch, but there's no discussion about why that solution is preferred despite the previous comment. -- Ticket URL: <https://code.djangoproject.com/ticket/26149#comment:8> 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/068.99c74c515eeac8084de258f5bd860060%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.