Hi,

i've read the blog from christian about using instead-of-trigger for creating history-data and versioning ...

Because it's not possible to change the database to add a version- or timestamp-column directly (other existing applications will use these tables, too and therefore no changes to the existing db-tables are allowed) i've tried to put the version-info into a seperate table ... so far so good.

But the IBM DB2/AS400 doesn't support "instead-of"-triggers :(

There're some possibilities for me, that i all don't really like:
1.) use "optimistic-lock='all'" which does not work since version 2.1.5. so i had to use version 2.1.4. But this can't be really the solution, because version 2.1.6 includes some bug-fixes and so on ...

2.) do the concurrency-handling by hand using e.g. the "Interceptor-callback-methods" and checking perhaps a version-id in a child-object. (additional select-statement required). Alternatively i can check the versionid before insert- or update-operations ... but i still need a seperate select-statement ...

3.) don't use concurrency-handling ;)


Does anybody has a better idea? At the moment i'm thinking of using version 2.) ...

thx!
carsten

You could use Hibernate3 and take advantage of its stored procedure support.