#10929: Support a default value for Sum (and possibly other aggregation
functions)
-------------------------------------+-------------------------------------
Reporter: nolan | Owner: Nick Pope
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: aggregate annotate | Triage Stage: Ready for
default | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"fee87345967b3d917b618533585076cbfa43451b" fee87345]:
{{{
#!CommitTicketReference repository=""
revision="fee87345967b3d917b618533585076cbfa43451b"
Refs #10929 -- Deprecated forced empty result value for PostgreSQL
aggregates.
This deprecates forcing a return value for ArrayAgg, JSONBAgg, and
StringAgg when there are no rows in the query. Now that we have a
``default`` argument for aggregates, we want to revert to returning the
default of ``None`` which most aggregate functions return and leave it
up to the user to decide what they want to be returned by default.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/10929#comment:34>
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/063.5bd4489f99c4e1fd2d66c7f52d3b0eab%40djangoproject.com.
