Re: multi-column aggregates

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Chris Kratz" <chris(dot)kratz(at)vistashare(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: multi-column aggregates
Date: 2006-03-09 19:18:28
Message-ID: b42b73150603091118n5b8a64ddu4ffcec1d654fbcca@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Chris Kratz wrote:
> Well for anyone else who may be interested in doing something similar, here is
> what we did. It does require typecasting going into the functions, composite
> types and using the dot notation to get the value back out of the composite
> object returned. But it works.
>
> This is what we wanted...
>
> select last(cur_date, some_column) from some_table....
>
> We got this close...
>
> select (last((cur_date, some_column)::last_int_agg)).value as last_int from...

have you looked at new row-wise comparison feature (i might be
misunderstanding your problem)?

select some_column from some_table where (cur_date, some_column) <
'01/01/06', 99999999) order by cur_date desc, some_column desc limit
1;

this will give you the highest value of some_column on the abitrarily
chosen date 01/01/06 (assuming all values of some_column are less than
99999999).

Merlin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Fuhr 2006-03-09 19:26:10 Re: NULL TIMESTAM problem
Previous Message Chris Kratz 2006-03-09 18:49:41 Re: multi-column aggregates