@Max:
Max Schubert wrote in post #996743:
> I am guessing you are in development mode with class caching off :)
> and that this behavior does not occur in test nor production mode ...
>
> Try the code with either test or production if you haven't already ...
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?
- ff
P.S.: Max: what's your handle on ruby talk? I poked around and didn't
see anything obvious
--
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 [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.
