#29097: Migrations using MySQL fail for constraints using composite indexes
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: Hasan
| Ramezani
Type: Bug | Status: assigned
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: introspection mysql | Triage Stage: Accepted
migration index constraint |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Hasan Ramezani):
* owner: (none) => Hasan Ramezani
* status: new => assigned
* needs_tests: 1 => 0
Comment:
Seems it has been fixed in
[https://github.com/django/django/commit/4fba321a457e52df77d0b512d043019e9f6b0bc9]
I Added a patch to test it.
Question: Do we need to add `kc.'constraint_name'` to `ORDER BY` as well?
--
Ticket URL: <https://code.djangoproject.com/ticket/29097#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.ba52903a1794e0ea36468cb296bc4ec6%40djangoproject.com.
