DB->set_dup_compare
DB->set_dup_compare |
|
#include <db.h>int DB->set_dup_compare(DB *db, int (*dup_compare_fcn)(DB *, const DBT *, const DBT *));
Set the duplicate data item comparison function. The comparison function is called when it is necessary to compare a data item specified by the application with a data item currently stored in the tree. The first argument to the comparison function is the DBT representing the application's data item; the second is the current tree's data item.
The comparison function must return an integer value less than, equal to, or greater than zero if the first data item argument is considered to be respectively less than, equal to, or greater than the second data item argument. In addition, the comparison function must cause the data items in the set to be well-ordered. The comparison function must correctly handle any data item values used by the application (possibly including zero-length data items). The data and size fields of the DBT are the only fields that may be used for the purposes of this comparison, and no particular alignment of the memory to which the data field refers may be assumed.
If no comparison function is specified, the data items are compared lexically, with shorter data items collating before longer data items. The same duplicate data item comparison method must be used each time a particular Btree is opened.
The DB->set_dup_compare interface may be used only to configure Berkeley DB before the DB->open interface is called.
The DB->set_dup_compare function returns a non-zero error value on failure and 0 on success.
The DB->set_dup_compare function may fail and return a non-zero error for the following conditions:
The DB->set_dup_compare 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->set_dup_compare 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 @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d32 1 a32 1 argument to the comparison function is the DBT representing the a33 2 Calling DB->set_dup_compare implies calling DB->set_flags with the DB_DUPSORT flag. d41 1 a41 1 size fields of the DBT are the only fields that may be d46 5 a50 7
The DB->set_dup_compare interface may not be called after the DB->open interface is called. If the database already exists when DB->open is called, the information specified to DB->set_dup_compare must be the same as that historically used to create the database or corruption can occur.
The DB->set_dup_compare method returns a non-zero error value on failure and 0 on success. d52 1 a52 1
The DB->set_dup_compare method may fail and return a non-zero error for the following conditions: d56 4 a59 6
The DB->set_dup_compare 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->set_dup_compare method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
The DB->set_dup_compare interface may be used only to configure Berkeley DB before the DB->open interface is called.
The DB->set_dup_compare function returns a non-zero error value on failure and 0 on success. d57 1 a57 1
The DB->set_dup_compare function may fail and return a non-zero error for the following conditions: d61 6 a66 4
The DB->set_dup_compare 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->set_dup_compare 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 2 a3 1 d32 1 a32 1 argument to the comparison function is the DBT representing the a33 2 Calling DB->set_dup_compare implies calling DB->set_flags with the DB_DUPSORT flag. d41 1 a41 1 size fields of the DBT are the only fields that may be d46 5 a50 7
The DB->set_dup_compare interface may not be called after the DB->open interface is called. If the database already exists when DB->open is called, the information specified to DB->set_dup_compare must be the same as that historically used to create the database or corruption can occur.
The DB->set_dup_compare method returns a non-zero error value on failure and 0 on success. d52 1 a52 1
The DB->set_dup_compare method may fail and return a non-zero error for the following conditions: d56 4 a59 6
The DB->set_dup_compare 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->set_dup_compare method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.