What are the problems with MySQL that cause it to get bad press? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 12 years ago.

I'm primarily a PostgreSQL user and I frequently hear about MySQL getting bad press (much like PHP). However, I don't actually know or understand why this happens. So I'm curious, what are the large problems with MySQL that cause developers to prefer othe开发者_JAVA百科r database solutions, and how real are the problems in the current releases?

---

I read something about this just yesterday in Phil Greenspun's blog:

Now that MySQL is 16 years old, I was surprised at the things that they’ve yet to accomplish. For example, the C in ACID is “Consistency”, i.e., being able to enforce rules in the SQL data model and using the RDBMS as a last line of defense against programmer mistakes. Yet MySQL silently fails to enforce any CHECK constraint. Similarly, when students would GROUP BY column_a and then SELECT column_b (where column_b had multiple values within each group), instead of raising an error as Oracle, Postgres, or SQL Server would, MySQL happily picks a column_b value at random and includes it. I don’t understand why people use it.

Also, the MySQL Gotchas page is a classic list.