Hi All, Could you please help how to proceed from here. With Regards Jayaram
On Wed, Jun 15, 2011 at 10:51 PM, Jayaram Subramanian (JIRA) < [email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/DERBY-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050205#comment-13050205] > > Jayaram Subramanian commented on DERBY-5010: > -------------------------------------------- > > Modified the the basecolumnNode class isequivalent method to do a > Thread.dumpStack(); and then ran the aggregate test alone by doing > $ java org.apache.derbyTesting.functionTests.tests.lang.LangScripts > aggregate > >june15.out 2>&1 > > Verified that executing aggregate resulted in the dump getting produced . > But the dump didnt indicate the sql statement which resulted in calling the > isquivalent method.. Attaching the june15.out file for reference > > > [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.4 > > > > Attachments: IsEquivalent_DoNotCommit_June11.txt, > IsEquivalent_Donotcommit_june14.txt, bad_equivalence_check.diff, 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 > > >
