Re: xpath not a good replacement for xpath_string - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: xpath not a good replacement for xpath_string
Date
Msg-id 4A6F194C0200002500028E85@gw.wicourts.gov
Whole thread Raw
In response to Re: xpath not a good replacement for xpath_string  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: xpath not a good replacement for xpath_string  (pgsql@mohawksoft.com)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> wrote:
> in fact the desired functionality is present [...] You just need to
> use the text() function to get the contents of the node, and an
> array subscript to pull it out of the result array.
I just took a quick look, and that didn't jump out at me from the
documentation.  Perhaps there should be an example or two of how to
get the equivalent functionality through the newer standard API, for
those looking to migrate?
Would it make sense to supply convenience SQL functions which map
some of the old API to the new?
-Kevin


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: xpath not a good replacement for xpath_string
Next
From: pgsql@mohawksoft.com
Date:
Subject: Re: xpath not a good replacement for xpath_string