| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Teodor Sigaev" <teodor(at)sigaev(dot)ru>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [patch] Proposal for \crosstabview in psql |
| Date: | 2016-02-09 14:54:03 |
| Message-ID: | f61d2f53-2a00-4134-a77b-8bb2c2fbbd66@mm |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-02-09 14:58:15 | Re: proposal: schema PL session variables |
| Previous Message | Noah Misch | 2016-02-09 14:45:55 | Re: More thorough planning for OLAP queries (was: [PATCH] Equivalence Class Filters) |