Hacker News new | ask | show | jobs
by imanaccount247 4254 days ago
Just the small list of flaws that we hit trying to use mysql (there's dozens more, and we're not including all the "mysql silently inserts invalid data" gotchas):

no check constraints

views with aggregates are too slow to be used

no expression indexes

triggers don't fire on cascaded actions

no window functions

can't set default values to be the result of a function

no transactional DDL

doesn't have multiple databases, just schemas misnamed as databases

rollbacks are orders of magnitude slower than other RDBMS, and if it is interrupted it can corrupt the database

functions can't use prepare/execute, so no dynamic SQL in functions

subqueries are broken: can't modify and select from the same table

functions can't be called recursively (seriously? is this 1962?)

triggers can't alter the table they are firing against

stored procedures can't be invoked from prepare/execute

"slow query" log has a completely useless resolution of seconds

2 comments

Agree with most of these issues but your last claim is only true for older versions of MySQL. Newer versions do support microsecond resolution[1].

1- http://hackmysql.com/slowlog

Mysql does have a much better durability solution -galera cluster IMO... Does Postgres have something similar?
Galera is not a durability solution. Yes, postgresql has multi-master synchronous replication. It is also not a durability solution.