get highest number

[Gonz Berger]

you are right. So I will have to live with it or rethink my database id concept. 

Thanks, gonzberg

-------- Original-Nachricht --------
> Datum: Wed, 14 May 2008 16:22:48 +0100
> Von: "Michael Kay" <http://x-query.com/mailman/listinfo/talk>
> An: http://x-query.com/mailman/listinfo/talk, "\'Wolfgang\'" <http://x-query.com/mailman/listinfo/talk>
> CC: http://x-query.com/mailman/listinfo/talk
> Betreff: RE:  get highest number

> > 
> > 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.
> 
> I doubt that would help. Your application would have to access the
> attribute
> nodes, which would incur the IO cost.
> > 
> > > 
> > > 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.
> 
> Thanks for the info. Obvious, when you think about it. 
> 
> Michael Kay
> http://www.saxonica.com/ 
> 
> _______________________________________________
> 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