more precise exception when insert fails?

feh · **Joined:** Wed Aug 02, 2006 11:30 am **Posts:** 7

When attempting to insert a record (save an object) which has a unique constraint on a column, and the unique constraint is being violated, I receive this exception:

org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update

Is it possible for hibernate to provide a more useful/specific exception, so I can interpret what the actual problem was?

Thanks.

max · **Posted:** Wed Aug 02, 2006 11:49 am

you probably have to disable jdbc batching to get a meaningfull exception from the database.

bkmr_77 · **Joined:** Tue Apr 25, 2006 12:04 pm **Posts:** 260

I just use following code to try to get the reason for exception and then throw my application exception based on it. I remember here, months back, on this forum there was an example to find the exact cause of exception - but I am not able to find the link/post.

Code:

String exMsg = e.getMessage();
System.out.println("exceptionMessage = " + exMsg);
// Will this naming convention stay same
// for all future releases of hibernate?
if ( (exMsg != null) && (exMsg.indexOf( "org.hibernate.exception.ConstraintViolationException" ) != -1) ) {
   exMsg = "The Code entered already exists, please enter a unique Code.";
}
throw new MyApplicationException( exMsg );

max · **Posted:** Wed Aug 02, 2006 12:11 pm

yes, but it probably still requires disable jdbc batching to get those exceptions.