You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Jayaram Subramanian (JIRA)" <ji...@apache.org> on 2011/06/11 14:14:58 UTC

[jira] [Commented] (DERBY-5010) [patch] bad equivalence check

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

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

Modified the BasecolumnNode class's IsEquivalent method to add the monitor method... But still when executing test.lang.__Suite, the log doesn't show any trace of the newly  added trace , i am attaching the patch and the __Suite  output

> [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: bad_equivalence_check.diff
>
>   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