I've seen this confusion several times. Let me explain.

In production we eager load from a few places. Reason is
thread-safety, and it is also COW-friendly for multi-process.

Now, since Rails eager loads model/user.rb, the User constant won't
trigger const_missing in production. But const_missing is still there,
and custom directories added to autoload_paths get autoloading just
fine.

-- 
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 [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-core?hl=en.

Reply via email to