That looks like what I was planning on doing, but a little light on the changed details.
Unless anyone has any other suggestion I'll just have to write my own. Brian On Feb 8, 11:37 pm, Erol Fornoles <[email protected]> wrote: > On Feb 9, 11:48 am, PsiPro <[email protected]> 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'shttp://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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
