#34811: Queryset filter Q order changed
-------------------------------------+-------------------------------------
Reporter: Edward Villegas- | Owner: nobody
Pulgarin |
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: filter, Q | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by David Sanders):
* status: new => closed
* resolution: => worksforme
Comment:
Hi,
Thanks for the report though I don't see an issue with Django here. There
are many reasons why a database will choose to ignore indexes but sadly
parameter ordering is not one of those. (To test this I recreated your
setup and MySQL reported that the indexes are a possibility both ways.)
I'd encourage you to seek help from one of the Django support channels
where there are many friendly people who are eager to help:
https://www.djangoproject.com/community/
You'll likely need to paste detailed descriptions of your models, query,
setup & any query plans (you may even be asked to paste memory settings
etc as this will have an impact on query planning).
If it is discovered there is an issue with Django feel free to reopen this
with links to discussion & findings.
Good luck!
--
Ticket URL: <https://code.djangoproject.com/ticket/34811#comment:1>
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/0107018a589a6f43-d364699c-edd8-4158-ae60-1fd66bb0042d-000000%40eu-central-1.amazonses.com.
