Project

Profile

Help

Bug #3395

closed

Composite keys with -export

Added by Michael Kay over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XSLT export
Sprint/Milestone:
-
Start date:
2017-08-15
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.8
Fix Committed on Branch:
9.8
Fixed in Maintenance Release:
Platforms:

Description

The fact that a key definition is composite (xsl:key composite=yes) is not reflected in the export file; on reloading, the key will be non-composite, so calls on key() will not work.

Affects test case key-093.


Related issues

Related to SaxonJS - Bug #3132: Composite keys in xsl:key not implementedClosed2017-02-15

Actions
Actions #1

Updated by Michael Kay over 6 years ago

  • Status changed from New to In Progress
  • Fix Committed on Branch 9.8 added

Fix committed on the 9.8 branch.

Will also affect Saxon-JS, so leaving the bug open.

Actions #2

Updated by Debbie Lockett over 6 years ago

  • Related to Bug #3132: Composite keys in xsl:key not implemented added
Actions #3

Updated by Michael Kay over 6 years ago

  • Status changed from In Progress to Resolved

Marking as resolved, the Saxon-JS side will be followed up under bug 3132.

Actions #4

Updated by O'Neil Delpratt over 6 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 9.8.0.4 added

Bug fix applied in the Saxon 9.8.0.4 maintenance release.

Please register to edit this issue

Also available in: Atom PDF