Robby on Rails

a million mysql users: I’ve never had a problem with it. postgresql users: Yes, that’s why you’re still a mysql user.

When will PostgreSQL evangelists learn that “good enough” is good enough for 99% of web apps (i.e. low- to medium-traffic, simple data, basic CRUD)?

People calling MySQL a “toy” is a counter-productive argument because it seems to imply that, if it works for you, your hard work must amount to a “toy” project.

I prefer Postgres by leaps and bounds, but if MySQL works for you, good for you.

I suppose the real issue here is whether MySQL is your choice because its popular or it fits your functionality level, and whether that matters.

If I need a lightweight database I tend to go towards SQLite. If I need robust features straight away, I gravitate towards Postgres. MySQL can handle either cases though.

I think the larger concern for MySQL users should be the dual license nature. What do you do when you want your product to go public? Do you need to buy a license. Currently not, when its a database backing a client server application but what if Sun changes their mind? Do you think your small start up, university, or non profit has the legal staff to challenge Sun’s? This is what scares me away from MySQL. With the availability of Postgres, I have a robust alternative that in many capacities meets or exceeds the functionality of MySQL, without the license issue.

MySQL is a thin veneer above a set of decent technologies. Sleepycat (berkeley db) and Innodb were actually written by people that did know what they were doing. When MySQL tried to implement ACID, they simply couldn’t do it, they’re were a bunch of script kiddies that have risen off the backs of a talented few.

Anyhow Innodb and Sleepycat are now owned by Oracle. Whereas the MySQL ‘brand’ and it’s veneer (some installers and an SQL parser) were bought by Sun for US$1Bn. Smell something wrong here? I certainly no longer own any shares in Sun.

I still don’t understand, why use a system that is guaranteed to fail in such a way as to cause you hard to trace support issues? Job for life? Are you those types of people that just patch things up by hacking the database, think no more of it and go to fix the next error on some other system sitting on top of MySQL? If ‘good enough’ is the benchmark by which you develop software, go ahead and use MySQL, otherwise use a proper database.

I also appreciate postresql, but in fact mysql has many users.

Hi,

I have switched my Rails app from MySQL to PostgreSQL because of the license, and because Postgre has many features which I don’t use yet, and which will keep me busy on rainy weekends.

With my very own mediocre benchmarks, I tend to see that Postgre is slightly faster than MySQL.

My take on it:

Despite superior performance, licensing, and features, PostgreSQL is just a very awkward name for software. I bet it if was called “Moo” or something like that it would be adopted very quickly by the Rails and open-source community.

How exactly do you say “PostgreSQL”? It looks like gibberish.