This post originated from an RSS feed registered with Ruby Buzz
by Jeremy Voorhis.
Original Post: Just a friendly reminder ;)
Feed Title: JVoorhis
Feed URL: http://feeds.feedburner.com/jvoorhis
Feed Description: JVoorhis is a Rubyist in northeast Ohio. He rambles about Ruby on Rails, development practices, other frameworks such as Django, and on other days he is just full of snark.
Despite the constant conjunction between Rails howto articles, examples in books and David Heinemeier Hanssion interviews, Rails supports far more than just MySQL with its ActiveRecord object-relational mapper.
At PLANET ARGON, we almost exclusively use PostgreSQL in Ruby on Rails development projects that we start from scratch, and we have also performed several MySQL to PostgreSQL migrations for Rails applications. In fact, the database.yml file in our modified default Rails application skeleton is preconfigured to use postgres, and until only two weeks ago during my three-month tenure at PLANET ARGON have I had to install MySQL on my shiny company PowerBook.
I myself prefer PostgreSQL for personal projects, but when I am dealing with small things, I sometimes prefer a SQLite3 database if only for the ease of portability!
Also, if you are comfortable with lower-level database programming, you may try your hand at following these instructions to create an ActiveRecord adapter for the RDBMS of your choice.