From 7b42d346465abb560d1b774bdf17d094fad75571 Mon Sep 17 00:00:00 2001 From: David-Wobrock Date: Fri, 13 Nov 2020 22:34:16 +0100 Subject: Refs #27718 -- Doc'd and tested QuerySet.exists() for combined querysets. Supported since 84c1826ded17b2d74f66717fb745fc36e37949fd. --- docs/ref/models/querysets.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 9e129932b2..c1a8fd1f3d 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -917,11 +917,11 @@ resulting ``QuerySet``. For example:: >>> qs1.union(qs2).order_by('name') In addition, only ``LIMIT``, ``OFFSET``, ``COUNT(*)``, ``ORDER BY``, and -specifying columns (i.e. slicing, :meth:`count`, :meth:`order_by`, and -:meth:`values()`/:meth:`values_list()`) are allowed on the resulting -``QuerySet``. Further, databases place restrictions on what operations are -allowed in the combined queries. For example, most databases don't allow -``LIMIT`` or ``OFFSET`` in the combined queries. +specifying columns (i.e. slicing, :meth:`count`, :meth:`exists`, +:meth:`order_by`, and :meth:`values()`/:meth:`values_list()`) are allowed +on the resulting ``QuerySet``. Further, databases place restrictions on +what operations are allowed in the combined queries. For example, most +databases don't allow ``LIMIT`` or ``OFFSET`` in the combined queries. ``intersection()`` ~~~~~~~~~~~~~~~~~~ -- cgit v1.3