The DB->remove interface removes the database specified by the
file and database arguments. If no database is
specified, the physical file represented by file is removed,
incidentally removing all databases that it contained.
If a physical file is being removed and logging is currently enabled in
the database environment, no database in the file may be open when the
DB->remove function is called. Otherwise, no reference count of database
use is maintained by Berkeley DB. Applications should not remove databases that
are currently in use. In particular, some architectures do not permit
the removal of files with open handles. On these architectures, attempts
to remove databases that are currently in use will fail.
The flags parameter is currently unused, and must be set to 0.
Once DB->remove has been called, regardless of its return, the
DB handle may not be accessed again.
The DB->remove function returns a non-zero error value on failure and 0 on success.
If the dbenv argument to db_create was initialized using
DBENV->open the environment variable DB_HOME may be used
as the path of the database environment home. Specifically, DB->remove
is affected by the configuration value DB_DATA_DIR.
The DB->remove function may fail and return a non-zero error for the following conditions:
A database in the file is currently open.
The DB->remove function 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->remove function may fail and return
DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail
in the same way.