We decided against it initially because the data is very simple and would't require the overheads of versioning, security checking etc.
On 7/4/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
On 7/4/07, harvey waters <[EMAIL PROTECTED]> wrote: > We're trying to implement an audit trail of activity, (who's adding content, > deleting e.t.c). Our first thought was to record the activity in a seperate > database but this means using distributed transactions.... Why not record the audit trail info in the repository? I'm doing this in one of our apps, using a separate tree which stores audit trail events under paths like /audittrail/2007/20070530/event-1 It works well for me, and avoids the use of a different storage mechanism. -Bertrand
