Altova Mailing List Archives

Re: Grouping By Field, with only 3 columns in each row.

From: "rdcpro" <rdcpro@-------.--->
Date: 12/21/2004 4:14:00 PM
The problem is with this template:

<xsl:template match="IssuedCard" mode="row">
<xsl:apply-templates select=". | following-sibling::*[DateIssued =
current()/DateIssued][position() &lt; $maxColCount]"/>

note that following-sibling includes all sibling nodes in the original
nodeset, even those that do not meet the key condition.

Also I wanted to point out a potential problem with using this
uniqueness test:

IssuedCard[count(. | key('CardsIssuedByDateIssued', DateIssued)[1]) =

If there are IssuedCard elements without a DateIssued child, they will
show up in the nodeset selected by that expression.  The reason is that

key('CardsIssuedByDateIssued', DateIssued)[1])

will return no node in this case, so the count of the current node plus
nothing is always one.  In your particular case this is probably not an
issue, but watch out for it when using muenchian grouping.  That's why
I still use the generate-id() approach myself, even though it's not
quite a fast on the processors I use.

Mike Sharp


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.