Thanks! This seems very useful.
For changes without going through Rails app, well I'm not sure when
enough is enough. At db level one can not catch the current_user.
But anyway this will do. Thanks, guys.
Regards, Zdravko
--
Posted via http://www.ruby-forum.com/.
--
You received this message
On Wed, Jul 15, 2015 at 12:36 AM, Zdravko Balorda wrote:
> The aim is to find an exact point when some specific change in the
> database has occurred and who did it, and to document it.
OK, that sounds less like "playback" and more like "audit" - keeping
a running record of attribute value chang
Hi!
You've got there a few good points!
I was hoping that playback could be based on requests only. More I think
of it, it would need to save responses, too.
To answer your questions:
1. Errors perhaps need not to be saved. Although, when everything is
saved it may lead to a huge amount of space,
3 matches
Mail list logo
