#29097: Migrations using MySQL fail for constraints using composite indexes
-------------------------------------+-------------------------------------
Reporter: geertjanvdk | Owner: Hasan
| Ramezani
Type: Bug | Status: closed
Component: Migrations | Version: 1.11
Severity: Normal | Resolution: fixed
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 felixxm):
* status: assigned => closed
* resolution: => fixed
Comment:
`kc.'constraint_name'` in an `ORDER BY` should not be necessary. I think
we can close this issue because ordering was added in
4fba321a457e52df77d0b512d043019e9f6b0bc9 and creating a regression test
may not be feasible (see [https://github.com/django/django/pull/9941
discussion]).
--
Ticket URL: <https://code.djangoproject.com/ticket/29097#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.83543425b39f998d9f26984ebc57ffce%40djangoproject.com.
