From 2a0f262beff32ba86bcb58f3273214e5d0517c09 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 14 May 2024 21:16:24 +0200 Subject: Merging upstream version 16.3. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/applevel-consistency.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/applevel-consistency.html') diff --git a/doc/src/sgml/html/applevel-consistency.html b/doc/src/sgml/html/applevel-consistency.html index 6c71c80..9ffcf2f 100644 --- a/doc/src/sgml/html/applevel-consistency.html +++ b/doc/src/sgml/html/applevel-consistency.html @@ -1,5 +1,5 @@ -13.4. Data Consistency Checks at the Application Level
13.4. Data Consistency Checks at the Application Level
Prev UpChapter 13. Concurrency ControlHome Next

13.4. Data Consistency Checks at the Application Level #

13.4.1. Enforcing Consistency with Serializable Transactions
13.4.2. Enforcing Consistency with Explicit Blocking Locks

+13.4. Data Consistency Checks at the Application Level

13.4. Data Consistency Checks at the Application Level
Prev UpChapter 13. Concurrency ControlHome Next

13.4. Data Consistency Checks at the Application Level #

13.4.1. Enforcing Consistency with Serializable Transactions
13.4.2. Enforcing Consistency with Explicit Blocking Locks

It is very difficult to enforce business rules regarding data integrity using Read Committed transactions because the view of the data is shifting with each statement, and even a single statement may not @@ -112,4 +112,4 @@ UPDATE, DELETE, or MERGE), so it is possible to obtain locks explicitly before the snapshot is frozen. -

Prev Up Next
13.3. Explicit Locking Home 13.5. Serialization Failure Handling
\ No newline at end of file +

Prev Up Next
13.3. Explicit Locking Home 13.5. Serialization Failure Handling
\ No newline at end of file -- cgit v1.2.3