Re: [patch] Proposal for \rotate in psql

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Joe Conway <mail(at)joeconway(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [patch] Proposal for \rotate in psql
Date: 2015-11-05 06:46:47
Message-ID: CAFj8pRB1B1pEndGCBb9LHhQfaxrT3u+0kz5+YN_-FgLjYH_s=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2015-11-05 7:39 GMT+01:00 Craig Ringer <craig(at)2ndquadrant(dot)com>:

> On 5 November 2015 at 05:22, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
>
> > If I understand to text on wiki, the name is used for tool, that can do
> > little bit more things, but it is often used for this technique (so it is
> > much better than "rotate"). I don't understand well, why "crosstab" is
> too
> > wrong name. This is pretty similar to COPY - and I know, so in first
> minutes
> > hard to explain this difference between COPY and \copy to beginners, but
> > after day of using there is not any problem.
>
> I see constant confusion between \copy and COPY. It's a really good
> reason NOT to overload other psql commands IMO.
>

but crosstab is one old function from old extension with unfriendly design.
When we support PIVOT/UNPIVOT - the crosstab function will be obsolete. It
is not often used command.

Regards

Pavel

>
> --
> Craig Ringer http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Torsten Zühlsdorff 2015-11-05 07:59:37 Re: September 2015 Commitfest
Previous Message Craig Ringer 2015-11-05 06:39:59 Re: [patch] Proposal for \rotate in psql