Ryan Bigg wrote:
DC, you've opened up a can of worms. A lot of people will argue
MySQL's better than PostgreSQL and vice-versa. Prepare for a long,
Hm...let's see if we can nip it in the bud...come on y'all, let's be
like Barney Fife!
SQLite is a decent database for embedded applications and development.
_Possibly_ for production if your traffic is low and your storage needs
are minimal. But if you plan to have a lot of data and/or a lot of
traffic, look elsewhere. Both PostgreSQL and MySQL are fine databases.
They can both be tuned to run at about the same level of performance.
Which one is better is, for all intents and purposes here, a matter of
opinion. There might be some technical reasons why one is better than
the other in this or that area, but unless you are a database engine
geek, it probably won't matter to you. Shoot, you don't have to choose
either one of those if you don't want to. There was a post just the
other day about another Rails database adapter for MonetDB (or something
like that), and if the numbers on the web site are accurate, it beats
MySQL and PostgreSQL both, hands down. Didn't Oracle release an
"express" version of their database a year or two ago? You might even be
able to use that as I believe there is an oracle adapter somewhere. The
point is that all of these databases are going to be sufficient. Which
one you choose depends on what you are doing. I use PostgreSQL, mainly
because my primary client uses it and I don't want two database engines
running at the same time. So I do everything on PostgreSQL. Could I use
MySQL? Sure. As of right now, I'm not making use of anything Postgres
specific (I don't think).