DB->set_lorder
DB->set_lorder |
|
#include <db.h>int DB->set_lorder(DB *db, int lorder);
Set the byte order for integers in the stored database metadata. The number should represent the order as an integer; for example, big endian order is the value 4,321, and little endian order is the value 1,234. If lorder is not explicitly set, the host order of the machine where the Berkeley DB library was compiled is used.
The value of lorder is ignored except when databases are being created. If a database already exists, the byte order it uses is determined when the database is opened.
The access methods provide no guarantees about the byte ordering of the application data stored in the database, and applications are responsible for maintaining any necessary ordering.
The DB->set_lorder interface may be used only to configure Berkeley DB before the DB->open interface is called.
The DB->set_lorder function returns a non-zero error value on failure and 0 on success.
The DB->set_lorder function may fail and return a non-zero error for the following conditions:
Called after DB->open was called.
The DB->set_lorder 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_lorder 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 d33 3 d39 3 a41 11
The DB->set_lorder method configures a database, not only operations performed using the specified DB handle.
The DB->set_lorder 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_lorder will be ignored. If creating additional databases in a file, the byte order specified must be consistent with the existing databases in the file or an error will be returned.
The DB->set_lorder method returns a non-zero error value on failure and 0 on success. d43 1 a43 1
The DB->set_lorder method may fail and return a non-zero error for the following conditions: d48 4 a51 6
The DB->set_lorder 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_lorder method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
The value of lorder is ignored except when databases are being created. If a database already exists, the byte order it uses is determined when the database is opened. d37 11 a47 3
The DB->set_lorder interface may be used only to configure Berkeley DB before the DB->open interface is called.
The DB->set_lorder function returns a non-zero error value on failure and 0 on success. d49 1 a49 1
The DB->set_lorder function may fail and return a non-zero error for the following conditions: d54 6 a59 4
The DB->set_lorder 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_lorder function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d61 1 a61 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 d33 3 d39 3 a41 11
The DB->set_lorder method configures a database, not only operations performed using the specified DB handle.
The DB->set_lorder 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_lorder will be ignored. If creating additional databases in a file, the byte order specified must be consistent with the existing databases in the file or an error will be returned.
The DB->set_lorder method returns a non-zero error value on failure and 0 on success. d43 1 a43 1
The DB->set_lorder method may fail and return a non-zero error for the following conditions: d48 4 a51 6
The DB->set_lorder 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_lorder method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.