Sorry for resending, I forgot to add 'pgsql-hackers' to CC.
-------- Original Message --------
Subject: Re: [HACKERS] Native XML
Date: Sun, 27 Feb 2011 23:18:03 +0100
From: Anton <antonin(dot)houska(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
On 02/27/2011 04:45 PM, Tom Lane wrote:
> Anton <antonin(dot)houska(at)gmail(dot)com> writes:
>> I've been playing with 'native XML' for a while and now wondering if
>> further development of such a feature makes sense for Postgres.
>> Unlike 'libxml2', the parser uses palloc()/pfree(). The output format is
>> independent from any 3rd party code.
> Hmm, so this doesn't rely on libxml2 at all? Given the amount of pain
> that library has caused us, getting out from under it seems like a
> mighty attractive idea. How big a chunk of code do you think it'd be
> by the time you complete the missing features?
> regards, tom lane
Right, no dependency, everything coded from scratch.
For the initial stable version, my plan is to make the parser conform to
the standard as much as possible and the same for XMLPath / XMLQuery.
(In all cases the question is which version of the standard to start at.)
Integration of SQL & XML data in queries is my primary interest. I
didn't really think to re-implement XSLT. For those who really need to
use XSLT functionality at the database level, can't the API be left for
Also I'm not sure if document validation is necessary for the initial
version - I still see a related item on the current TODO list.
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2011-02-27 22:40:46|
|Subject: Re: Exposing an installation's default value of
|Previous:||From: Josh Berkus||Date: 2011-02-27 22:17:49|
|Subject: Re: WIP: cross column correlation ...|