Hello
The following is a purely DB related answer to the question.
I am also inclined to avoid the use of triggers. What follows is an idea I had on the issue, but I did not realize it yet in practice. Moreover, it depends on possibilities of your DB :
Keep one table containing all objects and their history, so primary key should somehow involve the history, I would actually prefer to create a new unique id for each modification to the original object.
Keep a field in the table to indicate that a specific version is default or current.
Create a
materialized view and let your DB do the work of updating.
Admittingly, the work of adapting the view when the underlying table changes is not avoided, but this seems to be less cumbersome in maintenance than adapting triggers
Tabari
