Re: new unicode table border styles for psql

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: 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-26 19:23:32
Message-ID: CAFj8pRDdoLR3v5+aJpbsPDQL-BZtFyu=McYQbsah1NHF1bar3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2013/11/26 Peter Eisentraut <peter_e(at)gmx(dot)net>

> On 11/22/13, 3:26 AM, Pavel Stehule wrote:
> > website is related to patch for 9.3 (I add note there)
> >
> > patch for 9.4 is fixed - and now with small doc
>
> I think it would help if we considered the new border styles and the new
> line styles separately.
>
> I don't find the new border styles to be particularly useful. They just
> use up vertical screen space, which is usually more precious than
> vertical space. Is there a situation where you would find these styles
> to be more useful than the existing ones? Keep in mind that pset is
> usually set permanently, so it wouldn't be practical to use a different
> border style depending on how the query results shape up (like \x auto).
>
> 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.
>

+1

Pavel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-11-26 19:32:11 Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Previous Message David Johnston 2013-11-26 19:14:06 Re: why semicolon after begin is not allowed in postgresql?