depending upon the structure, I find it useful to pass such large files through
a SAX filter. though it may not be appropriate in your case.
cheers, jim
-----Original Message-----
From: andrew(_dot_)curry(_at_)pa(_dot_)press(_dot_)net
[mailto:andrew(_dot_)curry(_at_)pa(_dot_)press(_dot_)net]
Sent: 16 September 2003 13:02
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] xsl:for-each efficiency
Cheers
PA Sport RnD
Andrew Curry
Software Developer
Telephone: 01430 455545
Website: http://www.pa.press.net
PA News Limited:
Bridgegate, Howden, East Yorkshire, DN14 7AE
Registered Office:
PA News Limited, 292 Vauxhall Bridge Road, London SW1V 1AE. Registered in
England No. 3891053
----- Original Message -----
From: "Tom Schutzer-Weissmann" <xsl(_at_)tomweissmann(_dot_)org>
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Tuesday, September 16, 2003 1:38 PM
Subject: Re: [xsl] xsl:for-each efficiency
On Tuesday 16 Sep 2003 11:24,
andrew(_dot_)curry(_at_)pa(_dot_)press(_dot_)net wrote:
Would there be a better way of doing:
<xsl:for-each select="//element[(_at_)element-key = $id]">
</xsl:for-each>
for use over a very very large document?
Yes, use a key:
<xsl:key name="byId" match="element" use="@element-key"/>
...
<xsl:apply-templates select="key('byId',$id)"/>
Tom SW
--
"The facts are hideous, but we must face them" - Bertie Wooster
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list