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 4A6F14080200002500028E78@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
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> wrote:
> This is really a usage question, which doesn't belong on -hackers.
Perhaps this sentence in the 8.4.0 docs should be amended or removed?:
"If you find that some of the functionality of this module is not
available in an adequate form with the newer API, please explain your
issue to pgsql-hackers@postgresql.org so that the deficiency can be
addressed."
http://www.postgresql.org/docs/8.4/interactive/xml2.html#AEN115231
-Kevin


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: xpath not a good replacement for xpath_string
Next
From: Tom Lane
Date:
Subject: Deferred uniqueness versus foreign keys