From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [patch] Proposal for \rotate in psql |
Date: | 2015-09-08 18:13:46 |
Message-ID: | CA+TgmobVE1B1GRZM4vHc1UkyP2PafMyK-tw11yfr9ogc_L0N7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 8, 2015 at 2:10 PM, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Tue, Sep 8, 2015 at 1:38 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Mon, Sep 7, 2015 at 5:08 PM, David G. Johnston
>> <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>> > Given the role that psql performs I do think \rotate to be the least
>> > problematic choice; I concur that avoiding \pivot is desirable due to
>> > SQL's
>> > usage.
>>
>> I can't agree. Rotating a matrix has a well-defined meaning, and this
>> does something that is not that.
>
> Even though the input data is a table and not a matrix?
Yes, I think rotating a table also has a pretty well-defined meaning.
> Do you have an
> alternative choice you'd like to defend?
Not particularly. If everybody picks one thing they like and argues
strenuously for it, we'll never get anywhere. I think it's enough to
say that I think this particular choice isn't the best. It's not as
if no other suggestions have been made.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-09-08 18:15:32 | Re: Separating Buffer LWlocks |
Previous Message | David G. Johnston | 2015-09-08 18:10:10 | Re: [patch] Proposal for \rotate in psql |