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

Re: xpath not a good replacement for xpath_string

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>,<pgsql(at)mohawksoft(dot)com>
Cc: "PostgreSQL" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: xpath not a good replacement for xpath_string
Date: 2009-07-28 20:06:48
Message-ID: 4A6F14080200002500028E78@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)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(at)postgresql(dot)org so that the deficiency can be
addressed."
 
http://www.postgresql.org/docs/8.4/interactive/xml2.html#AEN115231
 
-Kevin

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-07-28 20:08:58
Subject: Deferred uniqueness versus foreign keys
Previous:From: Andrew DunstanDate: 2009-07-28 20:00:55
Subject: Re: xpath not a good replacement for xpath_string

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