[ https://issues.apache.org/jira/browse/DERBY-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049601#comment-13049601 ] 

Bryan Pendleton commented on DERBY-5010:
----------------------------------------

If it's definitely the 'aggregate' test which is touching the code, then you should be able
to confirm this by doing something like:

  java org.apache.derbyTesting.functionTests.harness.RunTest lang/aggregate.sql

with and without your "System.exit(1)", and see the test pass without your change, and
exit early with your change.


> [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.3
>
>         Attachments: IsEquivalent_DoNotCommit_June11.txt, IsEquivalent_Donotcommit_june14.txt, bad_equivalence_check.diff, 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