From: | Steve Atkins <steve(at)blighty(dot)com> |
---|---|
To: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: new border setting in psql |
Date: | 2008-08-25 18:43:48 |
Message-ID: | E39BD42B-595D-4E37-BD3C-9805A2BCE926@blighty.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Aug 24, 2008, at 6:16 AM, Merlin Moncure wrote:
> On Sun, Aug 24, 2008 at 2:00 AM, D'Arcy J.M. Cain <darcy(at)druid(dot)net>
> wrote:
>> On Sat, 23 Aug 2008 14:57:50 -0400
>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Also, having now looked at the proposed patch, it seems clear that
>>> it
>>> isn't addressing the issue of quoting/escaping at all; so I wonder
>>> how
>>> this can be considered to be a safely machine-readable format.
>>
>> It's not a machine readable format. It is a simple display with more
>> border lines. Just like "border 2" is like "border 1" with more
>> border
>> lines. I'm just following the progression.
>
>
> Personally I think it's rather nice to be able to have some extra
> flexibility in how psql prints out data. Maybe, instead of the dry
> and uninformative 'border 2', there could be a set of ouput control
> options. Maybe I want the text aligned but with no border for
> example.
Or maybe you want an external filter that eats csv or xml and excretes
what you want to see on the screen.
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2008-08-25 19:19:55 | Re: IN, BETWEEN, spec compliance, and odd operator names |
Previous Message | Joshua Drake | 2008-08-25 18:05:21 | Re: initdb change |