Thursday, March 4. 2010XSLT working properly in Postgres at lastTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Andrew,
This is really neat. I have found myself doing a lot xslt programming too. In PostGIS we use it to generate tests scripts from the PostGIS documentation and also generate the PostgreSQL function comments for each PostGIS function. Mapserver is moving toward XML as standard for their map template. And of course GIS data is just replete with XML formed data GML, KML, GPX etc. This will make it much simpler to load select data directly in without too much fuss. Does the xslt processor in PostgreSQL by chance support the xsl 2.0 standard. I've been shying away from that since a lot of parsers I use seem to be stuck on the 1.0 standard. But if I could do all my work in the database, that would be really sweet.
The docs say the xml2 module is deprecated and going to be removed (http://www.postgresql.org/docs/current/static/xml2.html) .. so what is recommended now? The built-in stuff does not do xslt.
@Regina it is xslt 1.0 because of libxml2.
The plan as I understand it is to remove the module when most or all of the functionality is incorporated in the Postgres core. Recently there were suggestions to remove the module now. The work that Tom has done to fix it has allayed that danger.
Hi,
actually we are using xslt_process() for ages now (in a 8.3 version) and it is running on the productive server processing about 100k documents per day (generating emails with HTML and text parts) without any seen problem. What exactly was not working there except, probable memory leaks?
If you used it in conjunction with the builtin XML type you got core dumps, IIRC. If you just kept your XML as text columns it worked fine. But of course we want it to work with the builtin XML type.
|
My Links etcCalendar
QuicksearchArchivesCategoriesBlog Administration |
|||||||||||||||||||||||||||||||||||||||||||||||||