On 12/4/06 5:57 AM, John Lenton wrote: > The "max", "min" and other such functions might be a little more > problematic, unless groupby returned, rather than a generic iterator, > a special "queryset group" and give _it_ the max/min/etc methods. This > way it would be clear that max() returns a tuple (value, queryset) (to > me, at least...). Also, ...groupby('foo').max() would return the same > result as max(...groupby('foo')), but less efficiently. > > Talking through my hat?
No, I think not -- I think that syntax (``queryset.groupby(field).max()``) actually looks like the best proposal for aggregates I've seen thus far... I'm taking this to django-dev for more discussion; it'll get seen by more the right people there. Thoughts, anyone? Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---