This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: XSL equivalent to SQL "unique"
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] XSL equivalent to SQL "unique"
- From: "Michael Kay" <mhkay at iclway dot co dot uk>
- Date: Wed, 18 Apr 2001 10:35:33 +0100
- Reply-To: xsl-list at lists dot mulberrytech dot com
> looks like I've got a syntax or rtf/node-set problem, all methods
> descibed there would apply easily if I had entries like
>
> <set name="1">
> <entry name="a">v1</entry>
> <entry namw="b">v2</entry>
> </set>
>
> but all my trials to convert from the below format to that
> seem to end at the result-tree-fragment/noed-set boundary. E.g.
> I'd like to write
>
> <xsl:variable name="all">
> <xsl:for-each select="set/*">
> <name><xsl:value-of select="name()"/></name>
> </xsl:for-each>
> </xsl:variable>
>
> to convert below data into above format in the variable $all.
> But the result is a result tree fragment which cannot be processed
> by another for-each loop. I cannot figure a workaround for the
> obstacle.
The work-around is called the xx:node-set() function, where xx is
vendor-specific.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list