[dev] Audit trailing in Hermes
Chuck Hagenbuch
chuck at horde.org
Wed Nov 14 16:18:36 UTC 2007
Quoting Vinay Kumar <vinay.kumar at ejyothi.com>:
> Thanks for the suggestions.
>
> Actually we are looking only for EDIT action on time slices . I think
> logging all actions is good one but not essential now. Since we are
> doing only the audit trail on EDIT action, duplicating record is a
> good choice. The edit operations are rare in ideal situation and the
> table may not grow larger. We would also like to track the changes in
> all the fields of the timeslice table, so I think that this approach
> will simplify the design.
>
> Kindly share your ideas also, so that we can evaluate the pros and
> cons of the two approaches.
I strongly object to simply creating duplicate rows in the same table.
No matter the amount of data that is being duplicated - we have to
duplicate *some* amount with audit logging - putting the duplicate
data in the same table makes the data model seriously unclear.
-chuck
More information about the dev
mailing list