[dev] Audit trailing in Hermes

[Chuck Hagenbuch]

Quoting Vinay Kumar <vinay.kumar at ejyothi.com>:

> Basically there are two approaches to keep the changes. One solution
> is to create a new table to keep all the changes. The second method is
> to use the existing table with some additional fields.
>
> I would prefer the second approach, because the edit/delete operations
>   on a timeslice row is probably minimal. The basic ideas is to add a
> new timeslice entry, whenever a timeslice is edited. Store the ID of
> the original timeslice  as timeslice_parentid in the new entry. Also
> mark the new timeslice as NOT EDITED  using another field.

That means you have to duplicate ALL of your data on edits, deletes,  
submissions, approvals... any possible action. Seems like a waste - as  
well as making the data model not very clear to someone looking at it  
- as opposed to a nice, lean audit table (that in addition could be a  
bit less lean but much more useful by storing information about what  
actually happened).

My initial impression, anyway.

-chuck