Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 31 Aug 2011 18:32:10 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1082095490.3738.1314815530523.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1774924227.1698.1297141617690.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5010) [patch] bad equivalence check
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden commented on DERBY-5010:
---------------------------------------

It seems the code may not be reachable so no need to backport.

> [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
>            Assignee: Dave Brosius
>            Priority: Trivial
>              Labels: derby_backport_reject_10_8
>             Fix For: 10.9.0.0
>
>         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