Skip site navigation (1) Skip section navigation (2)

OLAP, Aggregates, and order of operations

From: mlw <markw(at)mohawksoft(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: OLAP, Aggregates, and order of operations
Date: 2001-08-23 15:26:42
Message-ID: 3B8520B1.8A9069A1@mohawksoft.com (view raw or flat)
Thread:
Lists: pgsql-hackers
I need to do some OLAP stuff, and I asked previously if there were a way
to pass multiple parameters to an aggrigate function. i.e.:

select mycube(value1, value2, value3) from table group by value1;

I looked through the code and it is non-trivial to do, one would have to
alter the grammar to include a number of parameters, I guess something
like this:

create aggregate (sfunc = myfunct, sfuncnargs=3, stype = int4, basetype1
= int4, basetype2 = int4, ....);

Then change the catalog, and the execution, arrg!

(God I wish I could spend the time I want on PostgreSQL! )

Anyway, short of that....

If I do this:

select mycube(value1) as d1, dimention(value2) as d2, dimention(value3)
as d3 group by value1;

Can I safely assume the following:

(1) mycube() will be called first
(2) Assuming dimention() has no final func, that final func of mycube()
will be called last.




Responses

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2001-08-23 15:36:01
Subject: Re: [PATCHES] encoding names
Previous:From: Peter EisentrautDate: 2001-08-23 15:11:03
Subject: Re: A couple items on TODO

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group