I realize how the aggregates work, but if annotate is just for aggregates, then remove it as a standalone method. If it's not, then it should solve all the problems with one blow.
On May 12, 4:37 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On Mon, May 12, 2008 at 10:50 PM, David Cramer <[EMAIL PROTECTED]> wrote: > > > What is the difference between annotate and aggregate? They seem like > > they'd do the same thing, except annotate sounds like it should be > > doing GROUP BY, > > I don't mean to be rude, David, but the difference between the two > functions has been discussed _at length_, both in the past, and in > recent memory. > > Short version: > > Annotate returns a query set of objects, but with each returned object > enhanced with aggregated attribute(s) (e.g., a list of people, each of > which is annotated with the sum of their individual purchases) > > Aggregate returns the summary statistics over a query set (e.g., the > average age of people matching a query). > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
