Whole document tree

Whole document tree

Berkeley DB: 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 number 4,321, and little endian order is the number 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 only be used 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.


An invalid flag value or parameter was specified.

See Also

db_create, DB->close, DB->cursor, DB->del, DB->err, DB->fd, DB->get, DB->get_byteswapped, DB->get_type, DB->join, DB->key_range, DB->open, DB->put, DB->remove, 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_flags, DB->set_h_ffactor, DB->set_h_hash, DB->set_h_nelem, DB->set_lorder, DB->set_malloc, DB->set_pagesize, DB->set_paniccall, DB->set_q_extentsize, DB->set_realloc, DB->set_re_delim, DB->set_re_len, DB->set_re_pad, DB->set_re_source, DB->stat, DB->sync, DB->upgrade and DB->verify.


Copyright Sleepycat Software