Statement-level Read Consistency vs Transaction-level Read Consistency

이기현·2021년 1월 11일
0

Oracle

목록 보기
7/39

Statement-level Read Consistency는 각각의 query에 대해서 일관성을 보장해 주는 것이고,

Oracle always enforces statement-level read consistency. This guarantees that all the data returned by a single query comes from a single point in time—the time that the query began. Therefore, a query never sees dirty data or any of the changes made by transactions that commit during query execution. As query execution proceeds, only data committed before the query began is visible to the query. The query does not see changes committed after statement execution begins.

Transaction-level Read Consistency는 전체 Transaction에 대한 일관성을 보장해주는 것이다.

Oracle also offers the option of enforcing transaction-level read consistency. When a transaction runs in serializable mode, all data accesses reflect the state of the database as of the time the transaction began. This means that the data seen by all queries within the same transaction is consistent with respect to a single point in time, except that queries made by a serializable transaction do see changes made by the transaction itself. Transaction-level read consistency produces repeatable reads and does not expose a query to phantoms.

profile
실력을 쌓아가는 하루하루

0개의 댓글