Hi Michael - i kind of expected that kind of reply :) The reason that i'm doing it in this case is that i've overridden the set method for one of my foreign keys to do some other stuff after changing the foreign key. But, it just occurred to me that a better way to handle that is via a dirty models sort of approach of not getting involved in the set method but detecting the change instead. What's the simplest way to do that, do you know? -- Posted via http://www.ruby-forum.com/.
-- 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.
