Johannes Neubauer wrote:
Hi,
Michael Kay schrieb:
| This actually raises an interesting point that I hadn't thought of
before.
| then I think that in Saxon, one index is going to be built for each key
| definition, the indexes will all be searched, and duplicates in the
result
| will then be eliminated. So although it does no functional harm to repeat
| the key declaration, there will be a performance cost! This applies
| regardless whether you do xsl:include or xsl:import.
Oh, that's a behaviour I didn't expect. Why don't you look at the key
definition and if there already is a key definition with that name, use
and match attributes, no new index is created? Will you change this in
future releases?
This is a useful feature - you can use two <xsl:key > elements to
instruct the processor to put two different sets of nodes and values
into the same index.
# r
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--
Ronan Klyne
Business Collaborator Developer
Tel: +44 01189 028518
ronan(_dot_)klyne(_at_)groupbc(_dot_)com
www.groupbc.com
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--