#include <db_cxx.h>

int Db::remove(const char *file, const char *database, u_int32_t flags);


The Db::remove 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.

The flags parameter is currently unused, and must be set to 0.

The Db handle may not be accessed again after Db::remove is called, regardless of its return.

The Db::remove method either returns a non-zero error value or throws an exception that encapsulates a non-zero error value on failure, and returns 0 on success.

Environment Variables

If a dbenv argument to db_create was specified, the environment variable DB_HOME may be used as the path of the database environment home.

Db::remove is affected by any database directory specified using the DbEnv::set_data_dir method, or by setting the "set_data_dir" string in the environment's DB_CONFIG file.


The Db::remove method may fail and throw an exception or return a non-zero error for the following conditions:

An invalid flag value or parameter was specified.

A database in the file is currently open.

Called after Db::open was called.

If the file or directory does not exist, the Db::remove method will fail and and either return ENOENT or throw a FileNotFoundException exception.

The Db::remove method may fail and throw an exception or return a non-zero error for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the Db::remove method may fail and either return DB_RUNRECOVERY or throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.



See Also

Databases and Related Methods


Copyright Sleepycat Software