[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
A B updated DERBY-1681:
-----------------------
Attachment: d1681_test_v2.patch
Attaching a second version of the new test case for this issue. The test
changed as part of the DERBY-1633 checkins and thus the patch had to be
re-synced.
Note that the test cases which were added for DERBY-1633 actually already
demonstrate the problem reported (and now fixed) in this issue. However, I
don't think it hurts to have a dedicated test case, so I still think it would
be good to commit d1681_tests_v2.patch to the trunk and 10.2 codelines (those
are the codelines into which the fix for this issue has already been comitted).
I'm also working to port DERBY-1633 to 10.1; when that's done, the test patch
for this issue should be ported to 10.1, as well.
This is test-only patch: d1681_test_v2.patch is ready for commit.
> Regression (wrong results): Join predicate can be ignored for left-most child
> in a chain of nested unions.
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1681
> URL: http://issues.apache.org/jira/browse/DERBY-1681
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.2.1.0, 10.1.3.0, 10.1.3.1
> Reporter: A B
> Assigned To: A B
> Fix For: 10.2.1.0, 10.1.4.0
>
> Attachments: d1681_test.patch, d1681_test_v2.patch, d1681_v1.patch,
> DERBY-1681_v1.html
>
>
> If Derby chooses to do a join between two FromTables and the right table is a
> chain of UNIONs, then the optimizer may choose to push the join predicate (if
> provided) down into the UNION and to both children of every UNION in the
> chain. But if the predicate cannot be pushed to the children of any of the
> UNIONs (except the top-level one) the predicate can end up being ignored
> altogether with respect to that UNION's children. The result is that query
> execution can return rows that do not satisfy the predicate.
> This is a regression introduced in 10.1.2.4 and thus it affects 10.1.3 and
> 10.2. I came across this while tracing through code for DERBY-1633.
--
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
