Ruby on Rails

On Sun, Jul 31, 2011 at 7:23 PM, Peter Song <lists@ruby-forum.com> wrote:

> Mysql or Postgresql? Or some other database.
>
> What do you prefer and does it really matter down the road? Anybody have
> disaster stories where you choose one and it turned out another would
> have been better? Do you use different dbs depending on the job or do
> you stick with the same one always?

A couple of points to note.

* The Django community recommend PostgreSQL.
* Heroku, the Rails deployment people, use PostgreSQL exclusively
behind the scenes.

PostgreSQL usage has been growing steadily for many years and has more
open source contributors and mailing list posts than MySQL. PostgreSQL
consistently differentiates itself from MySQL by advanced features and
ease of use, as well as very low bug rates. MySQL was definitely the
more popular database 7-10 years ago but I'm not sure how to measure
that any more. PostgreSQL is 25 times faster than it was 7 years ago
and the latest version looks to improve on that by significant
margins. PostgreSQL's feature set exceeds that of Oracle in some
areas, not just MySQL. PostgreSQL 9.1 should be available within about
2 months and includes fully synchronous log based replication.
PostgreSQL works well from <100MB to beyond 1TB databases.

I need to declare myself here as a PostgreSQL developer, though that
means I can provide additional details if required on any questions.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.