是否符合Mysql ACID标准?

根据Postgresql,Mysql不符合ACID标准吗?在一些博客中,我看到Mysql不符合ACID.那是真的吗?

不要在这里考虑复制,让我们考虑一个独立的以及Mysql ACID的效率如何?

在我对Mysql-ACID的理解中.

A – Atomicity (Set of transactions should all be committed if one
fails it has to rollback. Yes means all are committed , no means even
one failed it has to Rollback).

I.E. Features that supports in Mysql are.

  • start Transaction; ….. commit ;
  • auto_commit=1;

C – Consistency.

( PK,FK,UK,NOT-NULL). It adheres to Relations and constraints for
Databases. Instance a parent key can be deleted only when its child
key is removed.

I – Isolation. Isolation between users and their state of commit.

Read Repeatable Read Uncommitted Read Committed Serialized

D – Durability. At the event of DB crash innodb recovers the DB by
applying committed transaction from iblog file and discards
not-committed transaction.

Click here for the source of this question. – 是因为博客是在2001年创建的吗?

更新Jun-30-2017:根据“Evan Carroll”的回复,我亲自测试了5.7.18企业的blog实验.从实验中获得的结果似乎是Mysql不符合ACID.

解决方法:

没有

我不认为允许可重复读取中的幻像写入满足任何ACID合规性.

See this blog entry for more information.

上一篇:Acid靶机渗透


下一篇:SQL,NoSQL和NewSQL