From 7fc9db1c6a3a4865d85338f26812ce80f076ebec Mon Sep 17 00:00:00 2001 From: Clifford Gama Date: Thu, 23 Oct 2025 15:57:16 +0200 Subject: [PATCH] Refs #35381 -- Clarified key and index lookup handling of None in exact lookup docs. --- docs/ref/models/querysets.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index e494739bcd..9bfaea025d 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -3188,6 +3188,8 @@ As a convenience when no lookup type is provided (like in Exact match. If the value provided for comparison is ``None``, it will be interpreted as an SQL ``NULL`` (see :lookup:`isnull` for more details). +:lookup:`Key and index lookups ` are exceptions: they +interpret ``None`` as JSON ``null`` instead. Examples::