Prev: Extraneous newlines in logfile from vacuumdb
Next: [HACKERS] pg_read_file() and non-ascii input file
From: Andrew Dunstan on 19 Nov 2009 10:12


Robert Haas wrote:
> On Thu, Nov 19, 2009 at 12:03 AM, Scott Bailey <artacus(a)comcast.net> wrote:
>
>> The nice thing about XMLTABLE is that it adds xquery support. I think the
>> majority of xquery engines seem to be written in Java. XQuilla is C++. I'm
>> not sure if our licensing is compatible, but it I would love the irony of
>> using Berkeley DB XML (formerly Sleepycat) now that its owned by Oracle.
>>
>
> It's very much not compatible. Berkeley DB is not free for commercial
> use. I anticipate that this would be a problem both for commericial
> users of PostgreSQL and also for commercial PostgreSQL forks.
> Besides, that's a lot of code to suck into Postgres to do, uh, a lot
> of things that we already do in other ways.
>
>
>

XQuilla, however, is not Berkely DB. And its license is Apache v2. It is
built on Xerces-C, although it appears at first glance to have less
dependencies that Zorba. I'm not sure how pluggable the XML parser
engine is (or could be made).

cheers

andrew



--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Andrew Dunstan on 21 Nov 2009 11:34


I wrote:
>>
>> The nice thing about XMLTABLE is that it adds xquery support. I think
>> the majority of xquery engines seem to be written in Java. XQuilla is
>> C++. I'm not sure if our licensing is compatible, but it I would love
>> the irony of using Berkeley DB XML (formerly Sleepycat) now that its
>> owned by Oracle.
>>
>>
>
> XQuery is a whole other question. Adding another library dependency is
> something we try to avoid. Zorba <http://www.zorba-xquery.com/> might
> work, but it appears to have its own impressive list of dependencies
> (why does it require both libxml2 and xerces-c? That looks a bit
> redundant.)
>
> Even if we did implement XMLTABLE, I think I'd probably be inclined to
> start by limiting it to plain XPath, without the FLWOR stuff. I think
> that would satisfy the vast majority of needs, although you might feel
> differently. (Do a Google for XMLTABLE - every example I found uses
> plain XPath expressions.)
>
>

I did look at this a bit further. Sadly, XQilla's XSLT support is stated
to be of alpha quality, and missing some quite necessary features (e.g.
xsl:output). That pretty much rules out for now Xerces-C+XQilla as an
alternative xml stack to libxml2+libxslt, ISTM.

cheers

andrew


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

First  |  Prev  | 
Pages: 1 2
Prev: Extraneous newlines in logfile from vacuumdb
Next: [HACKERS] pg_read_file() and non-ascii input file