I like to trot out this old gem[1] when people wonder why there's so much hate for MySQL.
Nontransactional DDL alone is sufficient to classify it as a toy DB for me. Yes, I've been personally bitten by it.
Nontransactional DDL alone is sufficient to classify it as a toy DB for me. Yes, I've been personally bitten by it.
[1] https://stackoverflow.com/questions/4711447/oracle-ddl-and-t...
[0] - https://dev.mysql.com/doc/refman/5.7/en/cannot-roll-back.htm...
And https://mysqlserverteam.com/new-defaults-in-mysql-8-0/
Previously on HN: https://news.ycombinator.com/item?id=5122299
Personally, I only use MySQL and derivatives where I have to (basically WordPress.)
... have dedicated hundreds of engineers and millions of dollars to nothing more than keeping MySQL up, running, and not crapping the bed every time someone looks at it funny. If you can afford that resource expenditure, by all means go nuts with MySQL. Most companies can't and would be far better served by something which doesn't need that amount of handholding to serve its basic purpose.
I think by the time Postgres sorted itself out into a more user/admin-friendly system (which is still fairly recently, really), MySQL had pretty much conquered the "quick and easy" mindshare and was deeply embedded almost everywhere.
And if you've spent millions of dollars architecting your systems such that MySQL's flaws aren't killer issues, there's very little financial benefit to switching, I guess.
Following on from that, I suspect a lot of large companies use MySQL because they always have, not because it's actually any good. For example, Basecamp used MySQL while I was there, but I never met a single Sysadmin there who would use it over Postgres if they were to start a new project.
MySql and PHP are good. They do the job they were designed for in a cost effective way and of course that means there will be trade offs.
Sure, you can knock up a contact form in it really quickly, but that ease of use hides significant dangers.
I've programmed it, it's a terrible language.
Eventually Postgres caught up in most things, and the delay was in some part because of implementing those features "correctly" and with more thought, but it's still a delay that hurt the uptake in the early days.