# Overview Read committed isolation is.. #flashcard The most basic level of weak transaction isolation that makes two guarantees: - When reading from the database, you will only see data that has been committed (i.e., no [[dirty reads]]) - When writing to the data, you will only overwrite data that has been committed (i.e., no [[dirty writes]]) <!--ID: 1751507776832--> # Key Considerations The dirty writes are usually prevented using row-level [[locking]]. # Pros The pros of read committed isolation are... #flashcard - Avoids some kinds of concurrency problems - Allows aborts - Prevents reading the incomplete results of transactions - Prevent concurrent writes from getting intermingles <!--ID: 1751507776834--> # Cons The cons of read committed isolation are... #flashcard - It does not prevent the race condition between two counter increments - Does not prevent [[nonrepeatable read or read skew]] <!--ID: 1751507776837--> # Use Cases # Related Topics