#include <db.h>

int DB_ENV->dbremove(DB_ENV *dbenv, DB_TXN *txnid, const char *file, const char *database, u_int32_t flags);


The DB_ENV->dbremove method removes the database specified by the file and database arguments. If no database is specified, the underlying file represented by file is removed, incidentally removing all databases that it contained.

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

If the operation is to be transaction-protected, the txnid parameter is a transaction handle returned from DB_ENV->txn_begin; otherwise, NULL.

The flags value must be set to 0 or the following value:

Enclose the DB_ENV->dbremove call within a transaction. If the call succeeds, changes made by the operation will be recoverable. If the call fails, the operation will have made no changes.

The DB_ENV->dbremove method returns a non-zero error value on failure and 0 on success.

Environment Variables

The environment variable DB_HOME may be used as the path of the database environment home.

DB_ENV->dbremove is affected by any database directory specified using the DB_ENV->set_data_dir method, or by setting the "set_data_dir" string in the environment's DB_CONFIG file.


The DB_ENV->dbremove method may fail and return a non-zero error for the following conditions:

The operation was selected to resolve a deadlock.

An invalid flag value or parameter was specified.

A database in the file is currently open.

Called before DB_ENV->open was called.

The DB_ENV->dbremove method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->dbremove method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.



See Also

Database Environments and Related Methods


Copyright Sleepycat Software