|Re: [CDO] Usage of property 'supportingAudits' in server config [message #899116 is a reply to message #899062]
||Mon, 30 July 2012 15:04
|| Eike Stepper
Registered: July 2009
Am 30.07.2012 14:13, schrieb Uri JOC:|
> Hello and good day,
> I am new to CDO but have nevertheless been working with it for some weeks now.
> Right now I'm using DBStore as CDO store variant. I have come across the property 'supportingAudits' and would like to
> see it in action, but I couldn't find any examples to get into it faster. Could someone please provide a short HowTo
> so I can try it out in our application? E. g. what do I have to give an Object so it gets audited? I have the prop in
> cdo-server-db.xml set, but of course I need a little bit more.
I don't have the time to write a how-to about auditing but it's not that difficult. You set the supportingAudits
property to true on a *new* repository. Then, whenever your client commits changes the old revisions are not overwritten
but kept in the DB. Note, that CDOTransaction.commit() returns a CDOCommitInfo which, in turn, provides you with the
exact commit timestamp (the commit ID). You can use this timestamp (or any other timestamp between repository creation
and now) with CDOView.setTimeStamp() to look at the object graph as it was at that time.
Auditing is a repository-wide setting and can not be different for particular objects.
> Further, until now I am not sure about its functionality (supportingAudits), besides providing finer grained
> revisioning for the Objects. e. g. modify an obj. 5x -> get five versions of the object in the database. Is this right?
Yes, that sounds right.
Powered by FUDForum
. Page generated in 0.02104 seconds