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-31 23:36:13 |
Message-ID: | 87hc3fkpzm.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:
> In any case, the results are the same as GROUPing BY from the data
> source.
> +-------------+---------+
> | Assignment | Average |
> +-------------+---------+
> | Assignment1 | 94.67 |
> | Assignment2 | 90.33 |
> | Assignment3 | 86.67 |
> +-------------+---------+
>
> A crosstab is not but a presentational transform of the data set. Any
> information you would eventually need can be taken from the original
> data source, one way or another. That's why dynamic-column crosstab are
> not a problem, and the DBMS should not worry about providing the
> information about the columns, maybe by simply not allowing the
> dynamic-column ones in subqueries.
What about a WHERE clause like
WHERE P1 > P2
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
From | Date | Subject | |
---|---|---|---|
Next Message | Cliff Pratt | 2009-01-31 23:47:53 | Re: [GENERAL] Encoding problem using pg_dumpall |
Previous Message | Andreas Wenk | 2009-01-31 23:16:58 | ALTER TABLE with TYPE serial does not work |