db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-5010) [patch] bad equivalence check
Date Tue, 05 Jul 2011 11:58:16 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen resolved DERBY-5010.

          Resolution: Fixed
       Fix Version/s:     (was:
            Assignee: Dave Brosius
    Issue & fix info:   (was: [Patch Available])

Thanks for the continued investigation, Jayaram.

The more I look at this code, the more convinced I get that the broken code cannot currently
be exercised, and your experiments seem to support that.

In any case, the patch looks correct, so I've committed it to trunk (revision 1143002). Thanks,
Dave, for the fix.

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


View raw message