Opened 5 years ago

Last modified 17 months ago

#16025 new Bug

distinct does not apply to aggregated querysets

Reported by: micolous Owned by:
Component: Database layer (models, ORM) Version: 1.6
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by ramiro)

When applying .distinct() to a QuerySet, performing an aggregation using .aggregate() on that will only ensure that the aggregation result is distinct. As a result, this prevents you from doing a query where you want the input to the aggregation to have distinct rows.

Take the example models:

class Category(Model):
  label = CharField(max_length=128)

class Food(Model):
  name = CharField(max_length=128)
  categories = ManyToManyField(Category)
  kilojoules_per_kg = PositiveIntegerField()

If you then did a query on which you selected a couple of Categories as foreign keys (eg: "Pizza Toppings" and "Fruits"), you'd end up with a list of Foods that would contain duplicates where a food item fits in multiple categories (eg: "Apple", "Orange", "Pineapple", "Pineapple", "Bacon" and "Cheese" ...).

If you then wanted to then find the average number of kilojoules per kilogram for items in those groups and eliminate duplicates (Pineapple), the documentation would lead you to do this:


However instead of counting Pineapple once, Pineapple would be counted twice, as the distinct() call would only apply to the result of the aggregation, not to the input of it.

>>> qs.distinct().aggregate(Avg('kilojoules_per_kg')) == qs.aggregate(Avg('kilojoules_per_kg'))

Instead, .distinct() before .aggregate() should instead cause a subquery to be executed to filter the results before passing it to the aggregation functions. There doesn't seem a way to presently execute a query like this using the Django ORM.

.distinct() after an aggregation should cause the results of the aggregation to be filtered so only distinct records are returned (which is the current behavior).

I've managed to confirm this behavior in Django 1.2.3 and 1.3.

Change History (9)

comment:1 Changed 5 years ago by micolous

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

I'm aware wrote "Average" here instead of "Avg" -- I meant "Avg". The rest of the bug still applies, I was trying to make an example of the error that was effecting my application using different models (because my application's models are rather complex), but have the same basic problem as described here.

Last edited 5 years ago by micolous (previous) (diff)

comment:2 Changed 5 years ago by ramiro

  • Component changed from Database layer (models, ORM) to ORM aggregation
  • Triage Stage changed from Unreviewed to Accepted

Does your Food model have any Meta.ordering model option or does the queryset have a order_by() call somewhere?

comment:3 Changed 5 years ago by micolous

In the example application I developed it doesn't (the only difference is I've implemented __unicode__, but in the application I'm actually writing it does.

Both ways give the same (erroneous) result.

comment:4 Changed 5 years ago by ramiro

  • Description modified (diff)

comment:6 Changed 3 years ago by akaariai

  • Component changed from ORM aggregation to Database layer (models, ORM)

comment:7 Changed 2 years ago by vsajip

  • Version changed from 1.3 to 1.6

Still there in 1.6 :-(

comment:8 Changed 17 months ago by mikalai

  • Owner changed from nobody to mikalai
  • Status changed from new to assigned

comment:9 Changed 17 months ago by mikalai

  • Owner mikalai deleted
  • Status changed from assigned to new
Note: See TracTickets for help on using tickets.
Back to Top