RE: Possible new key() function (Was: Re: Finding the

> > In this case xsl:key will know in advance about all possible
> > operators and could build the indexes in an optimal way in order to
> > guarantee most efficient key() performance.

The more I listen to this discussion, the more convinced I am that SQL got
it right and XSLT got it wrong: keys should be used implicitly, behind the
scenes, when the optimizer decides and not when the user decides. Rather
than having new variants on the key() function, we should do away with the
function entirely.

Mike Kay 

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list