Table of Contents
This document describes how to use transactions with your Berkeley DB applications. It is intended to describe how to transaction protect your application's data. The APIs used to perform this task are described here, as are the environment infrastructure and administrative tasks required by a transactional application. This book also describes multi-threaded and multi-process DB applications and the requirements they have for deadlock detection.
This book describes Berkeley DB 18 Release 18.1, which provides library version 18.1.32.
This book is aimed at the software engineer responsible for writing a transactional DB application.
This book assumes that you have already read and understood the concepts contained in the Getting Started with Berkeley DB guide.
The following typographical conventions are used within in this manual:
Class names are represented in monospaced font
, as are method
names
. For example:
"The Environment()
constructor returns an Environment
class object."
Variable or non-literal text is presented in italics. For example: "Go to your DB_INSTALL directory."
Program examples are displayed in a monospaced font
on a shaded background.
For example:
import com.sleepycat.db.DatabaseConfig; ... // Allow the database to be created. DatabaseConfig myDbConfig = new DatabaseConfig(); myDbConfig.setAllowCreate(true);
In some situations, programming examples are updated from one chapter to the next. When
this occurs, the new code is presented in monospaced bold
font. For example:
import com.sleepycat.db.Database;
import com.sleepycat.db.DatabaseConfig; ... // Allow the database to be created. DatabaseConfig myDbConfig = new DatabaseConfig(); myDbConfig.setAllowCreate(true);Database myDb = new Database("mydb.db", null, myDbConfig);
Finally, notes of special interest are represented using a note block such as this.