5 ms·
Article is from 2014; does all of this still apply? I'm just trying to understand the relevance, other than MySQL is a flaming death trap which everyone should
by spacemanmatt 11y ago
Article is from 2014; does all of this still apply? I'm just trying to understand the relevance, other than MySQL is a flaming death trap which everyone should be warned about regularly.
- kidmenot 11y agoI would be happy to be proven wrong (thankfully I have dealt exclusively with Postgres in the last two years or so), but I think most of the warts and shortcomings the post talks about are still extant. Off the top of my head, I can add that you can't have subselects in views (which is preposterous), nor can you materialize views. Also, I don't believe you can have function-based indexes, and most certainly you can't pivot tables easily and CTEs are not supported. I think 5.7 (if it's been released) finally brought the ability to create multiple triggers for the same event. Until 5.6 you could specify only one. In short: MySQL is no fun. Choose Postgres or any other decent system, but just steer clear of the damn dolphin.
- spacemanmatt 11y ago> MySQL is no fun. Choose Postgres or any other decent system, but just steer clear of the damn dolphin. Ahahahahahahaha. Thank you. That was amusing and also helpful.