Comparing MySQL and PostgreSQL 2

Mr. Jax writes "6 years ago Mr Poet submitted the story Comparing MySQL and PostgreSQL. Since then both databases have evolved to wherever they are today. Are the points raised 6 years ago still valid? What has changed? Are there other things to consider since then (e.g. licensing)?" This is certainly a valid question since both databases have had to evolve with the times. Have these applications been specialized to fit a particular niche market or are they both still strong competitors? What does the horizon look like for the development of these programs, especially considering the recent MySQL partnership with SCO?

Comments

Re:Helllooo?? Editors??

[geoffspear]

You haven't heard of Ask Slashdot?

You must be new here. How'd you get a user ID in the 24000s? Are they recycling old ones now?

Re:My point of view

[cortana]

postgresql (7.5.0) experimental; urgency=low

    * Initial release of transition package to new multicluster/multiversion
        architecture.

  -- Martin Pitt Tue, 15 Feb 2005 22:58:37 +0100

Silly wabbit, using Unstable on a production machine. ;)

Re:Get off it ScuttleMonkey

[Doc Ruby]

Don't worry, zealot. As usual, a blowhard hypocrite will be along presently to tell you what to think.

Re:popularity

[gizmonic]

MySQL's biggest problem is that if you try to update or insert with invalid data, in many cases it successfully inserts wrong data.

While that can be annoying, to be sure, why do people rely on the database to do their data validation? That should be done in the application code long before you ever run an insert or update. If you're trying to insert invlaid data, you're the only one to blame.