Ticket #19842: add_annotate_suggestion.patch

File add_annotate_suggestion.patch, 1.1 KB (added by jgeskens, 2 years ago)
  • docs/ref/models/querysets.txt

    From 4d1c420e006bbb625873de49664e2b7c0f6ca78f Mon Sep 17 00:00:00 2001
    From: jgeskens <jef.geskens@gmail.com>
    Date: Sat, 18 May 2013 12:41:01 +0200
    Subject: [PATCH] Add aggregate suggestion to distinct notes #19842
    
    ---
     docs/ref/models/querysets.txt |    2 ++
     1 files changed, 2 insertions(+), 0 deletions(-)
    
    diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
    index ffada19..9d68cc7 100644
    a b query spans multiple tables, it's possible to get duplicate results when a 
    368368    otherwise duplicate rows appear to be distinct. Since the extra columns
    369369    don't appear in the returned results (they are only there to support
    370370    ordering), it sometimes looks like non-distinct results are being returned.
     371    In this case, it may be possible to get distinct results using
     372    :meth:`aggregate` instead.
    371373
    372374    Similarly, if you use a :meth:`values()` query to restrict the columns
    373375    selected, the columns used in any :meth:`order_by()` (or default model
Back to Top