diff options
| author | Florian Apolloner <florian@apolloner.eu> | 2017-07-14 18:11:29 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2017-07-15 08:20:12 -0400 |
| commit | adab280cefb15659c39558ac26ea392b0a1e456c (patch) | |
| tree | d25014600368259ebbe806dd677530bda72cae5e /docs/ref | |
| parent | 9290f15bb525c7c0d2d06bee055d177ec947a1f6 (diff) | |
Fixed #28399 -- Fixed QuerySet.count() for union(), difference(), and intersection() queries.
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/models/querysets.txt | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 8cdf32b247..2c1f68fc06 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -821,11 +821,15 @@ of other models. Passing different models works as long as the ``SELECT`` list is the same in all ``QuerySet``\s (at least the types, the names don't matter as long as the types in the same order). -In addition, only ``LIMIT``, ``OFFSET``, and ``ORDER BY`` (i.e. slicing and -:meth:`order_by`) 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. +In addition, only ``LIMIT``, ``OFFSET``, ``COUNT(*)``, and ``ORDER BY`` (i.e. +slicing, :meth:`count`, and :meth:`order_by`) 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. + +.. versionchanged:: 1.11.4 + + ``COUNT(*)`` support was added. ``intersection()`` ~~~~~~~~~~~~~~~~~~ |