db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayaram Subramanian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5010) [patch] bad equivalence check
Date Wed, 15 Jun 2011 03:30:47 GMT

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

Jayaram Subramanian commented on DERBY-5010:
--------------------------------------------

After adding the system.exit(1) to the BaseColumnNode.IsEquivalent method  and the running
 java -Dderby.tests.trace=true junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.lang._Suite
> runoutputJune14.out 2>&1
is causing the log  output to stop at the "aggregate" test. 
Attaching the output log and the diff 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.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

        

Mime
View raw message