SERIALIZABLE-Concurrency and Multiversioning
This is generally considered the most restrictive level of transaction isolation, but it provides the highest degree of isolation. A SERIALIZABLE […]
Read More →This is generally considered the most restrictive level of transaction isolation, but it provides the highest degree of isolation. A SERIALIZABLE […]
Read More →
Autonomous transactions allow you to create a “transaction within a transaction” that will commit or roll back changes independently of its […]
Read More →
READ ONLY transactions are very similar to SERIALIZABLE transactions, the only difference being that they do not allow modifications, so they […]
Read More →
The goal of REPEATABLE READ is to provide an isolation level that gives consistent, correct answers and prevents lost updates. We’ll […]
Read More →
The Oracle database has supported autonomous transactions internally for quite a while. We see them all of the time in the […]
Read More →
A common use of REPEATABLE READ in databases that employ the shared read locks could be for lost update prevention. Note […]
Read More →
The READ COMMITTED isolation level states that a transaction may only read data that has been committed in the database. There […]
Read More →
The READ UNCOMMITTED isolation level allows dirty reads. Oracle does not make use of dirty reads, nor does it even allow […]
Read More →