#28211: Inefficient query produced when using OR'ed Q objects
-------------------------------------+-------------------------------------
Reporter: Tom | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
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 Simon Charette):
* version: 1.10 => master
* stage: Accepted => Ready for checkin
Comment:
I think the provided patch solves this in an efficient way.
We could add folding logic in the query compiler as well but given it will
be very hard to generate combined `Q` with a falsey sides after with this
patch (one would have to call `Q.add` manually) I don't think it's
required.
--
Ticket URL: <https://code.djangoproject.com/ticket/28211#comment:4>
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.87e2478ff68a6304a01b3e21cbd22498%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
