|
|
Table of Contents
This document describes how to use transactions with your Berkeley DB, Java Edition 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 JE applications and the requirements they have for deadlock detection.
This book is aimed at the software engineer responsible for writing a transactional JE application.
This book assumes that you have already read and understood the concepts contained in Getting Started with Berkeley DB.
The following typographical conventions are used within in this manual:
Class names are represented in monospaced font, as are method names. For example: "DbEnv::open() is a DbEnv class method."
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:
typedef struct vendor {
char name[MAXFIELD]; // Vendor name
char street[MAXFIELD]; // Street name and number
char city[MAXFIELD]; // City
char state[3]; // Two-digit US state code
char zipcode[6]; // US zipcode
char phone_number[13]; // Vendor phone number
} VENDOR;
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:
typedef struct vendor {
char name[MAXFIELD]; // Vendor name
char street[MAXFIELD]; // Street name and number
char city[MAXFIELD]; // City
char state[3]; // Two-digit US state code
char zipcode[6]; // US zipcode
char phone_number[13]; // Vendor phone number
char sales_rep[MAXFIELD]; // Name of sales representative
char sales_rep_phone[MAXFIELD]; // Sales rep's phone number
} VENDOR;
Finally, notes of special interest are represented using a note block such as this.
Beyond this manual, you may also find the following sources of information useful when building a transactional JE application: