Re: XML ouput for psql

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: XML ouput for psql
Date: 2003-03-07 13:35:08
Message-ID: 303E00EBDD07B943924382E153890E5434A927@cuthbert.rcsinc.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> A larger point is that this is still a protocol revision; pretending
it
> ain't is just willful obscurantism. You can tell it's a protocol
revision
> because you will need to rewrite client-side libraries to take
advantage
> of it. If we try to look the other way and pretend it isn't one, then
> we'll just be incurring pain --- the most obvious pain being that it
> will be hard for those client libraries to tell whether the protocol
> extension is supported or not.

Is it at all worth considering returning an xml document as a scalar?
In most cases when I'm extracting constructed documents from the backend
I would not be using psql to do any processing beyond executing the
query. Also, if at some point the backend learns to return more complex
documents than simple table mappings, this does not complicate the
protocol or the client libs.

As for schemas, they could be manifestly requested by the query. For
simplicity, they could be inlined into the document, returned instead of
(think explain...), or as a separate column.

Merlin

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-03-07 13:40:58 Re: My contract has been renewed
Previous Message Adam Harnett 2003-03-07 13:15:34