Hi Joseph,
that's probably a bug in the SQL parser. Could you please created a jira issue
for this?
as a workaround you can enclose the underscore in double quote, that should
work.
regards
marcel
Ottinger, Joseph wrote:
Incidentally... Is there any real reason that "_" isn't lexically
acceptable for a node name?
-----Original Message-----
From: David Nuescheler [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 10:32 AM
To: [email protected]
Subject: Re: count of nodes?
hi joe,
thanks for the feedback.
i could imagine that there is still quite a bit of room for performance
improvement for queries that are just interested in the number of nodes
that match, so if you run into performance issues please be sure to let
us know.
regards,
david
On 4/19/07, Ottinger, Joseph <[EMAIL PROTECTED]> wrote:
Done, and it works - confirmed kill. However...
What I did in the absence of taking the time to learn Xpath well
enough to get the actual correct query down was walk the tree
recursively. For a simple tree:
<foo>
<bar>
<baz />
</bar>
<bletch />
</foo>
... The recursive method was faster, ever-so-slightly. I don't have a
dataset large enough to test more complicated trees yet; when I do,
I'll let you know what I find.
-----Original Message-----
From: David Nuescheler [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 9:03 AM
To: [email protected]
Subject: Re: count of nodes?
Hi Joe,
But wouldn't getSize() on the getNodes() call only get the immediate
child nodes?
No. It would include everything that matched your query which would
include all the nodes in the QueryResult.
So the node iterator returned from QueryResult.getNodes() will contain
all the nodes that matched the query.
In your case:
/jcr:root/foo//*
... will return the nodes
/foo/bar
/foo/bar/baz
... and the QueryResult.getNodes().getSize() should return 2
I'll keep investigating - I still find the Xpath rules a problem. :/
What do you find a problem about it?
Do you prefer the SQL syntax?
regards,
david
