Hello,

Recently I've found a problem that's making me crazy. We are doing a test framework that's capable of saving a database state (rows) in an hierarchical way with hibernate to Json.
That way you can do a hibernate.hbm2ddl.auto=create at the begining of the tests. Restore a database snapshot and load the data for the test from the Json.

It works great!

Except if you don't rollback after the test and tries to remerge the existing entities. The problem is that the versioning timestamp is updated to now on the first save. And you cannot remerge it because the entity on the database is newer than the one loaded from the disk. While this is not true.

The problem is that Hibernate (correctly) updated the version on the first store.

My question is. Can I enter a batch mode where this version update is not done and database is stored as is? Without modifying DB definition. Programatically.

Is there a way to resolve this problem?

Is there any utility that can load the data so I don't have to do it?

Best regards,

What if you switch to numerical @Version?

It doesn't matter. In fact this is related to this other issue I opened
viewtopic.php?f=1&t=1044040

In fact the optimistic version field is okay as timestamp. This way we track whether a version has changed and when.

But thank you for the comment.

Well, using the wall-clock time for concurrency control is always trouble. Check out this article for more info.