Re: [patch] Proposal for \crosstabview in psql - Mailing list pgsql-hackers

From Daniel Verite
Subject Re: [patch] Proposal for \crosstabview in psql
Date
Msg-id f61d2f53-2a00-4134-a77b-8bb2c2fbbd66@mm
Whole thread Raw
In response to Re: [patch] Proposal for \crosstabview in psql  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
    Alvaro Herrera wrote:

> Also, what about the business of putting "x" if there's no third column?
> Three months from now some Czech psql hacker will say "we should use
> Unicode chars for this" and we will be forever stuck with \pset
> unicode_crosstab_marker to change the character to a ☑ BALLOT BOX WITH
> CZECH.  Maybe we should think that a bit harder -- for example, what
> about just rejecting the case with no third column and forcing the user
> to add a third column with the character they choose?  That way you
> avoid that mess.

Yes,  that implicit "X" with 2 column resultsets is not essential, it may
be removed without real damage.

About the possible suggestion to have a \pset unicode_crosstab_marker,
my opinion would be that it's not important enough to justify a new
\pset setting.


Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters)
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: schema PL session variables