Max Williams
2009-Oct-21 11:24 UTC
Plugin to track create, update, delete on certain tables?
Hi all I''d like to start keeping track of who has created, updated or deleted certain of our models - eg users, resources, lessons. The ''who'' would generally be simply the id that is in session[:id], ie the current user. The table to keep track would most likely have fields for user_id, record_type, record_id, transaction_type and created_at, or names to that effect anyway. This seems like the sort of thing for which a plugin would already exist, but i''ve not managed to put the right terms into google to find one. Can anyone point me at one? thanks max -- Posted via http://www.ruby-forum.com/.
Brijesh Shah
2009-Oct-21 11:45 UTC
Re: Plugin to track create, update, delete on certain tables?
Check it out below link http://github.com/collectiveidea/acts_as_audited/ This plugin will keep track of model actions... Thanks Brijesh Shah -- Posted via http://www.ruby-forum.com/.
Max Williams
2009-Oct-21 11:54 UTC
Re: Plugin to track create, update, delete on certain tables?
Brijesh Shah wrote:> Check it out below link > http://github.com/collectiveidea/acts_as_audited/ > > This plugin will keep track of model actions... > > > Thanks > Brijesh ShahLooks perfect - thanks a lot! max -- Posted via http://www.ruby-forum.com/.
Max Williams
2009-Oct-22 15:46 UTC
Re: Plugin to track create, update, delete on certain tables?
Just installed acts_as_audited, absolutely LOVE it. Fantastic. Thanks again for the pointer, and many thanks to the AAA team. :) -- Posted via http://www.ruby-forum.com/.
Robert Walker
2009-Oct-22 20:45 UTC
Re: Plugin to track create, update, delete on certain tables
Max Williams wrote:> Just installed acts_as_audited, absolutely LOVE it. Fantastic. Thanks > again for the pointer, and many thanks to the AAA team. :)If you like that you might also want to take a look at vestal versions. This not only allows you to audit changes on models, but also be able to actually see what the model looked like in the past. I know in your case you''re mostly interested in an audit trail, but vestal versions is certainly worth a look if you''re not aware of it. http://github.com/laserlemon/vestal_versions Get a quick tutorial of it here: http://railscasts.com/episodes/177-model-versioning -- Posted via http://www.ruby-forum.com/.