Torgeir Veimo-2 wrote:
>
> 2009/5/20 AdamR <[email protected]>:
>>
>> Jukka Zitting wrote:
>>>
>>> What does the troublesome query look like?
>>
>> The queries are fairly straight forward, for example:
>> /jcr:root/mynode//element(*, my:nodetype) order by @myProp ascending. I
>> then
>> iterate through a hundred or so nodes from the resulting NodeIterator
>> (which may contain many thousand results in total) and access various
>> properties and child nodes.
>
> Is the order by clause necessary?
>
> --
> -Tor
>
>
Yes, but previosu posts that I've come across indicate that the order by
clause is not exepnsive and can even improve the performance of the query.
See here:
http://www.nabble.com/Explanation-and-solutions-of-some-Jackrabbit-queries-regarding-performance-td15028655.html
http://www.nabble.com/Explanation-and-solutions-of-some-Jackrabbit-queries-regarding-performance-td15028655.html
--
View this message in context:
http://www.nabble.com/Caching-performance-issue-%28urgent-help-required-please%21%29-tp23592190p23633641.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
