Message-ID: <18738.24.91.171.78.1138561487.squirrel@mail.mohawksoft.com>
In-Reply-To: <43DD0997.7050104@dunslane.net>
References: <16397.24.91.171.78.1138558881.squirrel@mail.mohawksoft.com>
	<43DD0997.7050104@dunslane.net>
Date: Sun, 29 Jan 2006 14:04:47 -0500 (EST)
Subject: Re: Want to add to contrib.... xmldbx
From: "Mark Woodward" <pgsql@mohawksoft.com>
To: "Andrew Dunstan" <andrew@dunslane.net>
Cc: pgsql-hackers@postgresql.org
User-Agent: SquirrelMail/1.4.5
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

>
> [removing -patches since no patch was attached]
> This sounds highly specialised, and probably more appropriate for a
> pgfoundry project.
>
> In any case, surely the whole point about XML is that you shouldn't need
> to contruct custom parsers. Should we include a specialised parser for
> evey XML dialect someone might want to store in the database?

XML is not really much more than a language, it says virtually nothing
about content. Content requires custom parsers.

While I understand the notion that we don't want to have a custom parser
for every XML data spec, I did commit the xmldbx extension into the PHP
extensions.

MySQL has great street cred because it is very well integrated with PHP.
This extension may appeal to PHP users and make it more enticing to
PostgreSQL instead.