Re: new unicode table border styles for psql - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: new unicode table border styles for psql
Date
Msg-id 20131128214854.GI5513@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: new unicode table border styles for psql  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: new unicode table border styles for psql  (Robert Haas <robertmhaas@gmail.com>)
Re: new unicode table border styles for psql  (Peter Eisentraut <peter_e@gmx.net>)
Re: new unicode table border styles for psql  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Robert Haas escribió:
> On Tue, Nov 26, 2013 at 2:08 PM, Peter Eisentraut <peter_e@gmx.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.

You know what I think would have some value?  An output style that emits
DocBook markup for tables, something which we could paste on the docs.
(I already use the LaTeX mode to paste in presentation slides.)

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Performance Improvement by reducing WAL for Update Operation
Next
From: Robert Haas
Date:
Subject: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block