#35318: QuerySet.exclude() docs contain a potentially misleading statement
regarding the restrictiveness of examples.
-------------------------------------+-------------------------------------
Reporter: P1car00n | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 5.0
Severity: Normal | Resolution: invalid
Keywords: QuerySet, | Triage Stage:
Clarification, Accuracy | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by P1car00n):
Thanks for considering my report. I just wanted to suggest a possible
clarification regarding the wording then. Instead of "more restrictive,"
perhaps we could use "more exclusionary" to describe the second example?
This could help avoid confusion about the intention behind the term. What
do you think?
P.S.
While it's true that the second example excludes more rows, I ''feel''
that the term "restrictive" in the context of querying refers to how
narrowly or precisely the conditions filter the results, not necessarily
the quantity of rows excluded.
--
Ticket URL: <https://code.djangoproject.com/ticket/35318#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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e5d3ec4d9-937968a9-1d1f-4667-94eb-77723ffe4f3b-000000%40eu-central-1.amazonses.com.
