[
https://issues.apache.org/jira/browse/DERBY-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-4736:
---------------------------------
Attachment: derby-4736-1b.diff
derby-4736-1b.stat
Uploading a new version of the preliminary patch, derby-4736-1b, which makes
the test
correctly expect a row count of 1280 (the same as postgresql). By commenting
out the LOJ reordering code in SelectNode, Derby produces the same number of
rows also, so there is another bug in the reordering logic somewhere. The test
currently fails, although the assert is gone.
> ASSERT FAIL when code generating a column reference in a join predicate in
> presence of other outer join reordering
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4736
> URL: https://issues.apache.org/jira/browse/DERBY-4736
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 10.7.0.0
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Attachments: derby-4736-1a.diff, derby-4736-1a.stat,
> derby-4736-1b.diff, derby-4736-1b.stat
>
>
> From schema given in DERBY-4712, this query gives an ASSERT with sane Derby:
> rs = s.executeQuery("SELECT 1 FROM (T0 LEFT JOIN (T1 LEFT JOIN (T2 LEFT JOIN
> " +
> " (T3 LEFT JOIN T4 ON 1=1) ON T2.X = T3.X) ON
> 1=1) ON 1=1) " +
> " LEFT JOIN " +
> " (T5 INNER JOIN T6 ON 1=1) " +
> " ON T2.X = 1 ");
> Cf the attachments in DERBY-4712 assert-bind-opt-trees.*.
> From preliminary analysis, this error seems to be unrelated to the NPEs
> reported in DERBY-4712, so filing this as a sub-issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
