| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Roger Leigh <rleigh(at)codelibre(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Unicode UTF-8 table formatting for psql text output |
| Date: | 2009-11-23 08:26:18 |
| Message-ID: | 1258964778.23718.4.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On sön, 2009-11-22 at 00:23 -0500, Tom Lane wrote:
> Roger Leigh <rleigh(at)codelibre(dot)net> writes:
> > Attached is an updated patch with a couple of tweaks to ensure output
> > is formatted and spaced correctly when border=0, which was off in the
> > last patch.
>
> Applied wih minor editorialization. Notably, I renamed the
> backwards-compatible option from "ascii-old" to "old-ascii",
> because the original submission failed to preserve the documented
> behavior that the options could be abbreviated to one letter.
What is the plan behind keeping the old format? Are we going to remove
it after one release if no one complains, or are we seriously expecting
that someone has code that actually parses this?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Caleb Cushing | 2009-11-23 08:59:29 | named generic constraints [feature request] |
| Previous Message | Peter Eisentraut | 2009-11-23 07:20:24 | Re: operator exclusion constraints |