Fearless, On Thu, May 5, 2011 at 1:22 AM, Fearless Fool <[email protected]> wrote: > Thanks for the tip. Rather than try to get my db migrated over to > production mode, I simply edited the line in > config/environments/development.rb to read: > > config.cache_classes = true > > ... and now it works. BUT: this is a bug, right?
Well, not really a bug - it is 'behavior as designed' but it is also a 'fail' for those of us using 'meta-programming as designed LOL' because meta-programming requires that classes be loaded and that the callbacks associated with Object and Class get called! > P.S.: Max: what's your handle on ruby talk? I poked around and didn't > see anything obvious I am using the Google group to respond, so no handle :). Were you able to find the code I used to work around the class caching issue? It is not pretty but it works. - Max -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
