#32632: Query resolution can be at least 3x slower in 3.2
-------------------------------------+-------------------------------------
Reporter: Phillip Cutter | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Thanks for the investigation!
2 & 3 make sense for me, however I would like to see an implementation
first. This can be too massive for backporting. I'm a bit afraid that we
can open the Pandora's box.
Will we be able to keep support for combining `Q()` objects
[https://github.com/django/django/blob/78eaae9bf16f455c3a35234e0a04c08d5c82f808/django/db/models/query_utils.py#L46-L53
with boolean expressions]?
--
Ticket URL: <https://code.djangoproject.com/ticket/32632#comment:5>
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/065.6ce5e82edf5925353b3a49e5dc9781ed%40djangoproject.com.
