#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):
James, since this ticket was filled support for `Exists` expression was
added so you should be able to avoid using `extra`
{{{#!python
queryset.annotate(
foo_exists=Exists(subqueryset.filter(foo_id=OuterRef('pk'))
).filter(
foo_exists=False,
)
}}}
Once #25367 lands it'll be possible to pass `~Exists` directly to filter.
--
Ticket URL: <https://code.djangoproject.com/ticket/25789#comment:9>
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/067.1d660a5a704c6402f0e6b66fef4fcb5a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
