#27388: Filter chaining results in unnecessary joins (and degenerate
performance)
-------------------------------------+-------------------------------------
Reporter: Connor Osborn | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: queryset, join, | Triage Stage:
performance | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
> It looks like if I set the filter_is_sticky flag it gets reset to false
in the next filter. So in order to have a chain each one must be add that
flag, is that right?
Exactly but relying on Django's internal APIs is risky as it might be
replaced in future versions.
--
Ticket URL: <https://code.djangoproject.com/ticket/27388#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.5bd4e2a795396d91fded68d21e2c6c81%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
