From 83c631ade7b5f853580a44f3e8e8f6d6ea367b24 Mon Sep 17 00:00:00 2001 From: Adam Johnson Date: Wed, 6 May 2020 05:43:28 +0100 Subject: [PATCH] Improved wording in Q() docs. --- docs/ref/models/querysets.txt | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index cd22b03418..784d22ce4b 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -3567,14 +3567,12 @@ elsewhere. .. class:: Q -A ``Q()`` object, like an :class:`~django.db.models.F` object, encapsulates a -SQL expression in a Python object that can be used in database-related -operations. - -In general, ``Q() objects`` make it possible to define and reuse conditions. -This permits the :ref:`construction of complex database queries -` using ``|`` (``OR``) and ``&`` (``AND``) operators; -in particular, it is not otherwise possible to use ``OR`` in ``QuerySets``. +A ``Q()`` object represents an SQL condition that can be used in +database-related operations. It's similar to how an +:class:`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``). See +:ref:`complex-lookups-with-q`. ``Prefetch()`` objects ----------------------