Actions
Bug #3132
closed
Composite keys in xsl:key not implemented
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
XSLT Conformance
Sprint/Milestone:
-
Start date:
2017-02-15
Due date:
% Done:
100%
Estimated time:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-
Description
A stylesheet using xsl:key with composite="yes" appeared to be giving incorrect answers. We didn't stop to investigate so I don't have a repro at this stage.
Related issues
Updated by Debbie Lockett over 6 years ago
- Related to Bug #3395: Composite keys with -export added
Updated by Michael Kay over 6 years ago
- Subject changed from Possible problem with composite keys in xsl:key to Composite keys in xsl:key not implemented
- Status changed from New to Resolved
- Applies to JS Branch Trunk added
- Fix Committed on JS Branch Trunk added
The feature had simply not been implemented.
It is now implemented (on the 2.0 branch only: will not be retrofitted to 1.0). Involved some refactoring and reuse of the code for handling composite keys in xsl;for-each-group.
Updated by Debbie Lockett almost 4 years ago
- Description updated (diff)
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in JS Release set to Saxon-JS 2.0
Please register to edit this issue
Actions
Also available in: Atom PDF Tracking page
.