Skip to content
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.

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

Implementation detail about SET TRANSACTION ISOLATION LEVEL #10092

Closed
marsishandsome opened this issue Apr 10, 2019 · 1 comment
Closed

Implementation detail about SET TRANSACTION ISOLATION LEVEL #10092

marsishandsome opened this issue Apr 10, 2019 · 1 comment
Labels
type/question The issue belongs to a question.

Comments

@marsishandsome
Copy link
Contributor

I'm confused when working on this PR: #10065.

I find that, SET TRANSACTION ISOLATION LEVEL will affect two internal variables:

  1. tx_isolation
  2. transaction_isolation

Can any body tell me, what's the difference between the two variables?

@marsishandsome marsishandsome added the type/question The issue belongs to a question. label Apr 10, 2019
@lysu
Copy link
Contributor

lysu commented Apr 10, 2019

@marsishandsome

just alias, and mysql's old stuff.

"transaction_isolation was added in MySQL 5.7.20 as an alias for tx_isolation, which is now deprecated and is removed in MySQL 8.0. Applications should be adjusted to use transaction_isolation in preference to tx_isolation."

and there are same history question tx_read_only

Prior to MySQL 5.7.20, use tx_isolation and tx_read_only rather than transaction_isolation and transaction_read_only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/question The issue belongs to a question.
Projects
None yet
Development

No branches or pull requests

2 participants