> > <xsl:variable name="u" select="unordered((1,2,3))" />
Can anyone see a use for this please?
The function I mean, rather than this instance.
NOTICE: The information contained in this email and any attachments is
confidential and may be legally privileged. If you are not the
intended recipient you are hereby notified that you must not use,
disclose, distribute, copy, print or rely on this email's content. If
you are not the intended recipient, please notify the sender
immediately and then delete the email and any attachments from your
RNIB has made strenuous efforts to ensure that emails and any
attachments generated by its staff are free from viruses. However, it
cannot accept any responsibility for any viruses which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent those of RNIB.
RNIB Registered Charity Number: 226227
From: Michael Kay <mhk@mh...> - 2003-09-29 12:18:33
> Can anyone see a use for this please?
> The function I mean, rather than this instance.
It's mainly designed for data-intensive queries, where there is no need
to deliver the results in a particular order. In particular, putting
unordered() around a FLWR expression greatly improves the ability of the
system to do the sort of rewriting that SQL engines are good at, and
will often make it possible to exploit an index where otherwise a serial
scan (or at any rate a sort of the results) would be needed.
When you're dealing with hundreds of gigabytes of source, such things
become essential. I don't think there are strong use cases in the
typical XSLT scenario of a few megabytes.