On Jul 29, 2009, at 12:12 PM, Andrew Dunstan wrote:
As I said upthread, I think we can easily provide some extra
convenience functions which will do what you want. The only thing I
was really arguing about was the function name for such a gadget.
+1.
xpath_string does seem unfortunate, but
On Tuesday 28 July 2009 23:30:23 pg...@mohawksoft.com wrote:
The thing that perplexed me was that it was not obvious from the docs how,
exactly, to get the functionality that was simple and straight forward in
XML2.
I continue to be in favor of adding
xpath_string
xpath_number
xpath_boolean
On Tuesday 28 July 2009 23:30:23 pg...@mohawksoft.com wrote:
The thing that perplexed me was that it was not obvious from the docs
how,
exactly, to get the functionality that was simple and straight forward
in
XML2.
I continue to be in favor of adding
xpath_string
xpath_number
pg...@mohawksoft.com wrote:
On Tuesday 28 July 2009 23:30:23 pg...@mohawksoft.com wrote:
The thing that perplexed me was that it was not obvious from the docs
how,
exactly, to get the functionality that was simple and straight forward
in
XML2.
I continue to be in favor of adding
select datum form objects were key ='GUID' and
xpath_string(datum,E'foo/bar') = 'frobozz';
The logic of the function seems is that it is intended to use extracted
XML within a query. The new xpath functionality seems not to be designed
to facilitate this, requiring a pretty arcane query
pg...@mohawksoft.com wrote:
Well, the API is there, it is where, I guess, PostgreSQL is going, but I
think, philosophically, the API needs to see the XML contained within SQL
columns as being able to represent variable and optional columns in object
oriented environments easily. The harder it
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
On Tue, Jul 28, 2009 at 3:21 PM, pg...@mohawksoft.com wrote:
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
pg...@mohawksoft.com wrote:
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.
Andrew Dunstan and...@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
Kevin Grittner wrote:
Andrew Dunstan and...@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
Andrew Dunstan and...@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
Andrew Dunstan and...@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
On Tuesday, July 28, 2009, pg...@mohawksoft.com wrote:
Andrew Dunstan and...@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
pg...@mohawksoft.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
15 matches
Mail list logo
