DEBUG accesslayer.sql.SqlGeneratorDefaultImpl - SQL:INSERT INTO ... DEBUG broker.accesslayer.JdbcAccessImpl - executeInsert: null
There's only one place in JdbcAccessImpl where that log message could come from (because the string 'executeInsert:' only appears there):
-------- JdbcAccessImpl : lines 225-239:
stmt = broker.serviceStatementManager().getInsertStatement(cld);
if (stmt == null)
{
logger.error("getInsertStatement returned a null statement");
throw new PersistenceBrokerException("getInsertStatement returned a null statement");
}
broker.serviceStatementManager().bindInsert(stmt, cld, obj);
if (logger.isDebugEnabled())
logger.debug("executeInsert: " + stmt);stmt.executeUpdate();
// Harvest any return values.
this.harvestReturnValues(cld.getInsertProcedure(), obj, stmt);
--------If the 'stmt' in the debug call is 'null', how could it have gotten past the null check earlier? And why isnt' it throwing an NPE when the executeUpdate() is called? I'm mystified.
Joe
--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
