Berkeley DB: DB_ENV->dbremove
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++

DB_ENV->dbremove |

`

    #include <db.h>

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

Description: DB_ENV->dbremove

The DB_ENV->dbremove method removes the database specified by the file and database parameters. If no database is specified, the underlying file represented by file is removed, incidentally removing all of the databases 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 may fail.

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

Parameters
database

- The database parameter is the database to be removed.

file

- The file parameter is the physical file which contains the database(s) to be removed.

When using a Unicode build on Windows (the default), the file argument will be interpreted as a UTF-8 string, which is equivalent to ASCII for Latin characters.

flags

- The flags parameter must be set to 0 or the following value:
  DB_AUTO_COMMIT
  - 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.

txnid

- If the operation is part of an application-specified transaction, the txnid parameter is a transaction handle returned from DB_ENV->txn_begin; if the operation is part of a Berkeley DB Concurrent Data Store group, the txnid parameter is a handle returned from DB_ENV->cdsgroup_begin; otherwise NULL. If no transaction handle is specified, but the DB_AUTO_COMMIT flag is specified, the operation will be implicitly transaction protected.

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.

Errors

The DB_ENV->dbremove method may fail and return one of the following non-zero errors:

DB_LOCK_DEADLOCK

- A transactional database environment operation was selected to resolve a deadlock.

DB_LOCK_NOTGRANTED

- A Berkeley DB Concurrent Data Store database environment configured for lock timeouts was unable to grant a lock in the allowed time.

EINVAL

- If DB_ENV->dbremove called before DB_ENV->open was called; or if an invalid flag value or parameter was specified.

ENOENT

- The file or directory does not exist.

Class DB_ENV
See Also Database Environments and Related Methods`

Copyright (c) 1996,2008 Oracle. All rights reserved.