Re: Proposal: new border setting in psql

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: new border setting in psql
Date: 2009-01-12 17:19:51
Message-ID: 200901121719.n0CHJpb07698@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > My vote goes for 1.
>
> > I wonder why you think it's impossible. Is it because you must scan
> > the whole table before being able to print any of it? (For example to
> > add extra alignment for the escaping backslashes in a way that doesn't
> > render it invalid.) Note that psql already does that in aligned mode,
> > to determine the wide of the columns.
>
> Hmm. If RST is really that brain-damaged, the problem here is that it's
> going to take a very large patch to make it work. It's not going to be
> a "border" option but a separate output mode like latex or html. And
> then we have to get into the discussion of whether there's really enough
> demand for this to justify carrying such a large chunk of code.
>
> In any case, my vote is for either 0 or 1; I'm unimpressed by anything
> that emits RST-except-we-skipped-all-the-hard-parts.

Yep, that is my analysis as well. If you want a pretty ReST-like
output, that can be added later.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-01-12 17:20:23 Re: Recovery Test Framework
Previous Message Tom Lane 2009-01-12 17:19:14 Re: Recovery Test Framework