Re: [patch] Proposal for \rotate in psql

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(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 20:56:02
Message-ID: CAFj8pRBoMpVHYUGZ+-VfLEdkAi3rQBNjYbnr-OJHvnwP8tgeag@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2015-11-05 17:17 GMT+01:00 Joe Conway <mail(at)joeconway(dot)com>:

> On 11/04/2015 10:46 PM, Pavel Stehule wrote:
> > 2015-11-05 7:39 GMT+01:00 Craig Ringer wrote:
> > 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.
>
> Hey, I resemble that remark ;-)
>

I am sorry, Joe - no any personal attack - I'll pay a beer for you if you
visit Prague :)

Pavel

>
> > When we support PIVOT/UNPIVOT - the crosstab function will be
> > obsolete. It is not often used command.
>
> But agreed, once we have proper support for PIVOT built into the
> grammar, the entire tablefunc extension becomes obsolete, so perhaps
> overloading \crosstab is not so bad.
>
> Joe
>
> --
> Crunchy Data - http://crunchydata.com
> PostgreSQL Support for Secure Enterprises
> Consulting, Training, & Open Source Development
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2015-11-05 20:59:13 Re: [patch] Proposal for \rotate in psql
Previous Message Peter Geoghegan 2015-11-05 20:55:09 Re: Brain fade in gin_extract_jsonb_path()