#34808: Some aggregation functions may return None; this isn't well documented
-------------------------------------+-------------------------------------
Reporter: Eric Baumgartner | Owner: Lufafa
Type: | Joshua
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 4.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Lufafa Joshua):
Hey guys, would it be necessary to add a possible return of None on every
aggregate function in
https://docs.djangoproject.com/en/4.2/ref/models/querysets/. There is a
notice under aggregation functions on the querysets page that already does
so, perhaps adding a link on the querysets page about the default argument
usage in https://docs.djangoproject.com/en/4.2/topics/db/aggregation/
would be helpful.
--
Ticket URL: <https://code.djangoproject.com/ticket/34808#comment:12>
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/0107018ab1c29c56-e4c08e10-8c37-4a66-b2a4-efb86a6077d2-000000%40eu-central-1.amazonses.com.
