db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5010) [patch] bad equivalence check
Date Tue, 19 Apr 2011 16:08:05 GMT

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

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

There was some discussion on the list about tracking down the statement that goes through
BaseColumnNode.isEquivalient() , by adding a thread dump in the method.  I wanted to suggest
an alternate method that might make things easier to track down.  I may be missing the mark
as I have not been folllowing the thread on the list carefully.

I think if you set the system property derby.language.logStatementText=true with -Dderby.language.logStatementText=true
and then in the method call org.apache.derby.iapi.services.monitor.Monitor.getMonitor().logThrowable(new
Exception("Trace in isEquivalent")
you should get the stack trace right after the statement that goes there in derby.log




> [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.2
>
>         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

Mime
View raw message