RE: key(). ( Re: Saxon VS XT )
> Funny how this is the similar to what you are talking > about: by analyzing the XSLT a XSLT engine should be > able to decide what hash tables/indexes to build for a > fast execution of the transformation. I'm inclined to agree. xsl:key and the key() function seems to hark back to pre-relational days where access paths were all defined explicitly by the programmer. SQL allows you to explicitly create an index (using CREATE INDEX) but it doesn't allow the query to be written differently depending on whether there is an index or not, it relies on the optimiser to detect where indexes will be useful to the query. That's no excuse for not implementing the facility now that it's been specified, though! But if I ever have time, it would be nice to experiment with automatic creation and use of keys based on the actual XSL. An obvious and trivial example is to index elements by name whenever you see "//X" written somewhere in the stylesheet. Mike Kay XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
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