Skip site navigation (1) Skip section navigation (2)

xpath not a good replacement for xpath_string

From: pgsql(at)mohawksoft(dot)com
To: "PostgreSQL" <pgsql-hackers(at)postgresql(dot)org>
Subject: xpath not a good replacement for xpath_string
Date: 2009-07-28 19:21:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Sorry to bring this up, I know you've been fighting about XML for a while.

Currently, I am using XML2 functionality and have tried to get the newer
XPath function to work similarly, but can't quite seem to do it.

I think the current xpath function is too limited. (The docs said to post
problems to hackers if I have an issue.)

For instance, we have a web application that uses java with an XML class
serializer/deserializer Xstream. It creates XML that looks like this:


My current strategy is to use xml2 as:

select xpath_string(datum, E'/com\.company\.local\.myclass/uuid) as uuid
from table;

Which produces a usable:

I have been trying to use xpath
select xpath(E'/com\.company\.local\.myclass/uuid', XMLPARSE(CONTENT
datum)) as uuid from table;

Which produces an unusable:


pgsql-hackers by date

Next:From: David E. WheelerDate: 2009-07-28 19:22:34
Subject: Re: When is a record NULL?
Previous:From: Tom LaneDate: 2009-07-28 19:15:50
Subject: Re: WIP: Deferrable unique constraints

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group