> Happens all the time. The current ActiveRecord behaviour is weird > because it breaks that expectation.
You're describing the current behaviour of active record and it's use of method_missing to trigger generate_read_methods, and the lack of generate write methods. It leads to other crazy stuff like >> Post.public_instance_methods.grep(/body/) => [] >> Post.find(1).body => "Howdy World" >> Post.public_instance_methods.grep(/body/) => ["body?", "body"] I agree that this is counter intuitive, if you have a fix for this, I'd definitely be interested in applying it, the current behaviour causes problems here and in other cases. However this is the problem that should be fixed, not adding a callback to work around existing confusing implementation of our attribute related methods. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
