Although closing a database also closes any open cursors, it is recommended that applications explicitly close all their Cursor objects before closing the database. The reason why is that when the cursor is explicitly closed, the memory allocated for it is reclaimed; however, this does not happen if you close a database while cursors are still opened.

The same rule, for the same reasons, holds true for Transaction objects. Simply make sure you resolve all your transaction objects before closing your database handle.

Because key/data pairs are cached in-memory, applications should make a point to always either close database handles or sync their data to disk (using Sync()()() before exiting, to ensure that any data cached in main memory is reflected in the underlying file system.

When called on a secondary index's primary database, the primary should be closed only after all secondary indices referencing it have been closed.

When multiple threads use the object concurrently, only a single thread may call the Close method.

The object may not be accessed again after Close is called, regardless of its outcome.

Release the resources held by this object, and close the database if it is still open.

Determines whether the specified Object is equal to the current Object.

Serves as a hash function for a particular type.

Gets the Type of the current instance.

The statistical information is described by the BTreeStats, HashStats, HeapStats, QueueStats, and RecnoStats classes.

The statistical information is described by the BTreeStats, HashStats, HeapStats, QueueStats, and RecnoStats classes.

Applications should never remove databases with open DB handles, or in the case of removing a file, when any database in the file has an open handle. For example, some architectures do not permit the removal of files with open system handles. On these architectures, attempts to remove databases currently in use by any thread of control in the system may fail.

Remove should not be called if the remove is intended to be transactionally safe; RemoveDB(String, Boolean) should be used instead.

Applications should not rename databases that are currently in use. If an underlying file is being renamed and logging is currently enabled in the database environment, no database in the file should be open when Rename is called. In particular, some architectures do not permit renaming files with open handles. On these architectures, attempts to rename databases that are currently in use by any thread of control in the system may fail.

Rename should not be called if the rename is intended to be transactionally safe; RenameDB(String, String, Boolean) should be used instead.

Flush any cached information to disk.

Returns a String that represents the current Object.

When called on a database configured with secondary indices, This method truncates the primary database and all secondary indices. A count of the records discarded from the primary database is returned.

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

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

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 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 mechanism for reporting detailed statistic messages to the application.

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

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 database's current page size.

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 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.