#24385: Sum() doesn't seem to respect .distinct() in the queryset filter before
.aggregate() when filtering by m2m.
-------------------------------------+-------------------------------------
     Reporter:  mcagl                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  1.7
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by camillobruni):

 http://www.sqlteam.com/article/how-to-use-group-by-with-distinct-
 aggregates-and-derived-tables describes this issue on SQL-level. Their
 solution was to use a derived table, something that is not directly
 possible with django queries, I think. The only solution I came up with
 was to sum up the values in a python loop, relying on `distinct()` to
 properly do its job.

--
Ticket URL: <https://code.djangoproject.com/ticket/24385#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.baafbb78f5bfe9399327d84fc635b407%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to