GitHub Sale: sign up for any paid plan this week and pay nothing until January 1, 2009!  [ hide ]

public
Description: Provides a history of attribute and association updates for models. This coincides with a versioning system (such as acts_as_versioned). When used in tandem, you get both a history of changes and a history of what changed.
Homepage: http://rubyforge.org/projects/ruby-shadow/
Clone URL: git://github.com/TheBreeze/shadow.git
Initial import of shadow.
TheBreeze (author)
Fri May 02 15:52:03 -0700 2008
commit  26dea2fac83eb402cd3f314cf2bdfaaa5147f193
tree    5d86ed600af01eeb350f2262edb39b1832c3cb59

Comments

  • Hey Jordan, saw your presentation on SD.rb podcast and am curious about shadow….looking at the code (not running it yet), it seems that you could be using dirty objects to determine what has changed, instead of doing a separate find and compare as you’re doing now in the determine_updated_attributes method.

    http://ryandaigle.com/articles/2008/3/31/what-s-new-in-edge-rails-dirty-objects

    I’d be curious to try this out…what’s especially interesting is that you can do some_object.changes and get not only which attributes changed, but the before and after versions of them, which could effectively eliminate any ties you have with acts as versioned, and all this data could theoretically be stored in the tables you generate. Just an idea, but kind of interesting.

    (First github comment here, hope it finds it way to you)

    Cameron