This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Alternating table row colors with recursion


> > <xsl:apply-templates select = "//Message[ParentMessageID = '$MID']">
> 
> do you _really_ want to do that? Search the entire document 
> for all the next batch of messages?

With Saxon 6.0, if you use //Message it will build a node-set in memory
containing all the Message elements, and subsequent references to //Message
will use this node-set rather than searching the source document again. So
some of the conventional wisdom about not using //X may no longer be true:
I'd be interested to see any practical measurements. Obviously it depends on
how many Message elements there are. And defining a key should still be
faster for this kind of example. (Optimising this to auto-generate an index
is an exercise for the next release but N).

Mike Kay 


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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]