[
https://issues.apache.org/jira/browse/DERBY-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052072#comment-13052072
]
Kathey Marsden commented on DERBY-5010:
---------------------------------------
Looking at the derby.log, it seems to me that the
derby.language.logStatementText=true property is not getting picked up.
If you look at the top of the log, there is no statement listed before the
first instance of the stack trace printing,
Database Class Loader started - derby.database.classpath=''
java.lang.Exception: Trace in isEquivalent
at
org.apache.derby.impl.sql.compile.BaseColumnNode.isEquivalent(BaseColumnNode.java:183)
at
org.apache.derby.impl.sql.compile.SubstituteExpressionVisitor.visit(SubstituteExpressionVisitor.java:62)
at
org.apache.derby.impl.sql.compile.QueryTreeNode.accept(QueryTreeNode.java:718)
at
org.apache.derby.impl.sql.compile.ResultColumn.acceptChildren(ResultColumn.java:1550)
In your previous comment, you mentioned you ran it as:
java org.apache.derbyTesting.functionTests.tests.lang.LangScripts aggregate
try
java -Dderby.language.logStatementText=true
org.apache.derbyTesting.functionTests.tests.lang.LangScripts aggregate
If that still doesn't show the statement before the exception prints, try
running the
java/testing/org/apache/derbyTesting/functionTests/tests/lang/aggregate.sql ust
with ij, outside of the harness, making sure you start ij with the property
java -Dderby.language.logStatementText=true org.apache.derby.tools.ij
> [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.4
>
> Attachments: IsEquivalent_DoNotCommit_June11.txt,
> IsEquivalent_Donotcommit_june14.txt, bad_equivalence_check.diff, 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
