From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/transapp_why.html | 56 +++++++++++++++++------------ 1 file changed, 33 insertions(+), 23 deletions(-) (limited to 'docs/programmer_reference/transapp_why.html') diff --git a/docs/programmer_reference/transapp_why.html b/docs/programmer_reference/transapp_why.html index b8573e72..f3f381b2 100644 --- a/docs/programmer_reference/transapp_why.html +++ b/docs/programmer_reference/transapp_why.html @@ -14,7 +14,7 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +
Prev Chapter 11.  - Berkeley DB Transactional Data Store Applications - Chapter 11.  Berkeley DB Transactional Data Store Applications  Next
@@ -38,33 +36,47 @@
-

Perhaps the first question to answer is "Why transactions?" There are -a number of reasons to include transactional support in your applications. -The most common ones are the following:

+

+ Perhaps the first question to answer is "Why transactions?" + There are a number of reasons to include transactional support + in your applications. The most common ones are the + following: +

Recoverability
-
Applications often need to ensure that no matter how the system or -application fails, previously saved data is available the next time the -application runs. This is often called Durability.
+
+ Applications often need to ensure that no matter + how the system or application fails, previously saved + data is available the next time the application runs. + This is often called Durability. +
Atomicity
-
Applications may need to make multiple changes to one or more databases, -but ensure that either all of the changes happen, or none of them -happens. Transactions guarantee that a group of changes are atomic; -that is, if the application or system fails, either all of the changes -to the databases will appear when the application next runs, or none of -them.
+
+ Applications may need to make multiple changes + to one or more databases, but ensure that either all + of the changes happen, or none of them happens. + Transactions guarantee that a group of changes are + atomic; that is, if the application or system fails, + either all of the changes to the databases will appear + when the application next runs, or none of + them. +
Isolation
-
Applications may need to make changes in isolation, that is, ensure that -only a single thread of control is modifying a key/data pair at a time. -Transactions ensure each thread of control sees all records as if all -other transactions either completed before or after its transaction.
+
+ Applications may need to make changes in + isolation, that is, ensure that only a single thread + of control is modifying a key/data pair at a time. + Transactions ensure each thread of control sees all + records as if all other transactions either completed + before or after its transaction. +
@@ -79,9 +91,7 @@ other transactions either completed before or after its transaction.  Next - Chapter 11.  - Berkeley DB Transactional Data Store Applications -   + Chapter 11.  Berkeley DB Transactional Data Store Applications   Home -- cgit v1.2.1