I have removed the XML TODO item:
* Add XML output to pg_dump and COPY We already allow XML to be stored in the database, and XPath queries can be used
onthat data using /contrib/xml2. It also supports XSLT transformations.
---------------------------------------------------------------------------
Josh Berkus wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073