Hibernate version:2.1.8

Exception:
net.sf.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update

Database: MySQL 4

I have a problem that could be solved if I could give a certain priority to each operation executed during the Batch Update when commiting the transacton.

The problem is that certain table rows have to be deleted before inserting new ones due to foreign key restrictions. Both deletion and creation of new objects are executed during the same hibernate transaction but when commiting hibernate tries to insert the new rows first.

In other contexts, when the new rows inserted do not violate the constraint, everything works perfectly, because old objects (rows) are deleted at the end of the sql batch update.

To make matters worse, I cannot separate these two operations in two different transactions, because data consistency would be at risk.

is there a way to create the delete statements before the insert statements (or create a bunch of Query classes and wait to use them) and use them at the end and do a transaction.flush() after running the delete statements but before running the insert statements.

apparently there was no need to complicate things that much.
I hadn´t thought about the flush() call in the middle of the Transaction, and that seems to have solved the problem.
What Im concerned about now is the consistency issue...

Thanks a lot!

haha, guess I got carried away with the explanation. I tend to ramble.

Well I don't know how complicated your database and its relationships are, but flush is a relatively good command so long as your cascade and delete options are correct.

Don't forget to rate