CSK Furniture

Get dirty objects in Rails

Soiled object functionality has been in cutting side rails for a month now, allowing you to see what changes have been made to an reality prior to sparing it. Here's an example from Ryan's cutting side rails blog -branch = Article.find(:first)
paragraph.changed? #=> untrue

# Track changes to single attributes with
# attr_name_changed? accessor
member.title #=> "Inscription"
particular.title = "New Inscription"
division.title_changed? #=> veritable

# Access foregoing value with attr_name_was accessor
point.title_was #=> "Inscription"

# See both antecedent and current worth with attr_name_make some change in accessor
part.title_modify #=> ["Inscription", "New Inscription"]Begrimed objects should be to be turned to account with the next release of Rails. Unfortunately, you want it in your Rails 2.0 throw out right off and can't wait. Well, you're in fortune; adding this functionality to a Rails throw turns out to be lifeless simple expressions of gratitude to Dirty being a critically decoupled module.
Here's what you strait to do:Download the origin for dirty.rb from http://dev.rubyonrails.org/browser/stem/activerecord/lib/effective_record/foul.rb?rev=9127. I'm specifically picking revisal 9127 because later versions mix partial updates (also new in cutting side rails), which complicates matters.Once you've got the rasp create a directory called influential_record under RAILS_Foundation/config/initializers and transcript dirty.rb into it. Thus, if your shoot forward is under /home/act/myproj, the footway to dirty.rb should be /abode/work/myproj/config/initializers/begrimed.rb.Reopen operant_record and mixin Nasty. Do this by creating a toothed tool called in force_record.rb under RAILS_Base/config/initializers and putting the...

Read more...

Kzk::Anurag-Prem dining table scene of 27th march07

Dining Table News

Table Directory