Every Rails app that I’ve ever worked on has had to break away from the “ActiveRecord way” at some point, for some part of the app. But it’s not an all-or-nothing question. Most of the time, the standard relational/ActiveRecord approach works perfectly well, and the convenience of following the Rails golden path is completely worthwhile. But most interesting apps will run into at least a few points where the standard tools break down, and you need to access your data differently.
What do you think?
What's to disagree with? Who on Earth would ever claim "ActiveRecord
is all you'll ever need"?
Like it says "Most of the time, the standard relational/ActiveRecord
approach works perfectly well [but] apps will run into at least a few
points where the standard tools break down"
Who hasn't had to do do at least one find_by_sql to do some
cross-tabbing in the DB to save processing time?
He does not say that AR own methods are not enough, he says that an app needs to be based on AR and other other tool that are them selves based on NoSQL.
The quotation does not claim that. What it says is that the
ActiveRecord ORM does not handle every situation well. Which can be
said of Ruby (or any other language, methodology, persistence store,
religious belief, etc.) for that matter.
Also you may give a try for NoSQL:
MongoDB or CouchDB
There is not The Best DB and also not any Best ORM for sure. Depends
on your needs. Maybe ActiveRecord has smthg with foreign keys but Rein
gem can solve this issue as I heard(haven't used since I'm fun of DM):
http://github.com/nullobject/rein