Re: Proposal: new border setting in psql

From: Cédric Villemain <cedric(dot)villemain(at)dalibo(dot)com>
To: "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>
Cc: Greg Smith <gsmith(at)gregsmith(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: new border setting in psql
Date: 2009-01-09 16:15:28
Message-ID: 49677820.9010502@dalibo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

D'Arcy J.M. Cain a écrit :
>
> As Tom has pointed out, ReST has problems beyond our implementation.
> People who use it are aware of these warts. Given that I really think
> that the cleanest solution is to just give them "border 3", don't
> mention ReST in the docs and have it happily work for 95% of the cases
> in a ReST processor.

+1

>
> How about my other proposal under the "Output filter for psql"
> subject? That would let people create parsers as safe as they need
> them. I think that this proposal is still useful for those that need
> something quick and dirty though.
>

Can be interesting, but for my own usage "border=3" will be enough.

- --
Cédric Villemain
Administrateur de Base de Données
Cel: +33 (0)6 74 15 56 53
http://dalibo.com - http://dalibo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAklneBwACgkQo/dppWjpEvxucQCeIuTatyfoEw/TkqAVLK/hI0wq
WkIAn3mt4tnMz3BAjXIJqtmMlj9d4r4l
=Ykl+
-----END PGP SIGNATURE-----

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-01-09 16:20:40 Re: SET TRANSACTION and SQL Standard
Previous Message Tom Lane 2009-01-09 16:15:08 Re: Improving compressibility of WAL files