Re: Adding missing aggregate functions to contrib.postgres ?

On Monday 09 February 2015 02:01:03 Russell Keith-Magee wrote: > > The only other thing I'd flag is that if any of these aggregates are recent > additions (e.g., added in Postgres 9), the failure mode for earlier > versions should be relatively clean. > Nitpick: Django 1.8 -- the first to have dj

Re: Adding missing aggregate functions to contrib.postgres ?

ld *all* aggregates >>>> functions from >>>> http://www.postgresql.org/docs/9.4/static/functions-aggregate.html be >>>> implemented ? I'm asking to prevent doing unnecessary work. >>>> >>>> воскресенье, 8 февраля 2015 г., 1:11:08 U

Re: Adding missing aggregate functions to contrib.postgres ?

/www.postgresql.org/docs/9.4/static/functions-aggregate.html be >>> implemented ? I'm asking to prevent doing unnecessary work. >>> >>> воскресенье, 8 февраля 2015 г., 1:11:08 UTC+2 пользователь Andriy >>> Sokolovskiy (c

Re: Adding missing aggregate functions to contrib.postgres ?

;> I opened a ticket for it. >>> https://code.djangoproject.com/ticket/24301 >>> >>> суббота, 7 февраля 2015 г., 18:51:34 UTC+2 пользователь Michael Manfre >>> написал: >>>> >>>> It's reasonable to support backend specific aggregate funct

Re: Adding missing aggregate functions to contrib.postgres ?

cket. >>> >>> Regards, >>> Michael Manfre >>> >>> On Sat, Feb 7, 2015 at 9:00 AM, Andriy Sokolovskiy (coldmind) < >>> soka...@yandex.ru> wrote: >>> >>>> So, since django has contrib.postgres, maybe it would be reasonable to >&

Re: Adding missing aggregate functions to contrib.postgres ?

vskiy (coldmind) написал: > > I opened a ticket for it. > https://code.djangoproject.com/ticket/24301 > > суббота, 7 февраля 2015 г., 18:51:34 UTC+2 пользователь Michael Manfre > написал: >> >> It's reasonable to support backend specific aggregate function

Re: Adding missing aggregate functions to contrib.postgres ?

I opened a ticket for it. https://code.djangoproject.com/ticket/24301 суббота, 7 февраля 2015 г., 18:51:34 UTC+2 пользователь Michael Manfre написал: > > It's reasonable to support backend specific aggregate functions. The > database backen

Re: Adding missing aggregate functions to contrib.postgres ?

It's reasonable to support backend specific aggregate functions. The database backend API contains BaseDatabaseOperations.check_expression_support for this exact reason. Feel free to create the ticket. Regards, Michael Manfre On Sat, Feb 7, 2015 at 9:00 AM, Andriy Sokolovskiy (coldmind) <

Adding missing aggregate functions to contrib.postgres ?

So, since django has contrib.postgres, maybe it would be reasonable to add postgres-specific aggregate functions to this module? If it is good idea, I'm gonna create ticket and implement this. -- You received this message because you are subscribed to the Google Groups "Django

Aggregate functions - #1435 patch how to

Hello, sorry in advance for the dumb questions: I need to use aggregate functions into my db queries, actually I need SUM. I saw a patch referring to the ticket #1435. I have 2 questions: 1 - How many chance are there to integrate this patch in the trunk before 1.0? 2 - How can I apply the

Re: Aggregate Functions

> I'm not opposed to the idea of a simple min/max etc API in addition to some > mega-aggregate API. I am completely opposed to this. What I am trying to devise is a non-mega-aggregate function that handles 80% of the cases easily. The sum(), min(), max() etc. convenience functions are _not_ that.

Re: Aggregate Functions

orphism - There is no reason that get_aggregate couldn't accept a list as its first parameter as well as a single item - The method name is get_ in an API moving towards descriptorsNot to put too fine a point on it, but I find very little in get_aggregates that is appealing. all, is how I do the

Re: Aggregate Functions

tity') Inventory.objects.calculate(['AVG','MIN','MAX'],'quantity') Of course, you would then allow singular and iterable for the aggregate functions. --~--~-~--~~~---~--~~ You received this message because you are subsc

Re: Aggregate Functions

the names should be expanded or none. I prefer none since the non-standard SQL aggregate functions must match the SQL provided name precisely. Might as well make the standard function names do the same. The get_aggregate() function is really just the shared code behind sum(), min(), max(), stddev() an

Re: Aggregate Functions

On 3/2/06, Rock <[EMAIL PROTECTED]> wrote: > > My other changeset developed at this week's Django Sprint is much more > extensive and is best explained by the new section that I am adding to > the DB API docs. > > Feedback is welcome. Truth be told, a desire to improve aggregates in Django is the

Aggregate Functions

My other changeset developed at this week's Django Sprint is much more extensive and is best explained by the new section that I am adding to the DB API docs. Feedback is welcome. Rock Aggregate Functions === Aggregate functions perform calculations on columns. Typi