You're just wrong. Order.all is simply an alias for Order.find(:all), and as such and array of Orders - *not an associations*. (see http://api.rubyonrails.org/classes/ActiveRecord/Base.html#M001966). There's no N+1 problem here.
p.s. I just noticed the grandfather quotes code in the form Orders.find. This is clearly a sign the author isn't even used with basic Rails naming conventions.
I always stumble across blogs with long explanations and tutorials on things so simple as *starting a service at boot* - and not even an arbitrary service, a common service like Ferret.
So what's Ferret or you inability to manage system services got to do with Rails ?
Not to mention that it's easy to do something idiotic in Rails. For example:
Orders.all.each { |order|
With power comes responsibility - something you ought to know by now. You can do something just as stupid using _any_ other web framework + ORM; this is not a problem in Rails, it's a problem with the way you choose to solve the problem at hand.
Go guys! We're counting on you!
How about counting on yourself and getting some work done (on the Rails framework) without waiting for others to solve your problems ?
The rate at which a disease spreads through a corn field is a precise measurement of the speed of blight.
