If true, all database modification operations based on this object are transactionally protected.

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

The Btree key comparison function. The comparison function is called whenever it is necessary to compare a key specified by the application with a key currently stored in the tree.

The CreatePolicy with which this database was opened.

The name of this database, if it has one.

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

The duplicate data item comparison function.

Whether the insertion of duplicate data items in the database is permitted, and whether duplicates items are sorted.

The algorithm used by the Berkeley DB library to perform encryption and decryption.

If true, encrypt all data stored in the database.

The database byte order.

The mechanism for reporting detailed error messages to the application.

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

Monitor progress within long running operations.

The filename of this database, if it has one.

If true, the object is free-threaded; concurrently usable by multiple threads in the address space.

If true, the object references a physical file supporting multiple databases.

If true, the underlying database files were created on an architecture of the same byte order as the current one. This information may be used to determine whether application data needs to be adjusted for this architecture or not.

The delegate that creates the set of secondary keys corresponding to a given primary key and data pair.

The mechanism for reporting detailed statistic messages to the application.

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

The minimum number of key/data pairs intended to be stored on any single Btree leaf page.

The message file.

If true, this database is not mapped into process memory.

See MMapSize for further information.

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

If true, configure the database handle to obtain a write lock on the entire database. When the database is opened it immediately throws LockNotGrantedException if it cannot obtain the exclusive lock immediately. If False, configure the database handle to obtain a write lock on the entire database. When the database is opened, it blocks until it can obtain the exclusive lock. If null, do not configure the database handle to obtain a write lock on the entire database.

The nullifying function used to set the foreign key to null.

The database's current page size.

The Btree prefix function. The prefix function is used to determine the amount by which keys stored on the Btree internal pages can be safely truncated without losing their uniqueness.

The cache priority for pages referenced by this object.

If true, this database has been opened for read only. Any attempt to modify items in the database will fail, regardless of the actual permissions of any underlying files.

If true, this database supports transactional read operations with degree 1 isolation. Read operations on the database may request the return of modified but not yet committed data.

If true, this object supports retrieval from the Btree using record numbers.

If false, empty pages are not coalesced into higher-level pages.

If true, this database has been opened in a transactional mode.

If true, the underlying file was physically truncated upon open, discarding all previous databases it might have held.

The type of the underlying access method (and file format). This value may be used to determine the type of the database after an Open(String, DatabaseConfig).

If true, the database was opened with support for multiversion concurrency control.