3 ms·
As far as I understand mySQL - You have to choose engines - Some features (e.g. ACID Transactions) don't work in some engines. I'm not sure exactly why this
by WorkerBee 17y ago
As far as I understand mySQL
- You have to choose engines
- Some features (e.g. ACID Transactions) don't work in some engines.
I'm not sure exactly why this is a feature.
In PostgreSQL (and in most sane DB software)
- You don't have to choose engines
- All features work all the time. There's no posiblity of foolery like, say, beginning a transaction and then updating two tables, then finding that one of the tables will ignore the transaction but the other won't.
- rimantas 17y agoAll features work all the time That's the key. Even features which you may not need in particular scenario will add their overhead.
- WorkerBee 17y agoYou might not need transactions now, but what if you need then later? If the speed difference between postgress and MySQL performance (what is that, 10%? a boundary case ) is going to kill your app, then get a 10% faster server.
- rimantas 17y agoIn MySQL case: switch from MyISAM to InnoDB or Falcon (ALTER TABLE table ENGINE=Engine, that's it). What if you don't need transactions in PG? Let's not forget MySQL has engines like MEMORY, ARCHIVE, BLACKHOLE (not to mention third party engines).
- WorkerBee 17y agoIf you don't need transactions in a DB engine (PG, Oracle, MS SQL, etc), then you don't use them. I was trying to forget about MySQL and it's plethora of engines.