Re: Proposal: new border setting in psql

From: "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Asko Oja <ascoja(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: new border setting in psql
Date: 2008-08-24 05:42:18
Message-ID: 20080824014218.b85d65b4.darcy@druid.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 23 Aug 2008 14:42:57 -0400
Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> 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.

What do you mean by "machine readable?" XML?

> 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.

It isn't ReST. It just happens that this very simple and logical
progression of the border setting works for ReST. The display stands
on its own. This is not true of machine readable formats like XML. I
guess the question is, why border 2? Border 1 seems to be enough. In
fact border 0 has everything we absolutely need. Why have any borders?

--
D'Arcy J.M. Cain <darcy(at)druid(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2008-08-24 05:59:46 Re: proposal sql: labeled function params
Previous Message Pavel Stehule 2008-08-24 05:38:09 Re: proposal sql: labeled function params