> this is not a bug, Hibernate does not do object-level rollback at all. > This means after a rollback, your objects are not guaranteed to have their > state reverted to that before the transaction start. You should either not > reuse the object after rollback, or implement it yourself if you need.
Thanks, I got that. But what if the object is immutable? This will prevent setting the ID back to null, right? And what about my 2nd question: Shouldn't Hibernate check constraint violations via SessionImpl#checkNullability(..) etc. BEFORE the sequence is requested from the database? Regards, Jonas ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
