#20888: Index ordering in index_together and unique_together
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: akki
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: index, order, db- | Triage Stage: Accepted
indexes |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akki):
* has_patch: 0 => 1
Comment:
PR: https://github.com/django/django/pull/6982
Although requested for `alter_together`, I have implemented the feature
with the new class based indexes which would allow users to do the same
thing.
The patch contains implementation for all databases except backend which
doesn't support the feature itself according to their
[http://dev.mysql.com/doc/refman/5.7/en/create-index.html official docs].
I felt this to be a bit weird as the reporter had requested the feature
specifically for MySQL. Please let me know if I missed something in this
context.
The patch doesn't add the feature for `unique_together` as I couldn't
understand/don't know what that means. I can try to add it for
`unique_together` as well if somebody could explain that.
--
Ticket URL: <https://code.djangoproject.com/ticket/20888#comment:11>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.8ca4afea795520f91e4230d946c158bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
