On 16 Dec 2008, at 17:29, Pardee, Roy wrote: > In the olden days we would do this sort of thing with db triggers > and a 'journal' table--every UPDATE would result in a record_version > field being incremented, and the pre-update version of the rec > written out to a separate table. You can also keep all record > versions in one table & put up a view that selects out just the most > recent, but that can be problematic perf-wise. (IIRC, chunks of SAP > do the all-versions-in-one-table thing.) > > Agree that an AR plugin should be able to handle the journaling--not > sure if there is one that does. I vaguely recall an 'acts as > deleteable' or 'acts as archivable' plugin discussed here a while > back that seems like similar functionality--not sure if it would get > you all the way there.
There's also acts_as_git: http://www.caboo.se/articles/2008/11/15/new-plugin-acts_as_git All plugin based solutions have an impact on performance, don't know how good or bad acts_as_git does it. Since it uses text files to version records and works on a field-by-field basis, I wouldn't get my hopes up all too much. Maybe the developer himself can chime in on this thread. Best regards Peter De Berdt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
