Subject: Re: [xsl] Processing milestoned XML leads to many preceding:: calls and horrible performance From: Alex Muir <alex.g.muir@xxxxxxxxx> Date: Tue, 21 Feb 2012 11:16:17 +0000 |
Just a thought,, often when I use preceeding and following I limit how many preceeding or following using position() and le some number before other conditions to limit the scope of the results however that depends on the data of course. On Tue, Feb 21, 2012 at 10:28 AM, Michael Kay <mike@xxxxxxxxxxxx> wrote: > select="count(./preceding::kap[1]/following::*[not(count(preceding-sibling::v ers|current()) > = count(preceding-sibling::vers))])" -- Alex Muir Program Organizer - University Technology Student Work Experience Building University of the Gambia http://sites.utg.edu.gm/alex/ Come visit Gambia enjoy the sun and culture and help out! Software Engineering Lecturers needed! Join UTSWEB do local contract work or give a student a contract remotely for slow, cheap and good work http://sites.utg.edu.gm/utsweb/ Some fantastic African/Canadian Fusion http://bafila.bandcamp.com/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Processing milestoned XML, Michael Kay | Thread | [xsl] OutputURIResolver Cause: net., team wise |
Re: [xsl] Processing milestoned XML, Michel Hendriksen | Date | [xsl] OutputURIResolver Cause: net., team wise |
Month |