summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorMohammad Kazemi <mokazemi@disroot.org>2024-04-15 19:46:35 +0330
committerGitHub <noreply@github.com>2024-04-15 13:16:35 -0300
commit47c608202a58c8120d049c98d5d27c4609551d33 (patch)
tree47867bbcc98128c994d7a723108c42b0376ba692 /docs/ref
parent2bcf555763f3d4fa19c135ac895e5d16e9d7141a (diff)
Extended docs for Q() objects mentioning the ~ (NOT) operator.
Co-authored-by: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com>
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/models/querysets.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 0118cf4e5b..66d6259ec5 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -4078,9 +4078,10 @@ elsewhere.
A ``Q()`` object represents an SQL condition that can be used in
database-related operations. It's similar to how an
:class:`F() <django.db.models.F>` object represents the value of a model field
-or annotation. They make it possible to define and reuse conditions, and
-combine them using operators such as ``|`` (``OR``), ``&`` (``AND``), and ``^``
-(``XOR``). See :ref:`complex-lookups-with-q`.
+or annotation. They make it possible to define and reuse conditions. These can
+be negated using the ``~`` (``NOT``) operator, and combined using operators
+such as ``|`` (``OR``), ``&`` (``AND``), and ``^`` (``XOR``). See
+:ref:`complex-lookups-with-q`.
``Prefetch()`` objects
----------------------