On 10/11/06, Aidas Bendoraitis <[EMAIL PROTECTED]> wrote: > > I think, you should be able to do that with the method extra() at the moment: > http://www.djangoproject.com/documentation/db_api/#extra-select-none-where-none-params-none-tables-none > > Anyway I am +1 for this proposal, as it would make things easier and faster.
This is enhancement ticket #1435 (http://code.djangoproject.com/ticket/1435). This is a long standing request, and has been discussed before. Follow the mailing list links in the ticket for more details. As stated in those threads, I'm -1 on this change. There are several reasons: 1) The QuerySet code is currently being massivly refactored internally - I haven't seen the code yet, but as I understand it, one of the goals of this refactor is to make it easier to write extra-like clauses that access aggregate functions. 2) One of the reasons for the development of the SQLAlchemy stream is to aggregates easier to use. This development was specifically instigated by a desire to keep the core Django query syntax clean, consistent and obvious. 3) I _really_ don't like the proposed .sum(), max() etc syntax. Follow the mailing list links for reasons why. 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 -~----------~----~----~----~------~----~------~--~---
