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 29337 - UseCaseR31-028 incorrectly assumes specific ordering after group by
Summary: UseCaseR31-028 incorrectly assumes specific ordering after group by
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Proposed Edited Recommendation
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: O'Neil Delpratt
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-14 22:42 UTC by Josh Spiegel
Modified: 2016-01-11 22:10 UTC (History)
0 users

See Also:


Attachments

Description Josh Spiegel 2015-12-14 22:42:15 UTC
The order of the tuple stream after the group by may vary depending on the implementation.  Thus, the contents of the constructed arrays may be different depending on the implementation.  

I suggest adding order by clauses to make the contents of the arrays consistent across implementations.

e.g.  
add  "order by $state" after "group by $state" 
add  "order by $category" after "group by $category"
Comment 1 O'Neil Delpratt 2016-01-06 10:15:00 UTC
Bug fix committed to cvs as suggested in comment #0
Comment 2 Josh Spiegel 2016-01-11 22:10:49 UTC
We also need to update the result to match the new ordering.  I will do it.