I hadn't been using this property, but setting t to false (which is supposed to be the default) fixed the delete NPE.
THANKS!!! I was in a real pinch. I'll do some more validation of this later tonight. -geoff “How many legs does a dog have if you call the tail a leg? Four. Calling a tail a leg doesn't make it a leg.” – A. Lincoln ________________________________ From: Knut Anders Hatlen <[email protected]> To: Derby Discussion <[email protected]> Sent: Monday, February 2, 2009 1:33:07 AM Subject: Re: serious issue with delete Geoff hendrey <[email protected]> writes: > Hi All, > > I think I reported it a while back, but it keeps cropping up. This problem > seems to appear suddenly, on a database that was otherwise working fine, and > when it happens, all delete operations seem to be permanently broken. I cannot > delete from any table (or so it seems...I'm pretty tired right now). If it > matters, those are double underscores in the table name. > > DELETE FROM GEOFF__TESTPERID__A WHERE "PK"=6 > > ... > Caused by: java.sql.SQLException: Java exception: ': > java.lang.NullPointerException'. > at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown > Source) > at > org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA > (Unknown Source) > ... 39 more > Caused by: java.lang.NullPointerException > at org.apache.derby.impl.sql.execute.NoRowsResultSetImpl.close(Unknown Hi Geoff, It looks like you've come across this problem: https://issues.apache.org/jira/browse/DERBY-2353 (Or a similar issue, possibly the same as DERBY-2353, logged as https://issues.apache.org/jira/browse/DERBY-4043) The workaround in both cases is to unset derby.language.logQueryPlan. Hope this helps, -- Knut Anders
