From 3ee0d548785a9c0a668e1f0e75d442d91df3f60d Mon Sep 17 00:00:00 2001 From: Krasimir Angelov Date: Thu, 23 Sep 2021 15:07:13 +0200 Subject: [PATCH] Update transactions.md --- src/runtime/c/doc/transactions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/runtime/c/doc/transactions.md b/src/runtime/c/doc/transactions.md index 3e11a694c..09080f699 100644 --- a/src/runtime/c/doc/transactions.md +++ b/src/runtime/c/doc/transactions.md @@ -114,3 +114,5 @@ The solution is that we count on the database clients to correctly report when a ## Atomicity + +The transactions serve two goals. First they make it possible to isolate readers from seeing unfinished changes from writers. The second is to ensure atomicity. A database change should be either completely done or not done at all. The use of transient revisions ensures the isolation but the atomicity is only partly taken care of.