#28211: Inefficient query produced when using OR'ed Q objects
-------------------------------------+-------------------------------------
Reporter: Tom | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"bb0b6e526340e638522e093765e534df4e4393d2" bb0b6e52]:
{{{
#!CommitTicketReference repository=""
revision="bb0b6e526340e638522e093765e534df4e4393d2"
Fixed #28211 -- Prevented ORing an empty Q() from reducing query join
efficiency.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28211#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 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/061.247ee5e36e4460fb9425f3315dcf42ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
