From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | alvarezp(at)alvarezp(dot)ods(dot)org |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Pet Peeves? |
Date: | 2009-01-30 11:05:20 |
Message-ID: | 87tz7hm4un.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Octavio Alvarez <alvarezp(at)alvarezp(dot)ods(dot)org> writes:
> Now, last time I checked, Postgresql lacked an SQL extension to create
> crosstab queries. Even though contrib have some helper functions, they
> are not official and work only if the number of columns is actually
> predefined. For instance if you want to create a query to produce
> different paths to go through a graph, being represented by 1 arc per
> record, you will never be able to predict the final number of columns
> (path steps) needed for the crosstab without doing the whole query one
> extra time to get the max(step).
Is it the hierarchical query ability you're looking for or pivot?
The former we are actually getting in 8.4.
AFAIK even in systems with pivot you still have to declare a fixed list of
columns in advance anyways. Do you see a system where it works differently?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Katson | 2009-01-30 11:09:18 | Plproxy functions inside transactions and Pl/pgsql exception handling |
Previous Message | Octavio Alvarez | 2009-01-30 09:23:04 | Re: Pet Peeves? |