get highest number

[John Snelson]

Michael Kay wrote:
>> this makes it slightly faster, but still takes around 30 seconds...
>>
>> Then it is probably better to retieve all IDs and to process 
>> the max value in my application afterwards.
> 
> 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.

I can imagine all sorts of reasons. Maybe //@id is an index lookup, but 
max(//@id) involves looking up the value of the "id" attribute in the 
database.

What XQuery implementation is being used here?

John

-- 
John Snelson, Oracle Corporation            http://snelson.org.uk/john
Berkeley DB XML:            http://oracle.com/database/berkeley-db/xml
XQilla:                                  http://xqilla.sourceforge.net