#25789: Inefficient Queries Generated due to not using WHERE EXISTS
-------------------------------------+-------------------------------------
Reporter: Alex Rothberg | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: QuerySet.extra | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
FWIW I had a very limited try at this in
[https://github.com/django/django/compare/main...charettes:django:exists-
m2m-lookup this branch]. Mostly some test and debugging shims but I
figured I'd provide them if someone is interesting in looking this issue.
I'd add that this work has a bit of overlap with #28296 as it basically
needs to turn a series of transforms and lookups against a related field
into a subquery without causing JOINs on the outer query which the default
behaviour of using the `__` syntax.
--
Ticket URL: <https://code.djangoproject.com/ticket/25789#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701836197b663-b4082770-5fc4-45b8-ad57-793fd1a9b166-000000%40eu-central-1.amazonses.com.
