From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [patch] Proposal for \rotate in psql |
Date: | 2015-09-17 18:47:14 |
Message-ID: | CAFj8pRCWqWT-dVbNRR4JAyWu=BheB3ZzXSfE6vYUNiaj4wfEHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
2015-09-16 11:35 GMT+02:00 Daniel Verite <daniel(at)manitou-mail(dot)org>:
> Hi,
>
> This is the 2nd iteration of this patch, for comments and review.
>
>
>
>
my comments:
1. I don't understand why you are use two methods for sorting columns
(qsort, and query with ORDER BY)
2. Data column are not well aligned - numbers are aligned as text
3. When data are multiattribute - then merging together with space
separator is not practical
* important information is lost
* same transformation can be done as expression, so this feature is
useless
Is possible to use one cell per attribute (don't do merge)?
DATA QUERY: SELECT dim1, dim2, sum(x), avg(x) FROM .. GROUP BY dim1, dim2
and result header of rotate can be
DIM1 | dim2_val1/sum | dim2_val1/avg | dim2_val2/sum | dim2_val2/avg | ...
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-09-17 20:13:12 | Re: On-demand running query plans using auto_explain and signals |
Previous Message | Robert Haas | 2015-09-17 18:44:00 | Re: numbering plan nodes |