[ http://issues.apache.org/jira/browse/DERBY-1109?page=all ]
A B updated DERBY-1109:
-----------------------
Attachment: d1109.patch
d1109.stat
Based on comments from Satheesh and Mike at this thread:
http://article.gmane.org/gmane.comp.apache.db.derby.devel/16656
it seems like there is agreement that the resolution for this diff is to simply
add an "ORDER BY" clause to the affected queries. The attached patch does just
that. Note that the diffs might seem larger than expected, but that's because
the order by has added a level of nesting to the query plan, which affects
spacing and hence creates a larger diff.
I ran lang/subquery.sql and lang/predicatePushdown.sql against IBM wsdd5.6, IBM
1.4.2, and Sun 1.5 and both tests passed for all three JVMs.
There are no code changes in this patch, so if a committer could look it over
and commit, that'd be great.
Thanks again to Mike for the input/explanation of what was going on here. I
appreciate it.
> lang/predicatePushdown.sql fails with wsdd5.6
> ---------------------------------------------
>
> Key: DERBY-1109
> URL: http://issues.apache.org/jira/browse/DERBY-1109
> Project: Derby
> Type: Test
> Components: Regression Test Failure
> Versions: 10.2.0.0
> Environment: IBM wsdd5.6 j9_13
> Reporter: Deepa Remesh
> Attachments: d1109.patch, d1109.stat
>
> This test fails with the following diff:
> 7507a7508,7509
> > 2 |1
> > 4 |2
> 7509,7510d7510
> < 4 |2
> < 2 |1
> 7632a7633,7636
> > 2 |1
> > 2 |1
> > 4 |2
> > 4 |2
> 7635,7638d7638
> < 4 |2
> < 4 |2
> < 2 |1
> < 2 |1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
