Forum OpenACS Development: a Model to store Deleted Rows History
Did any one of you think of/implement a general dynamic DB Model to store a history for every deleted row in any table, something to work with an after delete trigger on each table.
My initial thinking is something like to store the filed name and field value.
Or this is a far impractical something to think about?
With the content repository, cr_revisions just holds everything and you point at the live revision from cr_items. The disadvantage of that audit method is that you can't have unique constraints on cr_revisions columns (the advantage is rolling a revisions back or forth is trivial).
Plus, implementing one way in the system is much easier than creating a copy for every audited table??
I am talking about all tables in the DB, not only content or so; also an update history model is also in the same level to think in.
What you think?
If ACS 3 Model for auditing is available, can we check and discuss it?
You can check the ecommerce package for one take on auditing.