From e20e5d1557785ba71e8ef0ceb8ccb85bdc13840a Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Tue, 26 Jul 2022 20:21:27 +0200 Subject: Fixed #33820 -- Doc'd "true"/"false"/"null" caveat for JSONField key transforms on SQLite. Thanks Johnny Metz for the report. Regression in 71ec102b01fcc85acae3819426a4e02ef423b0fa. --- docs/topics/db/queries.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/topics') diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt index 2d43e7ee32..d256545453 100644 --- a/docs/topics/db/queries.txt +++ b/docs/topics/db/queries.txt @@ -1091,6 +1091,12 @@ To query for missing keys, use the ``isnull`` lookup:: On PostgreSQL, if only one key or index is used, the SQL operator ``->`` is used. If multiple operators are used then the ``#>`` operator is used. +.. admonition:: SQLite users + + On SQLite, ``"true"``, ``"false"``, and ``"null"`` string values will + always be interpreted as ``True``, ``False``, and JSON ``null`` + respectively. + .. _containment-and-key-lookups: Containment and key lookups -- cgit v1.3