#36607: Improve the documentation by mentioning that "filter(a,b)" may not be
the
same as "filter(a).filter(b)" on querysets.
-------------------------------------+-------------------------------------
Reporter: Aaron | Owner: (none)
Type: Uncategorized | Status: new
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tanishq):
Hey Aaron,
the example you shared does a great job highlighting the difference
between {{{filter(a, b)}}} and {{{filter(a).filter(b)}}}
—especially how SQL joins come into play. I agree it’s worth documenting
this nuance, probably in the “Joining and Filtering” section of
{{{docs/topics/db/queries.txt}}}. A quick note about how chained filters
can trigger extra joins and potentially change result sets (like in your
{{{UnscheduledMaintenance}}}example) would be super helpful.
I can work on this Issue and even update the docs to perfectly cover this
section.
--
Ticket URL: <https://code.djangoproject.com/ticket/36607#comment:2>
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 visit
https://groups.google.com/d/msgid/django-updates/010701993d6181b1-4ce7338e-4766-4f0f-9c5a-4d57874f5faf-000000%40eu-central-1.amazonses.com.
