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

Re: xpath not a good replacement for xpath_string

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql(at)mohawksoft(dot)com
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: xpath not a good replacement for xpath_string
Date: 2009-07-29 03:32:32
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers

pgsql(at)mohawksoft(dot)com wrote:
> Another thing that is troubling is that more exotic types do not seem to
> be supported at all. For instance, in my example I used uuid, and if one
> substitutes "uuid()" for "text()" that doesn't work.

text() is an XPath function, with well defined semantics that have no 
relation at all to types in a PostgreSQL sense. uuid() of course has no 
meaning in an XPath expression.



In response to

pgsql-hackers by date

Next:From: Josh WilliamsDate: 2009-07-29 03:38:36
Subject: Re: multi-threaded pgbench
Previous:From: Tom LaneDate: 2009-07-29 01:52:29
Subject: Re: Review: Revise parallel pg_restore's scheduling heuristic

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