get highest number

[David Carlisle]

> Or switch to a better XQuery processor. I find it hard to imagine why a
> product should take noticeably longer to evaluate max(//@id) than it takes
> to evaluate //@id.


if the input is typed then it's possible that  max(//@id) could be doing
locale-sensitive lexicographic comparison, which it would slow it down (a
bit), in which case doing  max(//number(@id)) might help. But on the
other hand if the id values are numeric they didn't ought to be typed
with a (subtype of) xsd:string rather than a numeric type, so this is
just a blind and probably wrong guess...

David


________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________