Subject: RE: [xsl] xsl:for-each efficiency From: "Jim Fuller" <jim.fuller@xxxxxxxxxxxxxxxxxx> Date: Tue, 16 Sep 2003 13:12:29 +0100 |
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.curry@xxxxxxxxxxxx [mailto:andrew.curry@xxxxxxxxxxxx] Sent: 16 September 2003 13:02 To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxx> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Sent: Tuesday, September 16, 2003 1:38 PM Subject: Re: [xsl] xsl:for-each efficiency > On Tuesday 16 Sep 2003 11:24, andrew.curry@xxxxxxxxxxxx wrote: > > Would there be a better way of doing: > > > > <xsl:for-each select="//element[@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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] xsl:for-each efficiency, Jarno . Elovirta | Thread | [xsl] comparing xml documents, Koteswararao Mogili |
Re: [xsl] xsl:for-each efficiency, Mukul Gandhi | Date | Re: [xsl] xsl:for-each efficiency, Tom Schutzer-Weissma |
Month |