On 14/03/2025 17:37, Graydon graydon@xxxxxxxxx wrote:
> On Fri, Mar 14, 2025 at 04:26:54PM -0000, Michael Kaymichaelkay90@xxxxxxxxx
scripsit:
>> Three options:
>>
>> (a) use xsl:key
>>
>> (b) use an XSLT processor that optimizes joins (such as Saxon-EE) (but you
may need to write the search using predicates, not using xsl:for-each and
xsl:if)
>>
>> (c) build your own indexes as maps, as you suggest.
> Tangentially, is there a use case where xsl:key is expected to be
> preferable in performance terms to using maps?
I would still think that XSLT 3 with composite keys xsl:key
name="key-name" match="foo" use="bar, baz" composite="yes" is easier
than doing that with a map.
|
Cart
