[
https://issues.apache.org/jira/browse/DERBY-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059667#comment-13059667
]
Jayaram Subramanian commented on DERBY-5010:
--------------------------------------------
Hi Knut,
I tried all the following variations but nothing seem to break the basecolumn
to columnreference comparison.. So shall i jump on to the next task
select c1 from t1 group by c1 having (max(c2) in (select c1 from t2)) OR
(max(c1) in (select c2-999 from t2)) OR (count(*) > 0);
select c1 from t1 group by c1 having (max(c1) in (select c1 from t2)) OR
(max(c1) in (select c2-999 from t2)) OR (count(*) > 0);
select c1 from t1 group by c1 having (max(c1) in (select c1 from t2)) OR
(max(c1) in (select c1-999 from t2)) OR (count(*) > 0);
select c1,count(c1) from t1 group by c1 having (max(c1) in (select c1 from t2))
OR (max(c1) in (select c1-999 from t2)) OR (count(*) > 0);
> [patch] bad equivalence check
> -----------------------------
>
> Key: DERBY-5010
> URL: https://issues.apache.org/jira/browse/DERBY-5010
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1
> Reporter: Dave Brosius
> Priority: Trivial
> Fix For: 10.8.1.6
>
> Attachments: IsEquivalent_DoNotCommit_June11.txt,
> IsEquivalent_Donotcommit_june14.txt, bad_equivalence_check.diff, derby.log,
> derby.log, june15.out, runoutputJune14.out, runoutputJune2.out
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> code attempts to compare two BaseColumnNodes but doesn't compare the
> tableName correctly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
