summaryrefslogtreecommitdiff
path: root/docs/programmer_reference/transapp_why.html
diff options
context:
space:
mode:
authorLorry Tar Creator <lorry-tar-importer@baserock.org>2015-02-17 17:25:57 +0000
committer <>2015-03-17 16:26:24 +0000
commit780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch)
tree598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/transapp_why.html
parent7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff)
downloadberkeleydb-master.tar.gz
Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz.HEADdb-6.1.23master
Diffstat (limited to 'docs/programmer_reference/transapp_why.html')
-rw-r--r--docs/programmer_reference/transapp_why.html56
1 files changed, 33 insertions, 23 deletions
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 @@
<body>
<div xmlns="" class="navheader">
<div class="libver">
- <p>Library Version 11.2.5.3</p>
+ <p>Library Version 12.1.6.1</p>
</div>
<table width="100%" summary="Navigation header">
<tr>
@@ -22,9 +22,7 @@
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="transapp.html">Prev</a> </td>
- <th width="60%" align="center">Chapter 11. 
- Berkeley DB Transactional Data Store Applications
- </th>
+ <th width="60%" align="center">Chapter 11.  Berkeley DB Transactional Data Store Applications </th>
<td width="20%" align="right"> <a accesskey="n" href="transapp_term.html">Next</a></td>
</tr>
</table>
@@ -38,33 +36,47 @@
</div>
</div>
</div>
- <p>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:</p>
+ <p>
+ 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:
+ </p>
<div class="variablelist">
<dl>
<dt>
<span class="term">Recoverability</span>
</dt>
- <dd>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.</dd>
+ <dd>
+ 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.
+ </dd>
<dt>
<span class="term">Atomicity</span>
</dt>
- <dd>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.</dd>
+ <dd>
+ 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.
+ </dd>
<dt>
<span class="term">Isolation</span>
</dt>
- <dd>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.</dd>
+ <dd>
+ 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.
+ </dd>
</dl>
</div>
</div>
@@ -79,9 +91,7 @@ other transactions either completed before or after its transaction.</dd>
<td width="40%" align="right"> <a accesskey="n" href="transapp_term.html">Next</a></td>
</tr>
<tr>
- <td width="40%" align="left" valign="top">Chapter 11. 
- Berkeley DB Transactional Data Store Applications
-  </td>
+ <td width="40%" align="left" valign="top">Chapter 11.  Berkeley DB Transactional Data Store Applications  </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>