Saxon XSLT and XQuery Processor

Tracker: Bugs

5 Sort isn't stable for null key values - ID: 708789

Last Update: Settings changed ( mhkay )

Details:

When two or more sort keys evaluate to the empty
sequence, the result should be in document order. It is
currently in random order.

Afffects Saxon 7.4 only.

Test case: sort107

Submitted:

Michael Kay ( mhkay ) - 2003-03-24 13:00

Priority:

Status:

Closed

Resolution:

Fixed

Assigned:

Michael Kay

Category:

XSLT conformance

Group:

v7.4

Visibility:

Public

Comment ( 1 )

Date: 2003-03-24 13:11 Sender: mhkay Logged In: YES user_id=251681 Source code fixed. Line 181 in SortedIterator.java was: return (nodeKeys[b1+i]==null ? 0 : -1); should be: comp = (nodeKeys[b1+i]==null ? 0 : -1); In fact the problem is more severe that originally described; if one sort key is null for both items, then subsequent sort keys are not being examined. MK

Attached File

Changes ( 3 )

Field	Old Value	Date	By
status_id	Open	2003-06-27 18:58	mhkay
resolution_id	None	2003-06-27 18:58	mhkay
close_date	-	2003-06-27 18:58	mhkay

Saxon XSLT and XQuery Processor

Tracker: Bugs

Comment ( 1 )

Attached File

No Files Currently Attached

Changes ( 3 )

About SourceForge

Find Software

Develop Software

Community

Help