[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
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
