Berkeley DB Reference Guide: Release 3.0: the DBINFO structure

Berkeley DB Reference Guide:
Upgrading Berkeley DB Applications

Release 3.0: the DBINFO structure

The DB_INFO structure has been removed from the Berkeley DB 3.0 release. Accesses to any fields within that structure by the application should be replaced with method calls on the DB handle. The following example illustrates this using the historic db_cachesize structure field. In the Berkeley DB 2.X releases, applications could set the size of an underlying database cache using code similar to the following:

DB_INFO dbinfo;

	memset(dbinfo, 0, sizeof(dbinfo));
	dbinfo.db_cachesize = 1024 * 1024;

in the Berkeley DB 3.X releases, this should be done using the DB->set_cachesize method, as follows:

DB *db;
int ret;

	ret = db->set_cachesize(db, 0, 1024 * 1024, 0);

The DB_INFO structure is no longer used in any way by the Berkeley DB 3.0 release, and should be removed from the application.

The following table lists the DB_INFO fields previously used by applications and the methods that should now be used to set them. Because these calls provide configuration for the database open, they must precede the call to DB->open. Calling them after the call to DB->open will return an error.

DB_INFO field	Berkeley DB 3.X method
bt_compare	DB->set_bt_compare
bt_minkey	DB->set_bt_minkey
bt_prefix	DB->set_bt_prefix
db_cachesize	DB->set_cachesize Note: the DB->set_cachesize function takes additional arguments. Setting both the second argument (the number of GB in the pool) and the last argument (the number of memory pools to create) to 0 will result in behavior that is backward-compatible with previous Berkeley DB releases.
db_lorder	DB->set_lorder
db_malloc	DB->set_malloc
db_pagesize	DB->set_pagesize
dup_compare	DB->set_dup_compare
flags	DB->set_flags Note: the DB_DELIMITER, DB_FIXEDLEN and DB_PAD flags no longer need to be set as there are specific methods off the DB handle that set the file delimiter, the length of fixed-length records and the fixed-length record pad character. They should simply be discarded from the application.
h_ffactor	DB->set_h_ffactor
h_hash	DB->set_h_hash
h_nelem	DB->set_h_nelem
re_delim	DB->set_re_delim
re_len	DB->set_re_len
re_pad	DB->set_re_pad
re_source	DB->set_re_source