Tagged articles
12 articles
Page 1 of 1
Pan Zhi's Tech Notes
Pan Zhi's Tech Notes
Feb 20, 2025 · Databases

Mastering Database Concurrency: Dirty Read, Non‑Repeatable Read, and Phantom Read

The article explains ACID properties, details how inadequate isolation levels cause dirty reads, non‑repeatable reads, and phantom reads, illustrates each with transaction scenarios and diagrams, and shows how MySQL’s lock types and isolation settings prevent these anomalies, noting the trade‑off between isolation and concurrency.

databasedirty readlocking
0 likes · 9 min read
Mastering Database Concurrency: Dirty Read, Non‑Repeatable Read, and Phantom Read
IT Services Circle
IT Services Circle
Aug 20, 2023 · Databases

Understanding MySQL Transaction Isolation Levels and Their Practical Implications

This article explains MySQL's four transaction isolation levels—READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ, and SERIALIZABLE—detailing their definitions, associated phenomena such as dirty reads, non‑repeatable reads, and phantom reads, and demonstrates how to query and set isolation levels with practical SQL examples.

Database ConcurrencySQLdirty read
0 likes · 12 min read
Understanding MySQL Transaction Isolation Levels and Their Practical Implications
Top Architect
Top Architect
Oct 13, 2022 · Databases

Understanding Transaction Isolation Levels and Concurrency Issues in MySQL

The article explains why transaction isolation is needed, describes common concurrency problems such as lost updates, dirty reads, non‑repeatable reads and phantom reads, outlines the ACID properties of a transaction, and details MySQL's four isolation levels with their effects and default settings.

ACIDLost Updateconcurrency
0 likes · 8 min read
Understanding Transaction Isolation Levels and Concurrency Issues in MySQL
Practical DevOps Architecture
Practical DevOps Architecture
Sep 21, 2022 · Databases

Understanding MySQL Transaction Isolation Levels: Dirty Read, Non-Repeatable Read, and Phantom Read

This article explains MySQL's four transaction isolation levels, illustrating how concurrent transactions can cause dirty reads, non‑repeatable reads, and phantom reads through detailed examples of two transactions interacting via SELECT, UPDATE, and INSERT operations, and summarizes the consistency issues each scenario creates.

databasesdirty readmysql
0 likes · 4 min read
Understanding MySQL Transaction Isolation Levels: Dirty Read, Non-Repeatable Read, and Phantom Read
JavaEdge
JavaEdge
Jul 31, 2022 · Databases

Understanding Dirty Reads and Writes: How Transaction Isolation Keeps Your Data Safe

When two transactions access the same data without proper coordination, concurrency bugs such as dirty reads and dirty writes can arise; the article explains these problems, the guarantees of isolation levels, and how row locks and snapshot techniques prevent them in modern databases.

Database Concurrencydirty readdirty write
0 likes · 7 min read
Understanding Dirty Reads and Writes: How Transaction Isolation Keeps Your Data Safe
Architects Research Society
Architects Research Society
Jan 8, 2022 · Databases

Understanding Database Isolation Levels and Dirty Reads

This article explains database isolation levels, including read committed, repeatable read, serializable, and snapshot isolation, discusses dirty reads, phantom reads, and how various systems such as SQL Server, PostgreSQL, MySQL, Oracle, MongoDB, and others implement or differ in these isolation semantics.

Isolation LevelSQLdatabase
0 likes · 19 min read
Understanding Database Isolation Levels and Dirty Reads
Architects Research Society
Architects Research Society
Jun 2, 2020 · Databases

Understanding Database Isolation Levels and Dirty Reads

This article explains the concepts of isolation levels, dirty reads, and phantom reads across various relational and NoSQL databases, describing how each system implements or lacks transaction isolation and the practical impact on data consistency and performance.

Isolation LevelNoSQLSQL
0 likes · 17 min read
Understanding Database Isolation Levels and Dirty Reads
Java High-Performance Architecture
Java High-Performance Architecture
Jan 3, 2019 · Databases

Understanding Transaction Isolation Levels: Dirty, Non‑Repeatable, and Phantom Reads Explained

This article explains the three classic concurrency anomalies—dirty read, non‑repeatable read, and phantom read—describes the four standard isolation levels (read uncommitted, read committed, repeatable read, serializable), and shows how databases implement isolation using rollback logs and read‑views.

Database ConcurrencyRepeatable ReadSQL
0 likes · 6 min read
Understanding Transaction Isolation Levels: Dirty, Non‑Repeatable, and Phantom Reads Explained