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

From Andrew Dunstan
Subject Re: Proposal: new border setting in psql
Date
Msg-id 48B05A31.7010602@dunslane.net
Whole thread Raw
In response to Re: Proposal: new border setting in psql  ("D'Arcy J.M. Cain" <darcy@druid.net>)
Responses Re: Proposal: new border setting in psql  ("D'Arcy J.M. Cain" <darcy@druid.net>)
Re: Proposal: new border setting in psql  (Hannu Krosing <hannu@krosing.net>)
Re: Proposal: new border setting in psql  (Greg Smith <gsmith@gregsmith.com>)
List pgsql-hackers

D'Arcy J.M. Cain wrote:
> On Thu, 21 Aug 2008 21:04:07 -0400
> "D'Arcy J.M. Cain" <darcy@druid.net> wrote:
>   
>>> There's still the question of whether this covers any needs that aren't
>>> met just as well by XML or CSV output formats.
>>>       
>> Well, we could remove all the display formats except XML.  After all,
>> it can always be converted to any other format.  Of course we wouldn't
>> do that. User convenience is all I'm thinking of.
>>     
>
> Well, Tom has raised a question about its need and Asko has questioned
> whether it should be under a different setting but so far no one has
> outright rejected the proposal.  Does anyone else have an opinion?  I am
> attaching a patch for further review.  
>
>   


In general I think I prefer machine readable formats to be produces by 
the backend so they are available through all clients, not just psql.

That said, this has sufficiently low impact that I'm not going to be 
vastly upset if we let it through.

I think we should probably confine ourselves to output formats that are 
in very wide use or we'll be supporting a vast multitude. CSV and XML 
both qualify here - not sure that ReST does.

cheers

andrew




pgsql-hackers by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: proposal sql: labeled function params
Next
From: "Greg Stark"
Date:
Subject: Re: proposal sql: labeled function params