QuerySet refactoring is like Django 1.0 ya? Never coming? We've been struggling to use the Django ORM for a long while now, because it has limited support for complex queries. GROUP BY is a nescesity. I don't see any problem with redoing the QuerySet methods, but there's no reason to not put in working fixes right now.
On Jul 27, 8:06 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On 7/28/07, David Cramer <[EMAIL PROTECTED]> wrote: > > > > > I committed a quick patch earlier to trunk that adds group_by() > > support. > > Hi David, > > The idea of a 'group_by' and 'having' clause has been floated many > times before, and has been rejected in preference of an 'aggregations' > framework that provides a higher level, ORM-like interface (rather > than a SQL like interface) to the the ideas that group_by and having > expose. See Ticket #3566 for details on current thinking. > > Adding this feature is waiting on a refactor of the internals of the > query engine. Malcolm is in the process of doing this refactor; any > patch against query.py is likely to be rendered invalid in the near > future. > > 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
