From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Undisclosed(dot)Recipients: ; |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: patches for items from TODO list |
Date: | 2005-05-21 02:41:44 |
Message-ID: | 200505201941.44205.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Folks,
> - The COPY -> XML transformation is trivial -- it would be easy for
> clients to roll their own. At the same time, there is no standard or
> canonical XML representation for COPY output, and I can easily imagine
> different clients needing different representations. So there is limited
> value in providing a single, inflexible backend implementation.
I'm going to second Neil here. This feature becomes useful *only* when there
is a certified or de-facto universal standard XML representation for database
data. Then I could see a case for it. But there isn't.
Feel free to throw it on pgFoundry, though.
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-21 03:23:06 | Re: patches for items from TODO list |
Previous Message | Josh Berkus | 2005-05-21 02:37:39 | Re: Two-phase commit issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-05-21 03:16:40 | Re: WIP XLog Switch |
Previous Message | Bruce Momjian | 2005-05-21 02:30:51 | Re: patches for items from TODO list |