From fe59bf202d35467e3e4a169c1aac979b713a020a Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Fri, 31 Dec 2021 06:49:10 +0100 Subject: [PATCH] [4.0.x] Fixed #33391 -- Clarified Aggregate.empty_result_set_value docs. Backport of 4400d8568ad5695c46e8de45635a82a27a26b871 from main --- docs/ref/models/expressions.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt index c0ef4a46d0..a47e35b110 100644 --- a/docs/ref/models/expressions.txt +++ b/docs/ref/models/expressions.txt @@ -422,9 +422,8 @@ The ``Aggregate`` API is as follows: .. versionadded:: 4.0 - Override :attr:`~django.db.models.Expression.empty_result_set_value` to - ``None`` since most aggregate functions result in ``NULL`` when applied - to an empty result set. + Defaults to ``None`` since most aggregate functions result in ``NULL`` + when applied to an empty result set. The ``expressions`` positional arguments can include expressions, transforms of the model field, or the names of model fields. They will be converted to a