3 ms·
The thing is I wasn't trying to convince anyone though :) I doubt anyone here will be willing to shell out the money for a license. Although, Azure might make
by TheOsiris 11y ago
The thing is I wasn't trying to convince anyone though :) I doubt anyone here will be willing to shell out the money for a license. Although, Azure might make it affordable but I hated the limitations they put on the mssql instances (can't remember them rn).
My biggest problem with myssql is that it is very immature. Biggest problems I have with it are (right now, b/c that's what I'm facing atm): transaction isolation and stored procedures. I'm pretty sure pg has the same lame transaction isolation issues as well.
- vertex-four 11y agoWhat do you mean Postgres has tx isolation issues? The entire point of preferring it over mySQL is that it does most things around that area properly.
- TheOsiris 11y agonot from my experience. last I checked, neither one of them supports nested transactions
- rosser 11y agoWhatever transaction isolation issues PostgreSQL might have, I guarantee you it doesn't have the "same lame" ones as MySQL. As just one example: "range locking". Look it up.
- TheOsiris 11y agothe biggest one for me is the lack of support for nested transactions
- rosser 11y agoWhich you can effectively accomplish in PostgreSQL with SAVEPOINTs. In fact, with those, you can have arbitrarily complicated nesting of "transactions", though that does start to smell a bit like a foot-gun pretty quickly. http://www.postgresql.org/docs/current/static/sql-savepoint.html http://www.postgresql.org/docs/current/static/sql-savepoint....