1 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml">
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6 <title>Chapter 11. Berkeley DB Transactional Data Store Applications</title>
7 <link rel="stylesheet" href="gettingStarted.css" type="text/css" />
8 <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
9 <link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" />
10 <link rel="up" href="index.html" title="Berkeley DB Programmer's Reference Guide" />
11 <link rel="prev" href="cam_app.html" title="Architecting Data Store and Concurrent Data Store applications" />
12 <link rel="next" href="transapp_why.html" title="Why transactions?" />
15 <div xmlns="" class="navheader">
17 <p>Library Version 11.2.5.3</p>
19 <table width="100%" summary="Navigation header">
21 <th colspan="3" align="center">Chapter 11.
22 Berkeley DB Transactional Data Store Applications
26 <td width="20%" align="left"><a accesskey="p" href="cam_app.html">Prev</a> </td>
27 <th width="60%" align="center"> </th>
28 <td width="20%" align="right"> <a accesskey="n" href="transapp_why.html">Next</a></td>
33 <div class="chapter" lang="en" xml:lang="en">
34 <div class="titlepage">
37 <h2 class="title"><a id="transapp"></a>Chapter 11.
38 Berkeley DB Transactional Data Store Applications
45 <b>Table of Contents</b>
50 <a href="transapp.html#transapp_intro">Transactional Data Store introduction</a>
55 <a href="transapp_why.html">Why transactions?</a>
60 <a href="transapp_term.html">Terminology</a>
65 <a href="transapp_fail.html">Handling failure in Transactional Data Store applications</a>
70 <a href="transapp_app.html">Architecting Transactional Data Store applications</a>
75 <a href="transapp_env_open.html">Opening the environment</a>
80 <a href="transapp_data_open.html">Opening the databases</a>
85 <a href="transapp_put.html">Recoverability and deadlock handling</a>
90 <a href="transapp_atomicity.html">Atomicity</a>
95 <a href="transapp_inc.html">Isolation</a>
100 <a href="transapp_read.html">Degrees of isolation</a>
107 <a href="transapp_read.html#snapshot_isolation">Snapshot Isolation</a>
114 <a href="transapp_cursor.html">Transactional cursors</a>
119 <a href="transapp_nested.html">Nested transactions</a>
124 <a href="transapp_admin.html">Environment infrastructure</a>
129 <a href="transapp_deadlock.html">Deadlock detection</a>
134 <a href="transapp_checkpoint.html">Checkpoints</a>
139 <a href="transapp_archival.html">Database and log file archival</a>
144 <a href="transapp_logfile.html">Log file removal</a>
149 <a href="transapp_recovery.html">Recovery procedures</a>
154 <a href="transapp_hotfail.html">Hot failover</a>
159 <a href="transapp_journal.html">Using Recovery on Journaling Filesystems</a>
164 <a href="transapp_filesys.html">Recovery and filesystem operations</a>
169 <a href="transapp_reclimit.html">Berkeley DB recoverability</a>
174 <a href="transapp_tune.html">Transaction tuning</a>
179 <a href="transapp_throughput.html">Transaction throughput</a>
184 <a href="transapp_faq.html">Transaction FAQ</a>
189 <div class="sect1" lang="en" xml:lang="en">
190 <div class="titlepage">
193 <h2 class="title" style="clear: both"><a id="transapp_intro"></a>Transactional Data Store introduction</h2>
197 <p>It is difficult to write a useful transactional tutorial and still keep
198 within reasonable bounds of documentation; that is, without writing a
199 book on transactional programming. We have two goals in this section:
200 to familiarize readers with the transactional interfaces of Berkeley DB and
201 to provide code building blocks that will be useful for creating
203 <p>We have not attempted to present this information using a real-world
204 application. First, transactional applications are often complex and
205 time-consuming to explain. Also, one of our goals is to give you an
206 understanding of the wide variety of tools Berkeley DB makes available to you,
207 and no single application would use most of the interfaces included in
208 the Berkeley DB library. For these reasons, we have chosen to simply present
209 the Berkeley DB data structures and programming solutions, using examples that
210 differ from page to page. All the examples are included in a standalone
211 program you can examine, modify, and run; and from which you will be able
212 to extract code blocks for your own applications. Fragments of the
213 program will be presented throughout this chapter, and the complete text
214 of the <a class="ulink" href="transapp.cs" target="_top">example program</a> for IEEE/ANSI Std 1003.1 (POSIX)
215 standard systems is included in the Berkeley DB distribution.</p>
218 <div class="navfooter">
220 <table width="100%" summary="Navigation footer">
222 <td width="40%" align="left"><a accesskey="p" href="cam_app.html">Prev</a> </td>
223 <td width="20%" align="center"> </td>
224 <td width="40%" align="right"> <a accesskey="n" href="transapp_why.html">Next</a></td>
227 <td width="40%" align="left" valign="top">Architecting Data Store and Concurrent Data Store applications </td>
228 <td width="20%" align="center">
229 <a accesskey="h" href="index.html">Home</a>
231 <td width="40%" align="right" valign="top"> Why transactions?</td>