Message-ID: <43DD0997.7050104@dunslane.net>
Date: Sun, 29 Jan 2006 13:29:43 -0500
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.7.12) Gecko/20050922 Fedora/1.7.12-1.3.1
MIME-Version: 1.0
To: Mark Woodward <pgsql@mohawksoft.com>
CC: pgsql-hackers@postgresql.org
Subject: Re: Want to add to contrib.... xmldbx
References: <16397.24.91.171.78.1138558881.squirrel@mail.mohawksoft.com>
In-Reply-To: <16397.24.91.171.78.1138558881.squirrel@mail.mohawksoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


[removing -patches since no patch was attached]

Mark Woodward wrote:

>I have a fairly simple extension I want to add to contrib. It is an XML
>parser that is designed to work with a specific dialect.
>
>I have a PHP extension called xmldbx, it allows the PHP system to
>serialize its web session data to an XML stream. (or just serialize
>variables) PHP's normal serializer is a non-standard home grown format
>that it impossile to read. The xmldbx format may not be too much easier,
>but I have a format document for it. I also have a PostgreSQL extension
>that can take serialized data and use it in a query, like:
>
>select xmldbx('data.userdata.id', sessions.data);
>
>If the PHP variable has $userdata['id'] set to some varible in its session
>data, it will be returned.
>
>This allows a lot of flexability and a tight integration between
>PostgreSQL and PHP.
>
>
>  
>

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?

cheers

andrew