-
Notifications
You must be signed in to change notification settings - Fork 721
Reorder the description of transaction modes by strictness #24784
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
base: main
Are you sure you want to change the base?
Reorder the description of transaction modes by strictness #24784
Conversation
🟢 |
5abe8c2
to
d91c27f
Compare
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully Build logsWarnings (2) |
🔄 New commits pushed — @a-s-maslov please take a look. |
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully Build logsWarnings (2) |
Changelog entry
Reorder the description of transaction modes by strictness
Changelog category
Description for reviewers
There is a page in the YDB documentation, which describes the transaction modes.
https://ydb.tech/docs/ru/concepts/transactions#modes
This section starts with mentioning the Serializable mode (the strictest mode) and then describes other modes, but the other modes are described in essentially random order, which makes it hard to read and to understand their logic. This change reorders the descriptions so that the modes are described in the order of reduced strictness (from the most strict to the least strict mode). This makes it easier to understand which guarantee is "removed" from the previous mode and which performance characteristics are "gained" from the previous mode.
For comparison, the SQL isolation levels on the official Wikipedia page are also listed in the order of reduced strictness.
https://en.wikipedia.org/wiki/Isolation_(database_systems)#Isolation_levels
NOTE: There are no changes to the actual description of the modes. Only the order is changed.