Re: Proposal: new border setting in psql - Mailing list pgsql-hackers

From D'Arcy J.M. Cain
Subject Re: Proposal: new border setting in psql
Date
Msg-id 20080821231824.49744c48.darcy@druid.net
Whole thread Raw
In response to Re: Proposal: new border setting in psql  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Proposal: new border setting in psql  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-hackers
On Thu, 21 Aug 2008 21:19:58 -0400
Alvaro Herrera <alvherre@commandprompt.com> wrote:
> Tom Lane escribió:
> > There's still the question of whether this covers any needs that aren't
> > met just as well by XML or CSV output formats.
>
> I think it does -- I used to use the Latex output format for easy cut'n
> pasting.  ReST sounds like it serves the same purpose.  If I had had to
> use conversion to XML, it would have been rather painful.

ReST is nice because it's almost plain text.  In fact, a ReST document
source can easily be read raw.

> What I wonder is whether this should be a border setting or a format
> setting.

I don't see it as a format for two reasons.  First, it isn't really a
different format.  It's just the same format as "border 2" with a few
extra lines.  Second, and following from the first, it's such a logical
progression from "border 0" to the proposed "border 3" that that syntax
makes more sense.  In fact, the guide is inches away from describing
this behaviour already.

Besides, making it a border option adds 12 lines to the code, 5 of
which are blank.  I wouldn't want to think about the changes if it was
a different setting.

--
D'Arcy J.M. Cain <darcy@druid.net>         |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Does anything dump per-database config settings? (was Re: ALTER DATABASE vs pg_dump)
Next
From: "Pavel Stehule"
Date:
Subject: Re: proposal sql: labeled function params