db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <knut.hat...@oracle.com>
Subject Re: (DERBY-5010) [patch] bad equivalence check
Date Sun, 17 Apr 2011 17:47:33 GMT
Jayaram Subramanian <rsjay1976@gmail.com> writes:

> Thanks all,
> When i see the logs i am seeing that the test which calls isequivalent method is
>
> org.apache.derbyTesting.functionTests.util.ScriptTestCase.runTest(ScriptTestCase.java:188)
>
> The line 188 in scripttestcase has
> org.apache.derby.tools.ij.runScript(
> 				conn,
> 				sqlIn,
> 				inputEncoding,
>                 getOutputStream(),
> 				outputEnc,
>                 useSystemProperties);
>
>
> i will try to direct the sqlin to the logs and try to find out the sql
> which gets executed

I think running with -Dderby.tests.trace=true should make ScriptTestCase
print the name of the script it's running. Then perhaps you could run
that script manually in ij and see which statement it executed right
before the stack was printed.

-- 
Knut Anders

Mime
View raw message