[
https://issues.apache.org/jira/browse/DERBY-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054812#comment-13054812
]
Jayaram Subramanian commented on DERBY-5010:
--------------------------------------------
When executing the sql statement 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); in ij observed the following
1) the control goes to isequivalent method but if (isSameNodeType(o)) is
returning false making the flow not to go in to the modified section of code
2) the reason why if (isSameNodeType(o)) is returning false is
2.1) in valuenode class nodetype has a value 62
2.2) in querytreenode class nodetype has a value 94
I am not able to infer what these values mean or how they got assigned... but
if we are able to get to make them equal then control would go to the modified
section of code...
> [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.5
>
> 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
