5 ms·
What's the alternative? MySQL? No transactional DDL, immediate fail.
by stickfigure 2y ago
What's the alternative? MySQL? No transactional DDL, immediate fail.
- jes5199 2y agoI worked for a company that migrated from mysql to postgres, but then got big enough they wanted to hire fulltime database experts and ended up migrating back to mysql because it was easier to find talent
- bastawhiz 2y agoDunno if that says much about Postgres, but it says a lot about the company
- deleted 2y ago[deleted]
- appendix-rock 2y ago[dead]
- icedchai 2y agoUgh. I worked with MySQL earlier in my career (until about 10 years ago.) All the companies since have been Postgres. All my personal projects are Postgres. I can't imagine going back.
- cosmotic 2y agoIt's not just DDL that isn't transactional, there's a whole bunch of other things that aren't. And they break the transactionality silently. It's like an obstical course where bumping into something might be fatal.
- evanelias 2y agoWhat specific non-DDL things are you referring to here? Aside from DDL, the only other major ones are manipulating users/grants, manipulating replication, a small number of other administrative commands, and LOCK TABLES. This is all documented very clearly on https://dev.mysql.com/doc/refman/8.4/en/implicit-commit.html https://dev.mysql.com/doc/refman/8.4/en/implicit-commit.html. Hardly an "obstical course".
- stickfigure 2y ago"Aside from missing his head, the patient appears to be in fine shape."
- evanelias 2y agoThat hardly seems equivalent. Why do you need to e.g. reconfigure replication inside of a transaction in the first place? The lack of transactional DDL is a totally valid complaint, but the non-DDL stuff is just a total head-scratcher to me. Aside from DDL, implicit commits have literally never impacted me in my 21 years of using MySQL.
- stickfigure 2y agoSorry - I was trying to make light of the discussion. DDL is so important that it's silly to talk about the other stuff.
- cvalka 2y agoTiDB