From 3d2236773ba88e330841b8c72183b0e978e10909 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 8 Dec 2015 16:45:15 -0500 Subject: [PATCH] Refs #10060 -- Corrected description of multiple annotations bug. --- docs/topics/db/aggregation.txt | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/topics/db/aggregation.txt b/docs/topics/db/aggregation.txt index 030335c908..4838663beb 100644 --- a/docs/topics/db/aggregation.txt +++ b/docs/topics/db/aggregation.txt @@ -190,9 +190,8 @@ Combining multiple aggregations ------------------------------- Combining multiple aggregations with ``annotate()`` will `yield the wrong -results `_, as multiple tables are -cross joined. Due to the use of ``LEFT OUTER JOIN``, duplicate records will be -generated if some of the joined tables contain more records than the others: +results `_ because joins are used +instead of subqueries: >>> Book.objects.first().authors.count() 2 @@ -374,8 +373,8 @@ Both queries return a list of publishers that have at least one book with a rating exceeding 3.0, hence publisher C is excluded. In the first query, the annotation precedes the filter, so the filter has no -effect on the annotation. ``distinct=True`` is required to avoid a -:ref:`cross-join bug `. +effect on the annotation. ``distinct=True`` is required to avoid a :ref:`query +bug `. The second query counts the number of books that have a rating exceeding 3.0 for each publisher. The filter precedes the annotation, so the filter