New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tac 模式增加事务隔离级别的控制 #366

Merged

cherrylzhao merged 1 commit into dromara:master from zkyoma:365

Sep 8, 2023

Contributor

zkyoma commented Sep 1, 2023

在 HmilyTac 注解增加 isolationLevel 属性, 用来确定 tac 模式下的隔离级别, 默认为 read uncommitted；
开启全局事务，创建 HmilyTransactionContext 对象时，保存对应的隔离级别；
执行 select SQL 时，根据 HmilyTransactionContext 对象的 isolationLevel 判断是否需要 checkLocks；
修改 tac demo 中对应的读已提交测试案例。


          1.在HmilyTac注解增加isolationLevel属性, 用来确定tac模式下的隔离级别, 默认为read_uncommitted…

23ae3a4

…。执行select SQL时, 根据隔离级别判断是否需要checkLocks。

2.修改tac demo中对应的测试案例。

cherrylzhao merged commit 795d269 into dromara:master

1 check passed

zkyoma deleted the 365 branch

September 11, 2023 07:27

cherrylzhao pushed a commit that referenced this pull request


          1.在HmilyTac注解增加isolationLevel属性, 用来确定tac模式下的隔离级别, 默认为read_uncommitted…

12f534a

…。执行select SQL时, 根据隔离级别判断是否需要checkLocks。 (#366)

2.修改tac demo中对应的测试案例。

cherrylzhao pushed a commit that referenced this pull request


          1.在HmilyTac注解增加isolationLevel属性, 用来确定tac模式下的隔离级别, 默认为read_uncommitted…

c002fab

…。执行select SQL时, 根据隔离级别判断是否需要checkLocks。 (#366)

2.修改tac demo中对应的测试案例。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet