head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.52.48; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.08; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.55; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.07.56; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.56; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @
DB->del |
![]() ![]() |
#include <db.h>int DB->del(DB *db, DB_TXN *txnid, DBT *key, u_int32_t flags);
The DB->del function removes key/data pairs from the database. The key/data pair associated with the specified key is discarded from the database. In the presence of duplicate key values, all records associated with the designated key will be discarded.
When called on a database that has been made into a secondary index using the DB->associate function, the DB->del function deletes the key/data pair from the primary database and all secondary indices.
If the operation is to be transaction-protected, the txnid parameter is a transaction handle returned from txn_begin; otherwise, NULL.
The flags parameter is currently unused, and must be set to 0.
The DB->del function returns a non-zero error value on failure, 0 on success, and DB_NOTFOUND if the specified key did not exist in the file.
The DB->del function may fail and return a non-zero error for the following conditions:
The DB->del 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->del 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 d36 1 a36 1 parameter is a transaction handle returned from DB_ENV->txn_begin; @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d28 1 a28 1
The DB->del method removes key/data pairs from the database. The d33 1 a33 1 using the DB->associate method, the DB->del method deletes the d35 6 a40 13
If the operation is to be transaction-protected (other than by specifying the DB_AUTO_COMMIT flag), 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:
If the specified key is not in the database, the DB->del method will return DB_NOTFOUND. Otherwise, the DB->del method returns a non-zero error value on failure and 0 on success. d42 1 a42 1
The DB->del method may fail and return a non-zero error for the following conditions: d55 4 a58 6
The DB->del 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->del method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
The DB->del function removes key/data pairs from the database. The d34 1 a34 1 using the DB->associate function, the DB->del function deletes the d36 13 a48 6
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 parameter is currently unused, and must be set to 0.
The DB->del function returns a non-zero error value on failure, 0 on success, and DB_NOTFOUND if the specified key did not exist in the file. d50 1 a50 1
The DB->del function may fail and return a non-zero error for the following conditions: d63 6 a68 4
The DB->del 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->del function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d70 1 a70 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 2 a3 1 d28 1 a28 1
The DB->del method removes key/data pairs from the database. The d33 1 a33 1 using the DB->associate method, the DB->del method deletes the d35 6 a40 13
If the operation is to be transaction-protected (other than by specifying the DB_AUTO_COMMIT flag), 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:
If the specified key is not in the database, the DB->del method will return DB_NOTFOUND. Otherwise, the DB->del method returns a non-zero error value on failure and 0 on success. d42 1 a42 1
The DB->del method may fail and return a non-zero error for the following conditions: d55 4 a58 6
The DB->del 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->del method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.