On Aug 18, 12:33 am, Tomasz Romanowski <li...@ruby-forum.com> wrote: > > Rails comes with 3 development environments already ready to go, look > > database.yml. In development and testing, all classes are always > > reloaded. > > This does not seem to be true. In my example above, if a class does not > derive from ActiveRecord::Base it preserves its class attributes between > requests, a plausible explanation being that it's NOT in fact reloaded. > Deriving from activerecord or not should have no incidence. How the particular class is loaded can influence reloading, the only thing that you're likely to do by accident is requiring a file explicitly
Fred > >In production they are always cached. How is this not > > exactly what you want? :) > > Very simple. I only would like to be reloading the classes that I'm > currently messing with. Reloading all the classes is a waste of time. > > -- > Posted viahttp://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.
