5 ms·
This is also my opinion and I think before that MySQL was known for fast and Postgres for features and correctness. I think the change went both ways, people re
by weinzierl 3y ago
This is also my opinion and I think before that MySQL was known for fast and Postgres for features and correctness. I think the change went both ways, people realized that MySQL's casual approach only got them so far and at the same time Postgres focused more on performance without giving up its existing qualities. I think Postgres became cool when it became fast (too).
- ASalazarMX 3y agoThe last straw was when Oracle bought MySQL, and it was forked to MariaSQL. Postgres went from the nerdy awkward kid to the nerdy cool kid, while MySQL started drinking, getting split personalities, and living off his past fame.
- CRConrad 3y ago> MariaSQL MariaDB.
- hashtag-til 3y agoThe “new” name never really stick…
- CRConrad 3y agoWas MariaDB ever called MariaSQL? When?
- hashtag-til 3y agoI referred to MySQL vs MariaDB
- CRConrad 3y agoThen you were even more wrong. MariaDB wasn't just "a new name" for MySQL.
- ASalazarMX 3y agoIt was my mistake, I misremembered MariaDB, but can't edit my comment now. In my defense, I've barely thought of it since 2009, when it was forked. On the other hand, I've worked with MySQL a few times in the same period, mostly because Oracle, whatever its failings, has kept MySQL alive. Not thriving, but alive. I'm so glad they didn't buy PostgreSQL.
- hashtag-til 3y agoIt is an easy mistake to make :) - it seems like ages ago when MySQL was sort of state of the art. I was there too when Oracle took over and everbody knew what was going to happen. Happy also that pgsql was not a victim and is still alive!
- chx 3y agoI think even Sun buying MySQL already hurt MySQL and helped PostgreSQL. Back in 2006, the startup I was with moved from PostgreSQL to MySQL because the support we were able to find was both expensive (300 USD/hr) and not satisfactory. Back then MySQL AB (this was before Sun) gave us a 10K two year deal on three servers and they had excellent response times and knowledgeable support. For PostgreSQL the year 2010 when Salesforce bought Heroku (big plus) and Oracle bought MySQL (big minus for MySQL so indirect big plus to PostgreSQL) was the breakthrough, I would say. That MySQL didn't get CTE and window functions until 2018 is a sad joke.
- paulddraper 3y ago> MySQL was known for fast and Postgres for features and correctness That's still the case. In particular, MySQL is faster for updates (no MVCC), but that comes at a cost that I would be hesitant to pay.
- evanelias 3y agoInnoDB (MySQL's default storage engine since 2010) has always used MVCC. Its MVCC implementation is arguably better than Postgres's in some important ways, see e.g. https://ottertune.com/blog/the-part-of-postgresql-we-hate-the-most/ https://ottertune.com/blog/the-part-of-postgresql-we-hate-th...
- code_runner 3y agoI came from a MSSQL background and eventually worked on an MySQL project with somebody who had a TON of MySQL experience by way of symfony. I was explaining that not all of his non-aggregated columns were in his group by, so his query wasn't going to work.... but what do you know, MySQL will just return whatever it feels like from the group in that situation. I expected it not to run at all. I think there are some flags etc you can use to enable to stricter behavior but it was one of the wildest footguns I've ever seen.