mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-11-19 19:24:46 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Refs #35381 -- Clarified key and index lookup handling of None in exact lookup docs.
Some checks failed
Linters / isort (push) Waiting to run
Details
Linters / flake8 (push) Waiting to run
Details
Linters / black (push) Waiting to run
Details
Tests / Windows, SQLite, Python 3.14 (push) Waiting to run
Details
Tests / JavaScript tests (push) Waiting to run
Details
Docs / spelling (push) Has been cancelled
Details
Docs / blacken-docs (push) Has been cancelled
Details
Docs / lint-docs (push) Has been cancelled
Details

Browse source
This commit is contained in:
Clifford Gama 2025-10-23 15:57:16 +02:00 • committed by Jacob Walls
parent 348ca84538
commit 7fc9db1c6a
1 changed files with 2 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/ref/models/querysets.txt
View file

@ -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 <jsonfield.key>` are exceptions: they
interpret ``None`` as JSON ``null`` instead.
Examples::