get highest number

[gonzberg at gmx.de]

Thank you all,
as Wolfgang said, I use eXist. If I get you right, Wolfgang, my solution would be to do the max/highest evaluation in my application. 

All the best, gonzberg

-------- Original-Nachricht --------
> Datum: Wed, 14 May 2008 16:11:24 +0200
> Von: Wolfgang <http://x-query.com/mailman/listinfo/talk>
> An: 
> CC: http://x-query.com/mailman/listinfo/talk
> Betreff: Re:  get highest number

> > 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 Gonzberg is using eXist (I remember other posts on the corresponding 
> lists), I can explain the difference: evaluating //@id is entirely 
> index-based (as John already suspected). Compared to this, max(//@id) 
> requires access to the actual attribute nodes, which generates a lot 
> more IO. Better index-support for aggregate functions would help here, 
> but that's work in progress.
> 
> Wolfgang
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

-- 
249 Spiele für nur 1 Preis. Die GMX Spieleflatrate schon ab 9,90 Euro.
Neu: Asterix bei den Olympischen Spielen: http://flat.games.gmx.de