Gecko [ 122.154.134.11 ]

Name	Size	Permission
admin.html	3.28 KB	-rw-r--r--
app.html	16.29 KB	-rw-r--r--
archival.html	9.52 KB	-rw-r--r--
atomicity.html	4.19 KB	-rw-r--r--
checkpoint.html	4.7 KB	-rw-r--r--
cursor.html	4.99 KB	-rw-r--r--
data_open.html	5.89 KB	-rw-r--r--
deadlock.html	5.78 KB	-rw-r--r--
env_open.html	6.53 KB	-rw-r--r--
fail.html	4.98 KB	-rw-r--r--
faq.html	7.8 KB	-rw-r--r--
filesys.html	4.22 KB	-rw-r--r--
hotfail.html	5.51 KB	-rw-r--r--
inc.html	6.1 KB	-rw-r--r--
intro.html	2.72 KB	-rw-r--r--
logfile.html	3.57 KB	-rw-r--r--
nested.html	4.19 KB	-rw-r--r--
put.html	10.51 KB	-rw-r--r--
read.html	7.93 KB	-rw-r--r--
reclimit.html	9.7 KB	-rw-r--r--
recovery.html	6.42 KB	-rw-r--r--
term.html	4.09 KB	-rw-r--r--
throughput.html	7.14 KB	-rw-r--r--
transapp.cs	10.34 KB	-rw-r--r--
tune.html	10.76 KB	-rw-r--r--
why.html	2.49 KB	-rw-r--r--
writetest.cs	2.32 KB	-rw-r--r--

Code Editor : intro.html

<html>
<head>
<title>Berkeley DB Reference Guide: Transactional Data Store introduction</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<a name="2"></a>
<table width="100%"><tr valign=top>
<td><b><dl><dt>Berkeley DB Reference Guide:<dd>Berkeley DB Transactional Data Store Applications</dl></b></td>
<td align=right><a href="../cam/app.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../transapp/why.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p align=center><b>Transactional Data Store introduction</b></p>
<p>It is difficult to write a useful transactional tutorial and still keep
within reasonable bounds of documentation; that is, without writing a
book on transactional programming.  We have two goals in this section:
to familiarize readers with the transactional interfaces of Berkeley DB and
to provide code building blocks that will be useful for creating
applications.</p>
<p>We have not attempted to present this information using a real-world
application.  First, transactional applications are often complex and
time-consuming to explain.  Also, one of our goals is to give you an
understanding of the wide variety of tools Berkeley DB makes available to you,
and no single application would use most of the interfaces included in
the Berkeley DB library.  For these reasons, we have chosen to simply present
the Berkeley DB data structures and programming solutions, using examples that
differ from page to page.  All the examples are included in a standalone
program you can examine, modify, and run; and from which you will be able
to extract code blocks for your own applications.  Fragments of the
program will be presented throughout this chapter, and the complete text
of the <a href="transapp.cs">example program</a> for IEEE/ANSI Std 1003.1 (POSIX)
standard systems is included in the Berkeley DB distribution.</p>
<table width="100%"><tr><td><br></td><td align=right><a href="../cam/app.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../transapp/why.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p><font size=1>Copyright (c) 1996,2008 Oracle.  All rights reserved.</font>
</body>
</html>

${this.title}

Code Editor : intro.html