MYSQL集群与INNODB事务处理的对比总结
2008-02-19 18:36
1181 查看
举个例子吧。自己实验了一下。
对MYSQL的innodb 和 ndb 引擎对事务的处理
对于NDB
mysql> begin;
Query OK, 0 rows affected (0.00 sec)
mysql> insert into foo values(1);
Query OK, 1 row affected (0.01 sec)
mysql> insert into foo values(1);
ERROR 1062 (23000): Duplicate entry '1' for key 'PRIMARY'
mysql> commit;
ERROR 1296 (HY000): Got error 4350 'Transaction already aborted' from NDBCLUSTER
mysql> show errors;
+-------+------+--------------------------------------------------------------+
| Level | Code | Message |
+-------+------+--------------------------------------------------------------+
| Error | 1296 | Got error 4350 'Transaction already aborted' from NDB |
| Error | 1296 | Got error 4350 'Transaction already aborted' from NDBCLUSTER |
| Error | 1180 | Got error 4350 during COMMIT |
+-------+------+--------------------------------------------------------------+
3 rows in set (0.00 sec)
mysql> select * from foo;
Empty set (0.00 sec)
对于INNODB
mysql> create table foo2 (i int not null primary key) engine innodb;
Query OK, 0 rows affected (0.00 sec)
mysql> begin;
Query OK, 0 rows affected (0.00 sec)
mysql> insert into foo2 values(1);
Query OK, 1 row affected (0.00 sec)
mysql> insert into foo2 values(1);
ERROR 1062 (23000): Duplicate entry '1' for key 'PRIMARY'
mysql> commit;
Query OK, 0 rows affected (0.00 sec)
mysql> select * from foo2;
+---+
| i |
+---+
| 1 |
+---+
1 row in set (0.00 sec)
NDB遇到错误就终止了,回滚到最初的状态。
而INNODB遇到错误还是继续执行已经成功事务。
其他的等待测试。。。
本文出自 “上帝,咱们不见不散!” 博客,转载请与作者联系!
对MYSQL的innodb 和 ndb 引擎对事务的处理
对于NDB
mysql> begin;
Query OK, 0 rows affected (0.00 sec)
mysql> insert into foo values(1);
Query OK, 1 row affected (0.01 sec)
mysql> insert into foo values(1);
ERROR 1062 (23000): Duplicate entry '1' for key 'PRIMARY'
mysql> commit;
ERROR 1296 (HY000): Got error 4350 'Transaction already aborted' from NDBCLUSTER
mysql> show errors;
+-------+------+--------------------------------------------------------------+
| Level | Code | Message |
+-------+------+--------------------------------------------------------------+
| Error | 1296 | Got error 4350 'Transaction already aborted' from NDB |
| Error | 1296 | Got error 4350 'Transaction already aborted' from NDBCLUSTER |
| Error | 1180 | Got error 4350 during COMMIT |
+-------+------+--------------------------------------------------------------+
3 rows in set (0.00 sec)
mysql> select * from foo;
Empty set (0.00 sec)
对于INNODB
mysql> create table foo2 (i int not null primary key) engine innodb;
Query OK, 0 rows affected (0.00 sec)
mysql> begin;
Query OK, 0 rows affected (0.00 sec)
mysql> insert into foo2 values(1);
Query OK, 1 row affected (0.00 sec)
mysql> insert into foo2 values(1);
ERROR 1062 (23000): Duplicate entry '1' for key 'PRIMARY'
mysql> commit;
Query OK, 0 rows affected (0.00 sec)
mysql> select * from foo2;
+---+
| i |
+---+
| 1 |
+---+
1 row in set (0.00 sec)
NDB遇到错误就终止了,回滚到最初的状态。
而INNODB遇到错误还是继续执行已经成功事务。
其他的等待测试。。。
本文出自 “上帝,咱们不见不散!” 博客,转载请与作者联系!
相关文章推荐
- 面试常考 MySQL优化 事务处理 MyISAM和InnoDB索引实现
- MySQL存储引擎InnoDB和MyISAM对比总结
- PHP 处理 MySQL INNODB 事务回滚(ThinkPHP、MySQL、PDO)
- MySQL存储引擎Innodb和MyISAM对比总结
- 并发控制 mysql InnoDB锁表,事务及处理方法
- MySQL Innodb事务编程问题和处理
- MySQL存储引擎Innodb和MyISAM对比总结
- Mysql表的七种引擎类型,InnoDB和MyISAM引擎对比区别总结
- Mysql表的七种引擎类型,InnoDB和MyISAM引擎对比区别总结
- 资深架构师Sum的故事:(Mysql)InnoDB下,存储过程中事务的处理
- EF 事务处理 (InnoDB Engine的MySQL表也可以)
- PHP PDO事务处理及MYSQLengine=InnoDB
- MYSQL--事务处理
- mysql 中 MyISAM和InnoDB 对比
- Mysql学习总结(13)——使用JDBC处理MySQL大数据
- mysql的innodb中事务日志(redo log)ib_logfile
- PHP与MYSQL事务处理
- [MYSQL -26]控制事务处理
- MySQL InnoDB四个事务级别 与 脏读、不反复读、幻读
- MySQL Innodb的事务部分 函数调用关系