On Wed, Jul 15, 2015 at 12:36 AM, Zdravko Balorda <li...@ruby-forum.com> 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 changes (and changer identity). I have one app that requires that kind of tracking, currently provided by <https://github.com/collectiveidea/audited> but there are other options: <https://www.ruby-toolbox.com/search?utf8=%E2%9C%93&q=audit> HTH, -- Hassan Schroeder ------------------------ hassan.schroe...@gmail.com http://about.me/hassanschroeder twitter: @hassan Consulting Availability : Silicon Valley or remote -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yDE1vmE%3Do5bpQB2kWuZt_2PkT5QZzC169XgTwJhLys-xA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
