Hibernate version:
2.1.6

Hibernate designing question:
Whar is the most fitting way in hibernate to implement data access that never really deletes an object, but creates a new instance and marks the old one as "out-of-time".

My current approach (without hibernate) was to keep two timestamps with each entry - a "birth-date" and a "death-date" .... so "updating" was to set a death-date of the old version and insert the new version with a new birth-date while "deleting" was setting a death date without inserting a new entry....

Another approach would be to keep just the birth date and a "deleted" flag...

Now the questions:

Which model is better for hibernate to use ?

Some tips on where and how to do it would we be very fine of you as well

:o)

J

....with other people working on it it seems that the 2-timestamp model seems to be better, in the other model you dont know WHEN it was deleted, e.g. when you got an entry with a birth-date 1999 and the deleted flag set and you want to know the data of 2000 you dont know if the entry was deleted 1999 or 2001....

so it HAS to be the 2-timestamp model...

My first try would be an interceptor where the objects in the saved array would be modified (death-date set...) and the "new" versions would be added to the array....

It could work, but i guess theres a better way....

you can customize this pattern
http://blog.hibernate.org/cgi-bin/blosx ... rytriggers

http://blog.hibernate.org/cgi-bin/blosxom.cgi/Christian%20Bauer/relational/historytriggers.html

Damn, anthony faster again :)

Thx for the tip guys.... quite fast you are :o)

i looked through it and im unsure if its good for my environment, cause we are using mysql and mysql only supports triggers in version 5.0 which is indicated as alpha release....

Anyone any experiences with MySQL 5.0 ? Stability is a major point in my case....

Or any other approaches ?

Get a real database :)

;))