Re: SQLException: General Error
On Sep 22, 4:18 pm, Martin Gregorie
<mar...@see.sig.for.address.invalid> wrote:
That all looks OK. Obvious questions:
- What RDBMS are you using?
- Is the connection always prepared to accept updates?
- How are you handling commits?
Silly question: I suppose you've loaded the code with trace statements
sufficiently to know that it is the executeUpdate() that's throwing the
exception, not anything else?
RDMBS is MySQL 5.0 (and MS Access. I know, I know, it wasn't my idea.)
It fails in both.
I get the connection from another method in a superclass
(getConnection(connectionString)). I assume it is prepared to accept
updates, because it works most of the time.
commits are handled in the finally block like this:
finally {
try {
if (insertStmt != null) {
insertStmt.close();
}
} catch (SQLException sqle) {
//this isn't the place I'm getting a SQLException
//SQLE is caught in the catch block above
//this finally block
}
try {
if ((conn != null) && !(conn.isClosed()) {
conn.commit();
conn.close();
}
} catch (SQLException sqle) {
//this isn't the place I'm getting a SQLException
//SQLE is caught in the catch block above
//this finally block
}
}//end of finally
Yes. I've got tons of statments printing to a log file that show me
exactly where it is failing. It is throwing the SQLException right on
the executeUpdate().