This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2362 - Results for OrderExpr series are wrong
Summary: Results for OrderExpr series are wrong
Status: RESOLVED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 0.8.0
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Andreas Behm
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-18 21:03 UTC by Michael Kay
Modified: 2005-11-09 13:50 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2005-10-18 21:03:42 UTC 
OrderExpr-3 reads:

ordered {$input-context//part[@partid < 2]/fn:last()}

the result of this must be a sequence of integers, yet the results provided are
element nodes.

Also affects OrderExpr-4.

OrderExpr-7 and OrderExpr-8 call fn:first() which is a syntax error, there is no
such function.

OrderExpr-15 calls fn:subsequence((1,2,3,4),2,3) which returns a sequence of
length 3 namely (2,3,4), not (2,3) as given.

Similarly OrderExpr-16

OrderExpr-17 is described in the catalog as returning OrderExpr-15.txt, which is
not the correct result (the sequence hasn't been reversed).
Comment 1 Andrew Eisenberg 2005-10-19 17:33:12 UTC 
Perhaps ordered {$input-context//part[@partid < 2]}/fn:last() was intended?
Comment 2 Andreas Behm 2005-10-24 18:26:51 UTC 
fixed tests 15-17.
For now, removed tests 3/4/7/8 as they are not very meaningful, will add new
tests instead.
Comment 3 Alberto Massari 2005-11-08 15:55:22 UTC 
Andreas,
tests OrderExpr-15/17 are still wrong in the 0.8.0 version of the test suite

Alberto
Comment 4 Michael Kay 2005-11-08 22:26:59 UTC 
I agree with Alberto - 15-17 are still wrong.
Comment 5 Andreas Behm 2005-11-09 13:50:30 UTC 
Yes, I didn't commit the files in CVS.