I’m currently working on a spike solution with an existing Oracle database. We are using Hibernate 3.0.5 for this spike solution effort. Database triggers have been created to manage the setting of the initial version number and the increment of that version number in INSERTs and UPDATEs, respectively. Obviously, this is not the ideal situation for Hibernate—Hibernate wants to manage the incrementing of the version number and keeping that version number synchronized between the object instance and the database row. What sort of strategies can we use in Hibernate to allow the increment to happen at the database, but have Hibernate correctly reflect that situation in the associated object instance? Would an Interceptor or the new event subsystem in Hibernate3 allow us to manage the version number appropriately?

Kind regards,

-- chris bartling –

1)see http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#transactions-optimistic-customizing
2)you can manage version in trigger code.
3)you can use interceptor