I attempt to persist 3 new objects (i.e. transient ones that do not yet exist in the database) to the database in a single transaction.

The first 2 inserts are OK, but the third insert throws an exception (I put a CallbackException into the Interceptor to do this). When the transaction rolls back none of the records exist in the database, which is good.

I dump the session and create a new one, and then attempt to save the same 3 objects again, but this time without throwing the CallbackException. However, it seems that that even though the transaction was rolled back, Hibernate thinks that the first two objects were saved successfully (it does not try to insert them into the database, even though they don't exist there). This is probably because during the first attempt Hibernate gave the objects non-null identifiers?

What should I do - should I manually set the identifiers to null when the transaction rolls back?? This seems a bit clunky...

Can anyone help me??

Thanks,

Doug.



Hibernate version: 2.1.8

Name and version of the database you are using: MySQL 4.0

Its up to you (the developer) to 'rollback' to an acceptable domain object state if you are trying to recover that state after an Tx Exception. Most situations you throw the session and related state away. Ready to start again.

There are some other options worth considering, though.

Related thread here.