From 2d8dcba03aae200aaa103ec1e69f0a0038ec2f85 Mon Sep 17 00:00:00 2001 From: sage Date: Sun, 26 Jul 2020 11:54:40 +0700 Subject: Fixed #31829 -- Used JSONField __contains lookup on key transforms. --- docs/topics/db/queries.txt | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt index a56f9bf078..1b71cd77ff 100644 --- a/docs/topics/db/queries.txt +++ b/docs/topics/db/queries.txt @@ -905,10 +905,10 @@ To query for missing keys, use the ``isnull`` lookup:: The lookup examples given above implicitly use the :lookup:`exact` lookup. Key, index, and path transforms can also be chained with: - :lookup:`contains`, :lookup:`icontains`, :lookup:`endswith`, - :lookup:`iendswith`, :lookup:`iexact`, :lookup:`regex`, :lookup:`iregex`, - :lookup:`startswith`, :lookup:`istartswith`, :lookup:`lt`, :lookup:`lte`, - :lookup:`gt`, and :lookup:`gte` lookups. + :lookup:`icontains`, :lookup:`endswith`, :lookup:`iendswith`, + :lookup:`iexact`, :lookup:`regex`, :lookup:`iregex`, :lookup:`startswith`, + :lookup:`istartswith`, :lookup:`lt`, :lookup:`lte`, :lookup:`gt`, and + :lookup:`gte`, as well as with :ref:`containment-and-key-lookups`. .. warning:: @@ -937,8 +937,10 @@ 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. -Containment and key operations ------------------------------- +.. _containment-and-key-lookups: + +Containment and key lookups +--------------------------- .. fieldlookup:: jsonfield.contains -- cgit v1.3