[Rails] Re: How to implement more database adapters for Active Record

[David Heinemeier Hansson]

> Although I suspect there is already broad agreement on this, I'll 
> point out that
> in ActiveRecord, we can't ignore database optimization. Every database 
> is
> _designed_ to be optimized to get acceptable performance. Unlike 
> program
> optimization, it's generally not optional. It would be great if Rails 
> could define conventions that facilitated useful database optimization 
> with minimal code changes and certainly without falling back to 
> rolling your own SQL.

I definitely agree. Put all the database specific knowledge about how 
things should work into the adapters. Much everything but making the AR 
user API more complicated is fair game.
--
David Heinemeier Hansson,
http://www.basecamphq.com/   -- Web-based Project Management
http://www.rubyonrails.org/  -- Web-application framework for Ruby
http://macromates.com/       -- TextMate: Code and markup editor (OS X)
http://www.loudthinking.com/ -- Broadcasting Brain