Is there a recommended way to check for return codes from the DBMS for SQL executed through Hibernate?

Like something equivalent to Statement.getWarnings() ? We are experiencing a situation where DB2 is return -181 codes to us meaning our SQL statement failed, but we not seeing exceptions thrown when this happens, so up until now the statements have been silently bombing.

We are trying to see if there is a recommended way via Hibernate to check for return codes from the underlying DBMS? I know this is kind of a weird one. Thanks in advance for anyone who can help, or just for taking the time to read our post ! :),

Jim Bender
james.bender@53.com

I'm not sure if this is related to your issue, but I have found that turning off JDBC batching gives me much better exceptions from Hibernate (at least with HSQLDB). With batching turned on, I just get a generic 'batch failed' exception, but with batching turned off, I get more meaningful SQL exceptions that Hibernate automatically maps to meaningfule Hibernate exceptions (like org.hibernate.exception.ConstraintViolationException).

Of course, this is only helpful for reproducing a problem in development, since turning off batching is likely to incur a performance hit.

Hope this helps!

That is a good tip -- I will have to keep that in mind. Thanks! :),

Jim