DB->remove
DB->remove |
|
#include <db.h>int DB->remove(DB *db, const char *file, const char *database, u_int32_t flags);
The DB->remove interface 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 not remove databases that are currently in use. If an underlying 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. 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 by any thread of control in the system will fail.
The flags parameter is currently unused, and must be set to 0.
After 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.
The DB->remove function may fail and return a non-zero error for the following conditions:
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.
|
|
Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 d26 1 a26 1 const char *file, const char *database, u_int32_t flags); d42 1 a42 1 DB handle may not be accessed again. @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 3 a3 1 d29 1 a29 1
The DB->remove method removes the database specified by the d33 7 a39 6
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. d41 3 a43 3
The DB handle may not be accessed again after DB->remove is called, regardless of its return.
The DB->remove method returns a non-zero error value on failure and 0 on success. d46 4 a49 6
DB->remove 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. d52 1 a52 1
The DB->remove method may fail and return a non-zero error for the following conditions: d54 1 a54 3
A database in the file is currently open.
Called after DB->open was called. d56 4 a59 6
The DB->remove 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->remove method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
The DB->remove interface removes the database specified by the d35 6 a40 7
Applications should not remove databases that are currently in use. If an underlying 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. 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 by any thread of control in the system will fail. d42 3 a44 3
After 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. d47 6 a52 4
The DB->remove function may fail and return a non-zero error for the following conditions: d57 3 a59 1
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. d68 1 a68 46 db_create, DB->associate, DB->close, DB->cursor, DB->del, DB->err, DB->errx DB->fd, DB->get, DB->pget, DB->get_byteswapped, DB->get_type, DB->join, DB->key_range, DB->open, DB->put, DB->remove, DB->rename, DB->set_alloc, DB->set_append_recno, DB->set_bt_compare, DB->set_bt_minkey, DB->set_bt_prefix, DB->set_cachesize, DB->set_dup_compare, DB->set_errcall, DB->set_errfile, DB->set_errpfx, DB->set_feedback, DB->set_flags, DB->set_h_ffactor, DB->set_h_hash, DB->set_h_nelem, DB->set_lorder, DB->set_pagesize, DB->set_paniccall, DB->set_q_extentsize, DB->set_re_delim, DB->set_re_len, DB->set_re_pad, DB->set_re_source, DB->stat, DB->sync, DB->truncate, DB->upgrade, and DB->verify. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 3 a3 1 d29 1 a29 1
The DB->remove method removes the database specified by the d33 7 a39 6
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. d41 3 a43 3
The DB handle may not be accessed again after DB->remove is called, regardless of its return.
The DB->remove method returns a non-zero error value on failure and 0 on success. d46 4 a49 6
DB->remove 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. d52 1 a52 1
The DB->remove method may fail and return a non-zero error for the following conditions: d54 1 a54 3
A database in the file is currently open.
Called after DB->open was called. d56 4 a59 6
The DB->remove 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->remove method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.