From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
---|---|
To: | "David Fetter" <david(at)fetter(dot)org> |
Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [patch] A \pivot command for psql |
Date: | 2015-08-11 15:49:01 |
Message-ID: | 3900e08c-b218-4c5d-93a9-31070f10b9d0@mm |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Fetter wrote:
> Second, if we put this feature as-is in psql, we're stuck supporting
> it in psql until the end of time, even if (when, I believe) we have a
> fuller and likely not perfectly compatible feature on the back-end.
To me, doing \pivot in psql vs PIVOT in the backend is a false
dichotomy, both would be desirable to have in any order.
Having PIVOT in SQL is more important because it will help in a
broader range of cases.
But, even if I fail to be convincing on this, it will still be
much easier in a psql context to just type \pivot than turning a
non-pivot query into a pivoted equivalent, even if we achieve the
best possible (in ease of use) server-side SQL implementation.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-08-11 16:04:48 | Re: GinPageIs* don't actually return a boolean |
Previous Message | Andres Freund | 2015-08-11 15:46:51 | Re: GinPageIs* don't actually return a boolean |