Yeah, it is a bit inconsistant that the first call ends up executing different code than a subsequent call. method_missing should probably be changed to address this.
But, I don't think that will solve your original problem of needing to be able to override the read methods ... ? -Jonathan. On 5/10/06, Jeffrey Hall <[EMAIL PROTECTED]> wrote:
> That way you can simply override read_attribute_before_type_cast > and it will affect both read_attribute and the generated read_methods. Thoughts? As I see it, the inconsistancy exists in one of two places. If typecasting as performed by read_attribute really impacts performance undesirbly... then the call made by method_missing to return the attribute value during the reader's first call should be changed to match what is used in the generated reader methods. Does this stand to reason? -Jeff _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
