|
[XQuery Talk Mailing List Archive Home] [By Date] [By Thread] [By Subject] [By Author] [Recent Entries] [Reply To This Message] get highest numberIvan Bogouchev ivan.bogouchev at gmail.comWed May 14 16:33:33 PDT 2008
> > > > 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. Or maybe it does some sort of lazy evaluation ... > > > 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 -- Ivan
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|






