I am using MySQL 4.0.20a, and have created the database tables of type innoDB. I am using AUTO_INCREMENT as the id generation scheme for objects. I am doing the following:

JTA txn begin;

PersistenceObject obj = new PersistentObject();
obj.set.....;
getHibernateSession().save(obj); // this issues an SQL insert

JTA txn rollback();

I expect the rollback to undo the save/insert. This doesn't work if the id generation type is AUTO_INCREMENT. It seems to work if I use the the Hibernate id generation scheme.

Any ideas?
Suresh

I'd use native.

see Hib doc's 5.1.4...

"native
picks identity, sequence or hilo depending upon the capabilities of the underlying database. "

I am actually using the native tag in the hbm.xml. I have also noticed that the updates are rolled back but objects newly created are not getting rolled back.

It is as though the JDBC connection has auto commit mode set to true though the connection is obtained in JTA transaction. FYI, I am using JOTM transaction mgr implementation, with the Enhydra StandardXADataSource implementation. I have noticed the JDBC connection returned by default has auto mode set to true. Since I am calling Hibernate Session FactoryImpl.openSession() I am expecting Hibernate to get the JDBC connection. Maybe this is an Enhydra issue.

Did anyone ever find a solution to this problem?

I'm using hibernate 3.0.5, spring 1.2.1, and mysql 4.0.20 and notice this same behavior when inserting/saving new objects using auto_increament.