Read the rules before posting!
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 2.7

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using: DB2 8.0

The generated SQL (show_sql=true): true

Debug level Hibernate log excerpt:



it throws the ConstraintVoilationException during the commitTransaction() but not during the save call

is there way to catch ConstraintVoilationException during the save call itself

What you do will not work in any case. If a Session throws an exception it has to be discarded, not re-used. Read the section about exceptions again in the reference documentation. No, you can't use database exceptions for data validation.

>> What you do will not work in any case. If a Session throws an exception it >> has to be discarded, not re-used. Read the section about exceptions
>> again in the reference documentation. No, you can't use database
>> exceptions for data validation.


we have also the fact, that it is possible to get a constraint violation during runtime due to optimistic locking.

is it possible to discard the session and create a new one, while we operate within a CMT-Transaction ?

it would be nececcary to close the existing session, create a new one which will be the one with a possible constraint violation, because we do not like to throw away all statements that was done in the business transaction so far ... ?

cgs