表结构:
CREATE TABLE `t1` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`c1` int(11) NOT NULL,
`c2` int(11) NOT NULL,
`c3` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `c1` (`c1`)
) ENGINE=InnoDB AUTO_INCREMENT=14 DEFAULT CHARSET=utf8mb4;
数据:
INSERT INTO `t1` VALUES ('1', '1', '1', '1');
INSERT INTO `t1` VALUES ('2', '2', '2', '2');
INSERT INTO `t1` VALUES ('3', '3', '3', '3');
INSERT INTO `t1` VALUES ('4', '4', '4', '4');
INSERT INTO `t1` VALUES ('5', '5', '5', '5');
INSERT INTO `t1` VALUES ('6', '6', '6', '6');
INSERT INTO `t1` VALUES ('7', '7', '7', '7');
INSERT INTO `t1` VALUES ('8', '8', '8', '8');
INSERT INTO `t1` VALUES ('9', '9', '9', '9');
INSERT INTO `t1` VALUES ('10', '10', '10', '10');
INSERT INTO `t1` VALUES ('11', '11', '11', '11');
INSERT INTO `t1` VALUES ('12', '12', '12', '12');
INSERT INTO `t1` VALUES ('13', '13', '13', '13');
测试1:
se
CREATE TABLE `t1` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`c1` int(11) NOT NULL,
`c2` int(11) NOT NULL,
`c3` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `c1` (`c1`)
) ENGINE=InnoDB AUTO_INCREMENT=14 DEFAULT CHARSET=utf8mb4;
数据:
INSERT INTO `t1` VALUES ('1', '1', '1', '1');
INSERT INTO `t1` VALUES ('2', '2', '2', '2');
INSERT INTO `t1` VALUES ('3', '3', '3', '3');
INSERT INTO `t1` VALUES ('4', '4', '4', '4');
INSERT INTO `t1` VALUES ('5', '5', '5', '5');
INSERT INTO `t1` VALUES ('6', '6', '6', '6');
INSERT INTO `t1` VALUES ('7', '7', '7', '7');
INSERT INTO `t1` VALUES ('8', '8', '8', '8');
INSERT INTO `t1` VALUES ('9', '9', '9', '9');
INSERT INTO `t1` VALUES ('10', '10', '10', '10');
INSERT INTO `t1` VALUES ('11', '11', '11', '11');
INSERT INTO `t1` VALUES ('12', '12', '12', '12');
INSERT INTO `t1` VALUES ('13', '13', '13', '13');
测试1:
se

本文通过三个测试案例详细解析了MySQL中嵌套事务的行为,揭示了在不同autocommit模式下,如何影响事务的提交与回滚,强调了在嵌套事务中对事务边界的理解和使用注意事项。
最低0.47元/天 解锁文章
405

被折叠的 条评论
为什么被折叠?



