Re: Re: Object Version Control, or at least edit log

Mat Brown
2010-02-09T11:48:11Z

On Mon, Feb 8, 2010 at 23:37, Erol Fornoles
<erol.fornoles-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> On Feb 9, 11:48 am, PsiPro
<arjes...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> Hello all,
>>
>> I need to create a object history, as I''ll have multiple
editors for a
>> site i am working on. Of course it would be great to have the ability
>> to restore an object to its state and undo the damage due to a bad
>> editor, but I''ll settle for a system that will tell me who to
blame.
>>
>> Basically I want to track who changed what on what object. I would
>> like your input on the best way to do this, or someone to stop me if
>> its already been done.
>>
>> My first thought, was to simply make the activity log and log the
>> "self.changed.to_yaml" to the database, but I would like more
>> information then that if possible, adding this along with the
>> "self.to_yaml" would provide semi-readable output on the
changed
>> values but no details on the original values.
>>
>> I would, if at all possible like to make it a bit more detailed, but
>> right now I''m looking for someone with a bit more experience
in AR to
>> provide me with some tips/tricks.
>>
>> Thanks,
>> Brian
>
> There''s http://wiki.github.com/collectiveidea/acts_as_audited/.
That
> might work for your use case.
>
> --
> You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
> To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
>
>

Also might want to check out different database solutions - CouchDB
for instance has versioning built-in for all documents.