From 9369f0cebba1f65909a14dec6aa3515ec1eb2557 Mon Sep 17 00:00:00 2001 From: Hasan Ramezani Date: Wed, 9 Sep 2020 12:54:25 +0200 Subject: [PATCH] Fixed #31967 -- Doc'd consequences of resolving an output_field for Value(). --- docs/releases/3.2.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/releases/3.2.txt b/docs/releases/3.2.txt index b0a580fa05..9000b170eb 100644 --- a/docs/releases/3.2.txt +++ b/docs/releases/3.2.txt @@ -277,7 +277,10 @@ Models :py:class:`float`, :py:class:`int`, :py:class:`str`, :py:class:`datetime.date`, :py:class:`datetime.datetime`, :py:class:`datetime.time`, :py:class:`datetime.timedelta`, - :py:class:`decimal.Decimal`, and :py:class:`uuid.UUID` instances. + :py:class:`decimal.Decimal`, and :py:class:`uuid.UUID` instances. As a + consequence, resolving an ``output_field`` for database functions and + combined expressions may now crash with mixed types when using ``Value()``. + You will need to explicitly set the ``output_field`` in such cases. * The new :meth:`.QuerySet.alias` method allows creating reusable aliases for expressions that don't need to be selected but are used for filtering,