#26194: WHERE EXISTS / WHERE NOT EXISTS clause without using QuerySet.extra
-------------------------------------+-------------------------------------
Reporter: john-parton | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: QuerySet.extra | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by shaib):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
Consider using the reverse relation:
{{{
Parent.objects.filter(child=None)
}}}
It should create a left join, which should perform comparably with the
`EXISTS` query.
Also, please consider using [wiki:TicketClosingReasons/UseSupportChannels
our support channels] next time.
--
Ticket URL: <https://code.djangoproject.com/ticket/26194#comment:1>
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/069.58e5d260d110f254580190cfbc9241ea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
