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.

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

Update Isolation Levels.sql: Extremely minor typo fix #503

Merged
merged 1 commit into from
Nov 10, 2024
Merged

Update Isolation Levels.sql: Extremely minor typo fix #503

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Presentations/Isolation Levels/Isolation Levels.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1715,7 +1715,7 @@ then stick with Read Committed, and add Repeatable Read/Serializable hints where

If you're okay with queries using the most recently known good version of row data
without being blocked, then an optimistic isolation level is for you
* Some queries may read "out of date" data, but not "dirty dat"
* Some queries may read "out of date" data, but not "dirty" data

If you're okay with queries returning potato-faced nonsense, keep using NOLOCK

Expand Down Expand Up @@ -2202,4 +2202,4 @@ results even under pessimistic locking isolation levels without additional prote
Demos: https://go.erikdarling.com/Isolation
Datas: https://go.erikdarling.com/Stack2013

*/
*/