Enclose the open call within a transaction. If the call succeeds, the open operation is recoverable and all subsequent database modification operations based on this handle will be transactionally protected. If the call fails, no database has been created.

The byte order for integers in the stored database metadata. The host byte order of the machine where the Berkeley DB library was compiled is the default value.

The size of the shared memory buffer pool (the cache).

The Secondary Hash key comparison function.

The policy for how to handle database creation.

If true, do checksum verification of pages read into the cache from the backing filestore.

The duplicate data item comparison function.

Policy for duplicate data items in the database. Allows a key/data pair to be inserted into the database even if the key already exists.

The Berkeley DB environment within which to create a database. If null, the database is created stand-alone; it is not part of any Berkeley DB environment.

The mechanism for reporting error messages to the application.

The prefix string that appears before error messages issued by Berkeley DB.

Causes the database object to be free-threaded; that is, concurrently usable by multiple threads in the address space.

A user-defined hash function; if no hash function is specified, a default hash function is used.

If true, the secondary key is immutable.

The prefix string that appears before informational messages issued by Berkeley DB.

Do not map this database into process memory.

If true, Berkeley DB does not write log records for this database.

Configuration of BaseDatabase handle to obtain a write lock on the entire database.

If true and the secondary database is empty, walk through Primary and create an index to it in the empty secondary. This operation is potentially very expensive.

The cache priority for pages referenced by the database.

Open the database for reading only. Any attempt to modify items in the database will fail, regardless of the actual permissions of any underlying files.

Support transactional read operations with degree 1 isolation.

Physically truncate the underlying file, discarding all previous databases it might have held.

Open the database with support for multiversion concurrency control.