On Tue, Jan 5, 2010 at 9:40 PM, Matt Jones <al2o...@gmail.com> wrote: > > > On Jan 5, 1:40 am, Curtis Jennings Schofield > <curtis.schofi...@gmail.com> wrote: >> I have the below code - I cannot use alias_method_chain unless I >> declare :accepted= before using it - i suppost the attribute methods >> are added latter - I suspect that this case is blowing away my >> alias_method_chain >> >> How can i complete this intention correctly, doing it the rails-way and >> pretty? >> > > You'll likely want to do this in an after_save callback, as the method > you've posted (if it worked) would end up drooling stray CuratedVideo > records into the DB every time a model set that value (perhaps via > mass-assignment) then didn't pass validation. > > --Matt Jones
Thanks for your response - after i realized that it wasn't going to work - i did use a call back and the _changed? and _was parts of the dirty attribute and it was as clean as i prefer and passed spec (and as you said - avoided extra useless queries).
-- 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-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
