What GROUP BY pitfalls show up with annotate() and aggregate()?
PICTURE THIS: SQL JOIN
Simple meaning
annotate() adds per-row annotations and may group by the primary key plus selected fields
WHY — ORM instead of guessing?
Why interviewers care about ORM:
who only read docs from people who shipped.
and tied to Python work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1annotate() adds per-row annotations
and may group by the primary key plus selected fields
- 2mixing it with values()
changes the grouping key.
- 3aggregate() collapses the whole
queryset to a dict of aggregates.
- 4Joins can multiply rows
before aggregation, so Count('related') needs distinct=True when the join duplicates parents.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
annotate() adds per-row annotations and may group by the primary key plus selected fields mixing it with values() changes the grouping key.