Hi,
Modified the isEquivalent method to throw an exception like this.. is
it correct..

protected boolean isEquivalent(ValueNode o) throws StandardException
        {
                //Thread.dumpStck();
                
                
                if (isSameNodeType(o))
                {
                        BaseColumnNode other = (BaseColumnNode)o;
                        return other.tableName.equals(other.tableName)
                        && other.columnName.equals(columnName);
                }
                if (1==1) {     
                        throw StandardException.newException("Exception in 
equivalent for test");
                }
                return false;
        }
}

Also  all of a sudden i started getting
1) TriggerTests:embeddedjava.sql.SQLException: No suitable driver
        at java.sql.DriverManager.getConnection(DriverManager.java:330)
        at java.sql.DriverManager.getConnection(DriverManager.java:297)
        at 
org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:81)
        at 
org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43)
        at 
org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1538)

With Regards
Jayaram

On Thu, Apr 14, 2011 at 4:57 AM, Knut Anders Hatlen
<[email protected]> wrote:
> Jayaram Subramanian <[email protected]> writes:
>
>> Hi Knut,
>> Sorry for the delay.. It was hectic for me for the past 2 months..
>> When i placed thread.dumpstack and ran the lang.__suite, the log shows
>> a lot of references to isEquivalent method..  Just attaching one of
>> the example. Could you please guide me how to proceed from here
>
> Hi Jayaram,
>
> This sounds like good progress. Now you know which tests that call this
> method. I think the next step would be to find out what the queries look
> like. Can you see that from the test logs? If not, maybe you can make
> the method throw an exception so that the test stops once the method is
> called. If we know what the queries look like, we may find a way to
> tweak them so that they trigger the bug.
>
> --
> Knut Anders
>

Reply via email to