From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Szymon Guz <mabewlun(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: new unicode table border styles for psql |
Date: | 2013-11-29 07:28:01 |
Message-ID: | CAFj8pRCA7H2ndgtWmaiYKX50YQThre=v+bQfpCbTuJyRig_sPA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2013/11/28 Robert Haas <robertmhaas(at)gmail(dot)com>
> On Tue, Nov 26, 2013 at 2:08 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > Now for the linestyles. I can see how some of them are attractive, but
> > several of them have poor aesthetics, I think. I don't see a reason to
> > accept 7 new styles just for fun. If I had to choose, I'd consider
> > -double1 and -double4 to be acceptable.
>
> I'm confused why we need ANY of these. What problem are we solving
> that the existing unicode style doesn't already solve? We could
> doubtless invent an infinite or at least very large number of
> plausible ways to border psql output, but I don't see that as
> something that has value.
>
It has primary aesthetic value - not much more (similar value has original
unicode border)
With this patch you can prepare a little bit nicer (plain text) reports
without using special software. And a implementation is really simply - so
it offer sympathetic benefit without any cost.
Regards
Pavel
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-11-29 07:33:04 | Re: new unicode table border styles for psql |
Previous Message | Rajeev rastogi | 2013-11-29 06:41:59 | Re: TODO: Split out pg_resetxlog output into pre- and post-sections |