We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Real MySQL p183을 보면 "InnoDB 스토리지 엔진에서는 갭 락과 넥스트 키 락 덕분에 REPEATABLE READ 격리 수준에서도 이미 "PHANTOM READ"가 발생하지 않기 때문에" 라고 되어 있는데 명확하게 왜 발생하지 않는지 궁금하네요
The text was updated successfully, but these errors were encountered:
https://suhwan.dev/2019/06/09/transaction-isolation-level-and-lock/
https://dev.mysql.com/doc/refman/8.0/en/innodb-next-key-locking.html
Sorry, something went wrong.
굿
No branches or pull requests
Real MySQL p183을 보면
"InnoDB 스토리지 엔진에서는 갭 락과 넥스트 키 락 덕분에 REPEATABLE READ 격리 수준에서도 이미 "PHANTOM READ"가 발생하지 않기 때문에"
라고 되어 있는데 명확하게 왜 발생하지 않는지 궁금하네요
The text was updated successfully, but these errors were encountered: