#34845: Slow query when using exclude
-------------------------------------+-------------------------------------
Reporter: Amin Aminian | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: exclude,filter | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David Sanders):
So there's a couple of things here:
You asked:
> Why Django uses subquery when using exclude ?
Questions are usually interpreted as seeking help ;) Please refer all
questions to the community and not Trac ;)
> I just wanted to make sure it was intended.
We're aware of some possible performance issues related to the way Django
renders `NOT EXISTS`, eg: https://code.djangoproject.com/ticket/34597
--
Ticket URL: <https://code.djangoproject.com/ticket/34845#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018aa3a7060d-214155cf-67ab-4429-a20e-81bb5590b051-000000%40eu-central-1.amazonses.com.
