MySQL 事务隔离级别被破坏了吗？

发布于 2024-08-02 09:10:02 字数 618 浏览 2 评论 0原文

我似乎无法在 32 位 x86 Debian 上使用 MySQL 5.0.32 来支持事务隔离级别。

我已将问题简化为最简单的形式，并使用 mysql 命令行客户端进行了测试：

-- On node writer:
--

DROP TABLE test;
CREATE TABLE test (
    name VARCHAR(255)
);

set autocommit=0;
set transaction isolation level read committed;
begin;

-- On node reader:
--

set autocommit=0;
set transaction isolation level read committed;
begin;

-- On node writer:
--

INSERT INTO test VALUES ('bob');

-- On node reader:
--

SELECT * from test;
-- Returns the row with bob in it!!!

可能相关，我注意到即使在回滚后该行仍然存在！

所以我的问题是自动提交并没有真正被禁用，并且事务隔离级别因此被有效地忽略了？

再见，谢尔顿。

原文

I can't seem to get MySQL 5.0.32 on 32bit x86 Debian to honour transaction isolation levels.

I've reduced my problem to its simplest form, tested with the mysql command-line client:

-- On node writer:
--

DROP TABLE test;
CREATE TABLE test (
    name VARCHAR(255)
);

set autocommit=0;
set transaction isolation level read committed;
begin;

-- On node reader:
--

set autocommit=0;
set transaction isolation level read committed;
begin;

-- On node writer:
--

INSERT INTO test VALUES ('bob');

-- On node reader:
--

SELECT * from test;
-- Returns the row with bob in it!!!

Probably related, I've noticed that the row remains even after a rollback!

So my quess is that autocommit isn't really disabled, and that transaction isolation levels are thus effectively ignored?

Ciao,
Sheldon.

分享到QQ

分享到微博