From 01e6be0f325238643f7ad6a24f9388839f39760b Mon Sep 17 00:00:00 2001 From: unknown Date: Tue, 7 May 2002 18:05:15 +0300 Subject: Remove docs from the bdb distribution Hack to get MIT-pthreads to compile with glibc 2.2 BitKeeper/deleted/.del-index.html~450dd5db21a9bb64: Delete: bdb/docs/index.html BitKeeper/deleted/.del-db_set_h_hash.html~afe952f65389d93b: Delete: bdb/docs/api_cxx/db_set_h_hash.html BitKeeper/deleted/.del-dbc_close.html~2adba79b482ee157: Delete: bdb/docs/api_cxx/dbc_close.html BitKeeper/deleted/.del-env_close.html~5cc705b97b86972c: Delete: bdb/docs/api_cxx/env_close.html BitKeeper/deleted/.del-env_set_feedback.html~1d5bd8dfe2d8034e: Delete: bdb/docs/api_cxx/env_set_feedback.html BitKeeper/deleted/.del-log_file.html~9a724b41d84e0c31: Delete: bdb/docs/api_cxx/log_file.html BitKeeper/deleted/.del-cxx_index.html~a0bc165de8a0554c: Delete: bdb/docs/api_cxx/cxx_index.html BitKeeper/deleted/.del-db_set_bt_prefix.html~ecd8f927371a5dbd: Delete: bdb/docs/api_cxx/db_set_bt_prefix.html BitKeeper/deleted/.del-db_set_errpfx.html~1f26e7b0bb5a067f: Delete: bdb/docs/api_cxx/db_set_errpfx.html BitKeeper/deleted/.del-db_sync.html~dadf1f745e44faa7: Delete: bdb/docs/api_cxx/db_sync.html BitKeeper/deleted/.del-env_set_errcall.html~bae25b45b0196773: Delete: bdb/docs/api_cxx/env_set_errcall.html BitKeeper/deleted/.del-env_set_lk_detect.html~13e53300b722cf1e: Delete: bdb/docs/api_cxx/env_set_lk_detect.html BitKeeper/deleted/.del-lock_vec.html~c55deaa5173a3323: Delete: bdb/docs/api_cxx/lock_vec.html BitKeeper/deleted/.del-log_archive.html~d47f39e6dad7ee50: Delete: bdb/docs/api_cxx/log_archive.html BitKeeper/deleted/.del-log_get.html~aee6162219c71617: Delete: bdb/docs/api_cxx/log_get.html BitKeeper/deleted/.del-memp_trickle.html~c9df8540b9ebc898: Delete: bdb/docs/api_cxx/memp_trickle.html BitKeeper/deleted/.del-db_key_range.html~d79b373af096cb7: Delete: bdb/docs/api_cxx/db_key_range.html BitKeeper/deleted/.del-db_set_re_len.html~e09bb30e40208dfb: Delete: bdb/docs/api_cxx/db_set_re_len.html BitKeeper/deleted/.del-env_set_flags.html~8136e8e1ae16dc02: Delete: bdb/docs/api_cxx/env_set_flags.html BitKeeper/deleted/.del-except_class.html~59839667e43592e: Delete: bdb/docs/api_cxx/except_class.html BitKeeper/deleted/.del-lock_detect.html~bb50519c431233ed: Delete: bdb/docs/api_cxx/lock_detect.html BitKeeper/deleted/.del-mempfile_class.html~672b4aa787b4aeca: Delete: bdb/docs/api_cxx/mempfile_class.html BitKeeper/deleted/.del-txn_begin.html~3a2d1488ec9d8655: Delete: bdb/docs/api_cxx/txn_begin.html BitKeeper/deleted/.del-txn_commit.html~65afb8caf9c470ae: Delete: bdb/docs/api_cxx/txn_commit.html BitKeeper/deleted/.del-db_get.html~3b6e6005f3f17f2a: Delete: bdb/docs/api_cxx/db_get.html BitKeeper/deleted/.del-db_set_bt_minkey.html~d6181e52342005c: Delete: bdb/docs/api_cxx/db_set_bt_minkey.html BitKeeper/deleted/.del-db_set_cachesize.html~3befdbaf98d5a04e: Delete: bdb/docs/api_cxx/db_set_cachesize.html BitKeeper/deleted/.del-what.html~a64f42c697273c44: Delete: bdb/docs/api_cxx/what.html BitKeeper/deleted/.del-cxx_pindex.html~9ff6b69b56f988dd: Delete: bdb/docs/api_cxx/cxx_pindex.html BitKeeper/deleted/.del-db_get_type.html~398668783c4070db: Delete: bdb/docs/api_cxx/db_get_type.html BitKeeper/deleted/.del-db_set_re_source.html~46998978715ccc1: Delete: bdb/docs/api_cxx/db_set_re_source.html BitKeeper/deleted/.del-db_set_realloc.html~64d967a58c328957: Delete: bdb/docs/api_cxx/db_set_realloc.html BitKeeper/deleted/.del-dbc_dup.html~75df863b4bc13aaa: Delete: bdb/docs/api_cxx/dbc_dup.html BitKeeper/deleted/.del-dbt_class.html~fb91648586c1aa77: Delete: bdb/docs/api_cxx/dbt_class.html BitKeeper/deleted/.del-env_open.html~66ac1ae7fa67ca4a: Delete: bdb/docs/api_cxx/env_open.html BitKeeper/deleted/.del-txn_abort.html~81177bcb2e5f4502: Delete: bdb/docs/api_cxx/txn_abort.html BitKeeper/deleted/.del-db_put.html~2792034e8c83c56: Delete: bdb/docs/api_cxx/db_put.html BitKeeper/deleted/.del-db_set_append_recno.html~a158b1fdba756ce: Delete: bdb/docs/api_cxx/db_set_append_recno.html BitKeeper/deleted/.del-db_set_feedback.html~a08620d86f05ec8c: Delete: bdb/docs/api_cxx/db_set_feedback.html BitKeeper/deleted/.del-db_upgrade.html~c6231eb2f9989284: Delete: bdb/docs/api_cxx/db_upgrade.html BitKeeper/deleted/.del-dbenv_class.html~5ab8aaf8a531f76b: Delete: bdb/docs/api_cxx/dbenv_class.html BitKeeper/deleted/.del-env_set_lg_dir.html~c08aac264e7faa97: Delete: bdb/docs/api_cxx/env_set_lg_dir.html BitKeeper/deleted/.del-env_set_lk_max.html~52ac3c4ca2876de: Delete: bdb/docs/api_cxx/env_set_lk_max.html BitKeeper/deleted/.del-lock_id.html~b3c7995efbe12c16: Delete: bdb/docs/api_cxx/lock_id.html BitKeeper/deleted/.del-db_close.html~cc570e65ac7d22f: Delete: bdb/docs/api_cxx/db_close.html BitKeeper/deleted/.del-db_open.html~ab95c48ac26ad3f7: Delete: bdb/docs/api_cxx/db_open.html BitKeeper/deleted/.del-db_set_bt_compare.html~d888d1ebe056bc6b: Delete: bdb/docs/api_cxx/db_set_bt_compare.html BitKeeper/deleted/.del-db_set_flags.html~1146625feeb3bb0b: Delete: bdb/docs/api_cxx/db_set_flags.html BitKeeper/deleted/.del-db_set_q_extentsize.html~b17e340a68ede3ac: Delete: bdb/docs/api_cxx/db_set_q_extentsize.html BitKeeper/deleted/.del-dbc_get.html~36e2dbe65e3442e3: Delete: bdb/docs/api_cxx/dbc_get.html BitKeeper/deleted/.del-env_set_lk_conflicts.html~5bba88df4cc6dfba: Delete: bdb/docs/api_cxx/env_set_lk_conflicts.html BitKeeper/deleted/.del-get_errno.html~e1a57c1c5f1d2695: Delete: bdb/docs/api_cxx/get_errno.html BitKeeper/deleted/.del-txn_id.html~162661f4c2dc09d6: Delete: bdb/docs/api_cxx/txn_id.html BitKeeper/deleted/.del-db_rename.html~9c0a820e864220b3: Delete: bdb/docs/api_cxx/db_rename.html BitKeeper/deleted/.del-db_set_lorder.html~a46750a29588268c: Delete: bdb/docs/api_cxx/db_set_lorder.html BitKeeper/deleted/.del-env_remove.html~5efece7ecdfc4df7: Delete: bdb/docs/api_cxx/env_remove.html BitKeeper/deleted/.del-env_set_mutexlocks.html~f73e7ffdd2d8d62f: Delete: bdb/docs/api_cxx/env_set_mutexlocks.html BitKeeper/deleted/.del-env_set_tas_spins.html~a107049f4776b358: Delete: bdb/docs/api_cxx/env_set_tas_spins.html BitKeeper/deleted/.del-env_version.html~1cff25c44cbea934: Delete: bdb/docs/api_cxx/env_version.html BitKeeper/deleted/.del-lock_put.html~9eb85a1c9e88621: Delete: bdb/docs/api_cxx/lock_put.html BitKeeper/deleted/.del-memp_fset.html~e52fa0488faa893: Delete: bdb/docs/api_cxx/memp_fset.html BitKeeper/deleted/.del-memp_sync.html~253961279934d3c8: Delete: bdb/docs/api_cxx/memp_sync.html BitKeeper/deleted/.del-db_remove.html~8c537fc5e326293b: Delete: bdb/docs/api_cxx/db_remove.html BitKeeper/deleted/.del-env_set_errpfx.html~d26da4bab9538234: Delete: bdb/docs/api_cxx/env_set_errpfx.html BitKeeper/deleted/.del-log_put.html~66077da9630fa8c2: Delete: bdb/docs/api_cxx/log_put.html BitKeeper/deleted/.del-lsn_class.html~34809f73e15540ad: Delete: bdb/docs/api_cxx/lsn_class.html BitKeeper/deleted/.del-memp_fput.html~7ee8cda6287dee81: Delete: bdb/docs/api_cxx/memp_fput.html BitKeeper/deleted/.del-txn_class.html~5e57abe095aceca9: Delete: bdb/docs/api_cxx/txn_class.html BitKeeper/deleted/.del-db_class.html~3129ff8c53721fe8: Delete: bdb/docs/api_cxx/db_class.html BitKeeper/deleted/.del-db_set_errfile.html~f6eddb9ab7ef07d0: Delete: bdb/docs/api_cxx/db_set_errfile.html BitKeeper/deleted/.del-db_set_h_ffactor.html~a67084c644c38114: Delete: bdb/docs/api_cxx/db_set_h_ffactor.html BitKeeper/deleted/.del-db_set_malloc.html~b0aa5802da5bef4d: Delete: bdb/docs/api_cxx/db_set_malloc.html BitKeeper/deleted/.del-db_set_re_delim.html~81d9df93c3511df3: Delete: bdb/docs/api_cxx/db_set_re_delim.html BitKeeper/deleted/.del-db_verify.html~14db455da528229d: Delete: bdb/docs/api_cxx/db_verify.html BitKeeper/deleted/.del-env_set_lg_max.html~4f7ba5f02c66c0de: Delete: bdb/docs/api_cxx/env_set_lg_max.html BitKeeper/deleted/.del-env_set_lk_max_objects.html~c47424e4d13d5327: Delete: bdb/docs/api_cxx/env_set_lk_max_objects.html BitKeeper/deleted/.del-memp_register.html~cba6f572fe27c7a: Delete: bdb/docs/api_cxx/memp_register.html BitKeeper/deleted/.del-db_join.html~9c4819679501ad6e: Delete: bdb/docs/api_cxx/db_join.html BitKeeper/deleted/.del-db_set_h_nelem.html~1829bc583d9c7554: Delete: bdb/docs/api_cxx/db_set_h_nelem.html BitKeeper/deleted/.del-db_set_paniccall.html~6bc911c9d64e9237: Delete: bdb/docs/api_cxx/db_set_paniccall.html BitKeeper/deleted/.del-db_set_re_pad.html~f2e0c2c2c3806a97: Delete: bdb/docs/api_cxx/db_set_re_pad.html BitKeeper/deleted/.del-dbc_class.html~2a31b398c37d674b: Delete: bdb/docs/api_cxx/dbc_class.html BitKeeper/deleted/.del-env_set_rec_init.html~77916e00d1361c7b: Delete: bdb/docs/api_cxx/env_set_rec_init.html BitKeeper/deleted/.del-env_set_region_init.html~2d70678382bbbf9a: Delete: bdb/docs/api_cxx/env_set_region_init.html BitKeeper/deleted/.del-env_strerror.html~7e1cbfbd096ca: Delete: bdb/docs/api_cxx/env_strerror.html BitKeeper/deleted/.del-txn_checkpoint.html~173930473e76d008: Delete: bdb/docs/api_cxx/txn_checkpoint.html BitKeeper/deleted/.del-db_fd.html~99ec316575f80428: Delete: bdb/docs/api_cxx/db_fd.html BitKeeper/deleted/.del-db_set_dup_compare.html~91f36955a213e0f4: Delete: bdb/docs/api_cxx/db_set_dup_compare.html BitKeeper/deleted/.del-db_stat.html~3473827de856d680: Delete: bdb/docs/api_cxx/db_stat.html BitKeeper/deleted/.del-env_set_cachesize.html~b82ed49a47415fec: Delete: bdb/docs/api_cxx/env_set_cachesize.html BitKeeper/deleted/.del-env_set_lg_bsize.html~7fd917bea6b163bf: Delete: bdb/docs/api_cxx/env_set_lg_bsize.html BitKeeper/deleted/.del-env_set_server.html~bb74806839e8eb58: Delete: bdb/docs/api_cxx/env_set_server.html BitKeeper/deleted/.del-lock_get.html~527d63a8526f336c: Delete: bdb/docs/api_cxx/lock_get.html BitKeeper/deleted/.del-memp_fget.html~bfe74f8c299c2995: Delete: bdb/docs/api_cxx/memp_fget.html BitKeeper/deleted/.del-memp_fopen.html~abfef0a4db99c8e1: Delete: bdb/docs/api_cxx/memp_fopen.html BitKeeper/deleted/.del-db_get_byteswapped.html~a44d5d57d050b466: Delete: bdb/docs/api_cxx/db_get_byteswapped.html BitKeeper/deleted/.del-dbc_count.html~bc025b8894450525: Delete: bdb/docs/api_cxx/dbc_count.html BitKeeper/deleted/.del-dbc_del.html~424fc0ebb3b4c5cf: Delete: bdb/docs/api_cxx/dbc_del.html BitKeeper/deleted/.del-env_set_tmp_dir.html~6c815da1fad27537: Delete: bdb/docs/api_cxx/env_set_tmp_dir.html BitKeeper/deleted/.del-env_set_tx_timestamp.html~6396a1145f8e41c1: Delete: bdb/docs/api_cxx/env_set_tx_timestamp.html BitKeeper/deleted/.del-log_unregister.html~8fa1fe691751d6ad: Delete: bdb/docs/api_cxx/log_unregister.html BitKeeper/deleted/.del-memp_fclose.html~cc4a5776ac69d660: Delete: bdb/docs/api_cxx/memp_fclose.html BitKeeper/deleted/.del-txn_stat.html~e8e25f86f8541696: Delete: bdb/docs/api_cxx/txn_stat.html BitKeeper/deleted/.del-db_cursor.html~4f0225f98f4a11c: Delete: bdb/docs/api_cxx/db_cursor.html BitKeeper/deleted/.del-db_err.html~77022bd5af575696: Delete: bdb/docs/api_cxx/db_err.html BitKeeper/deleted/.del-env_set_lk_max_lockers.html~ebb61fd669c2eefb: Delete: bdb/docs/api_cxx/env_set_lk_max_lockers.html BitKeeper/deleted/.del-env_set_mp_mmapsize.html~c21e3f9c5a29b0ab: Delete: bdb/docs/api_cxx/env_set_mp_mmapsize.html BitKeeper/deleted/.del-lock_class.html~ed88ab78cccbef8d: Delete: bdb/docs/api_cxx/lock_class.html BitKeeper/deleted/.del-txn_prepare.html~818b4163518bace5: Delete: bdb/docs/api_cxx/txn_prepare.html BitKeeper/deleted/.del-db_set_errcall.html~28a7a1fa2b3b73ee: Delete: bdb/docs/api_cxx/db_set_errcall.html BitKeeper/deleted/.del-env_set_errfile.html~f9543c9e65ed6a1d: Delete: bdb/docs/api_cxx/env_set_errfile.html BitKeeper/deleted/.del-env_set_lk_max_locks.html~bbde4ffbcc607f61: Delete: bdb/docs/api_cxx/env_set_lk_max_locks.html BitKeeper/deleted/.del-env_set_tx_recover.html~cdf13797131b2d97: Delete: bdb/docs/api_cxx/env_set_tx_recover.html BitKeeper/deleted/.del-log_compare.html~3225b4c32016c9b1: Delete: bdb/docs/api_cxx/log_compare.html BitKeeper/deleted/.del-log_register.html~55470e0d79382beb: Delete: bdb/docs/api_cxx/log_register.html BitKeeper/deleted/.del-log_stat.html~dc2d4ffe7950fc09: Delete: bdb/docs/api_cxx/log_stat.html BitKeeper/deleted/.del-memp_fsync.html~76d47da7c5dc8932: Delete: bdb/docs/api_cxx/memp_fsync.html BitKeeper/deleted/.del-memp_stat.html~d370717a78971be1: Delete: bdb/docs/api_cxx/memp_stat.html BitKeeper/deleted/.del-db_del.html~43fa05f2dfa86dbc: Delete: bdb/docs/api_cxx/db_del.html BitKeeper/deleted/.del-dbc_put.html~11e6aa2492dd1032: Delete: bdb/docs/api_cxx/dbc_put.html BitKeeper/deleted/.del-env_set_error_stream.html~a4101c1d68559fa2: Delete: bdb/docs/api_cxx/env_set_error_stream.html BitKeeper/deleted/.del-env_set_pageyield.html~db4e5bdf71e171c0: Delete: bdb/docs/api_cxx/env_set_pageyield.html BitKeeper/deleted/.del-env_set_paniccall.html~2080056f15faa516: Delete: bdb/docs/api_cxx/env_set_paniccall.html BitKeeper/deleted/.del-env_set_shm_key.html~65b2c2f848ddf31e: Delete: bdb/docs/api_cxx/env_set_shm_key.html BitKeeper/deleted/.del-env_set_tx_max.html~910d1c17dd000729: Delete: bdb/docs/api_cxx/env_set_tx_max.html BitKeeper/deleted/.del-lock_stat.html~2112ceb0894b34d8: Delete: bdb/docs/api_cxx/lock_stat.html BitKeeper/deleted/.del-log_flush.html~3976f77e905f35eb: Delete: bdb/docs/api_cxx/log_flush.html BitKeeper/deleted/.del-db_set_h_hash.html~73f14897664d9d08: Delete: bdb/docs/api_c/db_set_h_hash.html BitKeeper/deleted/.del-db_set_pagesize.html~b8d544ec3e102c6c: Delete: bdb/docs/api_cxx/db_set_pagesize.html BitKeeper/deleted/.del-dbc_close.html~a3ad4ea563bafc42: Delete: bdb/docs/api_c/dbc_close.html BitKeeper/deleted/.del-env_close.html~a8e722cbb66c9d7b: Delete: bdb/docs/api_c/env_close.html BitKeeper/deleted/.del-env_set_data_dir.html~9176f081597e4f27: Delete: bdb/docs/api_cxx/env_set_data_dir.html BitKeeper/deleted/.del-env_set_panicstate.html~ad2d38e398cafd31: Delete: bdb/docs/api_cxx/env_set_panicstate.html BitKeeper/deleted/.del-env_set_verbose.html~e804a65368b5cdc1: Delete: bdb/docs/api_cxx/env_set_verbose.html BitKeeper/deleted/.del-log_file.html~574444b46b801f9c: Delete: bdb/docs/api_c/log_file.html BitKeeper/deleted/.del-c_pindex.html~697acebf58a8db4: Delete: bdb/docs/api_c/c_pindex.html BitKeeper/deleted/.del-env_set_feedback.html~87a78f97ba545aba: Delete: bdb/docs/api_c/env_set_feedback.html BitKeeper/deleted/.del-env_set_lk_detect.html~d9ed73495defdc19: Delete: bdb/docs/api_c/env_set_lk_detect.html BitKeeper/deleted/.del-hsearch.html~a8b76d897a8216d8: Delete: bdb/docs/api_c/hsearch.html BitKeeper/deleted/.del-lock_vec.html~cc79e33b82b7a275: Delete: bdb/docs/api_c/lock_vec.html BitKeeper/deleted/.del-set_func_ioinfo.html~80365bb8c66ae84c: Delete: bdb/docs/api_c/set_func_ioinfo.html BitKeeper/deleted/.del-set_func_malloc.html~5579a0604e14e1e7: Delete: bdb/docs/api_c/set_func_malloc.html BitKeeper/deleted/.del-set_func_write.html~63567be42d586fde: Delete: bdb/docs/api_c/set_func_write.html BitKeeper/deleted/.del-db_set_bt_prefix.html~d6e443a7e47c9b3a: Delete: bdb/docs/api_c/db_set_bt_prefix.html BitKeeper/deleted/.del-db_set_errpfx.html~756b9b73dd28b8d9: Delete: bdb/docs/api_c/db_set_errpfx.html BitKeeper/deleted/.del-db_sync.html~7a067029b6e1496b: Delete: bdb/docs/api_c/db_sync.html BitKeeper/deleted/.del-env_set_errcall.html~ba09eec1ba15f15f: Delete: bdb/docs/api_c/env_set_errcall.html BitKeeper/deleted/.del-log_archive.html~490428ce45f9f918: Delete: bdb/docs/api_c/log_archive.html BitKeeper/deleted/.del-log_get.html~24cdf17ba55cbecf: Delete: bdb/docs/api_c/log_get.html BitKeeper/deleted/.del-memp_trickle.html~8b1adf1404d7a5f: Delete: bdb/docs/api_c/memp_trickle.html BitKeeper/deleted/.del-set_func_fsync.html~f59339ff63d95e7d: Delete: bdb/docs/api_c/set_func_fsync.html BitKeeper/deleted/.del-c_index.html~1a854fa55012906: Delete: bdb/docs/api_c/c_index.html BitKeeper/deleted/.del-db_key_range.html~1060761b1e359d85: Delete: bdb/docs/api_c/db_key_range.html BitKeeper/deleted/.del-db_set_re_len.html~f30d68257bd60e1e: Delete: bdb/docs/api_c/db_set_re_len.html BitKeeper/deleted/.del-env_set_flags.html~b2a1f3c8498e6d95: Delete: bdb/docs/api_c/env_set_flags.html BitKeeper/deleted/.del-lock_detect.html~8fe406dce10e0bb: Delete: bdb/docs/api_c/lock_detect.html BitKeeper/deleted/.del-txn_begin.html~557b34fd3e7363: Delete: bdb/docs/api_c/txn_begin.html BitKeeper/deleted/.del-txn_commit.html~8950b5e11c8b0778: Delete: bdb/docs/api_c/txn_commit.html BitKeeper/deleted/.del-db_get.html~7e0018b93ee31eba: Delete: bdb/docs/api_c/db_get.html BitKeeper/deleted/.del-db_get_type.html~d66aa1642a4d20e2: Delete: bdb/docs/api_c/db_get_type.html BitKeeper/deleted/.del-db_set_bt_minkey.html~e2d52ba2d0174432: Delete: bdb/docs/api_c/db_set_bt_minkey.html BitKeeper/deleted/.del-db_set_cachesize.html~47a3c8ca486eb013: Delete: bdb/docs/api_c/db_set_cachesize.html BitKeeper/deleted/.del-db_set_re_source.html~6d12ac12652acc31: Delete: bdb/docs/api_c/db_set_re_source.html BitKeeper/deleted/.del-dbc_dup.html~3bdf8b0a687b43f3: Delete: bdb/docs/api_c/dbc_dup.html BitKeeper/deleted/.del-env_open.html~e4c9706220a4cd9b: Delete: bdb/docs/api_c/env_open.html BitKeeper/deleted/.del-txn_abort.html~a53425dd70214619: Delete: bdb/docs/api_c/txn_abort.html BitKeeper/deleted/.del-db_put.html~ea78709ffb6cd7e8: Delete: bdb/docs/api_c/db_put.html BitKeeper/deleted/.del-db_set_append_recno.html~bdf0130e642f74fa: Delete: bdb/docs/api_c/db_set_append_recno.html BitKeeper/deleted/.del-db_set_feedback.html~90d495e78318a332: Delete: bdb/docs/api_c/db_set_feedback.html BitKeeper/deleted/.del-db_set_realloc.html~a9be244baf966892: Delete: bdb/docs/api_c/db_set_realloc.html BitKeeper/deleted/.del-db_upgrade.html~5e6210d6f09a0c3e: Delete: bdb/docs/api_c/db_upgrade.html BitKeeper/deleted/.del-dbt.html~ae7a81c9c5f574f6: Delete: bdb/docs/api_c/dbt.html BitKeeper/deleted/.del-env_set_lg_dir.html~26be310214a2ff8f: Delete: bdb/docs/api_c/env_set_lg_dir.html BitKeeper/deleted/.del-env_set_lk_max.html~a2dc11fa8b2f1c9: Delete: bdb/docs/api_c/env_set_lk_max.html BitKeeper/deleted/.del-lock_id.html~c9ee776f928a38f: Delete: bdb/docs/api_c/lock_id.html BitKeeper/deleted/.del-db_close.html~fda0b4dfa946f44e: Delete: bdb/docs/api_c/db_close.html BitKeeper/deleted/.del-db_set_bt_compare.html~e55a311bb0be93a8: Delete: bdb/docs/api_c/db_set_bt_compare.html BitKeeper/deleted/.del-db_set_flags.html~4cd3700ae4387d22: Delete: bdb/docs/api_c/db_set_flags.html BitKeeper/deleted/.del-db_set_q_extentsize.html~f2fe41a5d8c46658: Delete: bdb/docs/api_c/db_set_q_extentsize.html BitKeeper/deleted/.del-env_create.html~3e73dd35fe5dcc8: Delete: bdb/docs/api_c/env_create.html BitKeeper/deleted/.del-env_set_lk_conflicts.html~58d9f7179bc864a3: Delete: bdb/docs/api_c/env_set_lk_conflicts.html BitKeeper/deleted/.del-db_open.html~59dfa6e5198c382e: Delete: bdb/docs/api_c/db_open.html BitKeeper/deleted/.del-db_set_lorder.html~e24ae76325374653: Delete: bdb/docs/api_c/db_set_lorder.html BitKeeper/deleted/.del-dbc_get.html~4bf7579a92c35195: Delete: bdb/docs/api_c/dbc_get.html BitKeeper/deleted/.del-env_version.html~9bf7f99fefacc2bf: Delete: bdb/docs/api_c/env_version.html BitKeeper/deleted/.del-lock_put.html~f5bc2f52e55f16e1: Delete: bdb/docs/api_c/lock_put.html BitKeeper/deleted/.del-txn_id.html~1e71088a7e8f6678: Delete: bdb/docs/api_c/txn_id.html BitKeeper/deleted/.del-db_rename.html~36796ad9e106c3f0: Delete: bdb/docs/api_c/db_rename.html BitKeeper/deleted/.del-env_set_mutexlocks.html~85bbd53b877cafe1: Delete: bdb/docs/api_c/env_set_mutexlocks.html BitKeeper/deleted/.del-env_set_tas_spins.html~91c7091deca3d97f: Delete: bdb/docs/api_c/env_set_tas_spins.html BitKeeper/deleted/.del-memp_fset.html~ecb97931b222568d: Delete: bdb/docs/api_c/memp_fset.html BitKeeper/deleted/.del-memp_sync.html~b387035a94c20c50: Delete: bdb/docs/api_c/memp_sync.html BitKeeper/deleted/.del-db_remove.html~668fa1d67a4f6941: Delete: bdb/docs/api_c/db_remove.html BitKeeper/deleted/.del-env_remove.html~a71d5e1ca41324a7: Delete: bdb/docs/api_c/env_remove.html BitKeeper/deleted/.del-env_set_errpfx.html~806c8c438d0ee36c: Delete: bdb/docs/api_c/env_set_errpfx.html BitKeeper/deleted/.del-log_put.html~11a1bec49bb90419: Delete: bdb/docs/api_c/log_put.html BitKeeper/deleted/.del-memp_fput.html~4a7aace7db01ee15: Delete: bdb/docs/api_c/memp_fput.html BitKeeper/deleted/.del-set_func_dirfree.html~d59f36547c7b5384: Delete: bdb/docs/api_c/set_func_dirfree.html BitKeeper/deleted/.del-set_func_dirlist.html~24e75ccc86809023: Delete: bdb/docs/api_c/set_func_dirlist.html BitKeeper/deleted/.del-db_set_errfile.html~f07d3c57bb3c8fbd: Delete: bdb/docs/api_c/db_set_errfile.html BitKeeper/deleted/.del-db_set_h_ffactor.html~41352ddf74ccc338: Delete: bdb/docs/api_c/db_set_h_ffactor.html BitKeeper/deleted/.del-db_set_malloc.html~3581879fef5af695: Delete: bdb/docs/api_c/db_set_malloc.html BitKeeper/deleted/.del-db_set_re_delim.html~e0a7face764111b9: Delete: bdb/docs/api_c/db_set_re_delim.html BitKeeper/deleted/.del-db_verify.html~cf80f5ba845eac2e: Delete: bdb/docs/api_c/db_verify.html BitKeeper/deleted/.del-env_set_lg_max.html~319c24b5245b0685: Delete: bdb/docs/api_c/env_set_lg_max.html BitKeeper/deleted/.del-env_set_lk_max_objects.html~1a428bbee06cb5cc: Delete: bdb/docs/api_c/env_set_lk_max_objects.html BitKeeper/deleted/.del-set_func_rename.html~3f8c7b6674cda105: Delete: bdb/docs/api_c/set_func_rename.html BitKeeper/deleted/.del-db_join.html~a58c2d81ecfea5b: Delete: bdb/docs/api_c/db_join.html BitKeeper/deleted/.del-db_set_h_nelem.html~bd8371e033b15c8f: Delete: bdb/docs/api_c/db_set_h_nelem.html BitKeeper/deleted/.del-db_set_re_pad.html~8a1de721eb6fc53f: Delete: bdb/docs/api_c/db_set_re_pad.html BitKeeper/deleted/.del-env_set_region_init.html~2ca19f76ee1ae790: Delete: bdb/docs/api_c/env_set_region_init.html BitKeeper/deleted/.del-env_strerror.html~7f090bf26bdd4dc: Delete: bdb/docs/api_c/env_strerror.html BitKeeper/deleted/.del-memp_register.html~8b9dff9b5043da58: Delete: bdb/docs/api_c/memp_register.html BitKeeper/deleted/.del-set_func_open.html~8c812591efc8abe6: Delete: bdb/docs/api_c/set_func_open.html BitKeeper/deleted/.del-txn_checkpoint.html~4a1704dbfcaad5dc: Delete: bdb/docs/api_c/txn_checkpoint.html BitKeeper/deleted/.del-db_create.html~a87157ea60c82ee2: Delete: bdb/docs/api_c/db_create.html BitKeeper/deleted/.del-db_set_dup_compare.html~a833bfc727a794e7: Delete: bdb/docs/api_c/db_set_dup_compare.html BitKeeper/deleted/.del-db_set_paniccall.html~ac7f63325b4499ce: Delete: bdb/docs/api_c/db_set_paniccall.html BitKeeper/deleted/.del-env_set_lg_bsize.html~1eb03c137a42e80f: Delete: bdb/docs/api_c/env_set_lg_bsize.html BitKeeper/deleted/.del-env_set_rec_init.html~bf7da051ef6689ba: Delete: bdb/docs/api_c/env_set_rec_init.html BitKeeper/deleted/.del-memp_fget.html~460714b5c2e3e1c5: Delete: bdb/docs/api_c/memp_fget.html BitKeeper/deleted/.del-set_func_sleep.html~4b962c8b82989d8c: Delete: bdb/docs/api_c/set_func_sleep.html BitKeeper/deleted/.del-env_set_cachesize.html~f4c341d3f2c09469: Delete: bdb/docs/api_c/env_set_cachesize.html BitKeeper/deleted/.del-env_set_server.html~c13b793b525d504b: Delete: bdb/docs/api_c/env_set_server.html BitKeeper/deleted/.del-memp_fopen.html~d032a963a0103472: Delete: bdb/docs/api_c/memp_fopen.html BitKeeper/deleted/.del-set_func_free.html~ed61d2dfea9e069e: Delete: bdb/docs/api_c/set_func_free.html BitKeeper/deleted/.del-set_func_unlink.html~c42b13fd26f2e90: Delete: bdb/docs/api_c/set_func_unlink.html BitKeeper/deleted/.del-set_func_unmap.html~d85790692f3b536e: Delete: bdb/docs/api_c/set_func_unmap.html BitKeeper/deleted/.del-db_fd.html~15a01776b340a959: Delete: bdb/docs/api_c/db_fd.html BitKeeper/deleted/.del-db_stat.html~578f6f99f8e247ff: Delete: bdb/docs/api_c/db_stat.html BitKeeper/deleted/.del-dbc_count.html~c3cd00c48b4babf5: Delete: bdb/docs/api_c/dbc_count.html BitKeeper/deleted/.del-env_set_tmp_dir.html~b563e87af5431824: Delete: bdb/docs/api_c/env_set_tmp_dir.html BitKeeper/deleted/.del-env_set_tx_timestamp.html~ddb77d7dfb531085: Delete: bdb/docs/api_c/env_set_tx_timestamp.html BitKeeper/deleted/.del-lock_get.html~63399d204f1885fa: Delete: bdb/docs/api_c/lock_get.html BitKeeper/deleted/.del-log_unregister.html~45b8f9d3f8eb3d80: Delete: bdb/docs/api_c/log_unregister.html BitKeeper/deleted/.del-memp_fclose.html~b52c7d599d83c26: Delete: bdb/docs/api_c/memp_fclose.html BitKeeper/deleted/.del-db_get_byteswapped.html~bcab4145183a7be2: Delete: bdb/docs/api_c/db_get_byteswapped.html BitKeeper/deleted/.del-db_lsn.html~5edb9bce1118feae: Delete: bdb/docs/api_c/db_lsn.html BitKeeper/deleted/.del-dbc_del.html~2685f75d28e4ad99: Delete: bdb/docs/api_c/dbc_del.html BitKeeper/deleted/.del-env_set_lk_max_lockers.html~f22d5d4640436efe: Delete: bdb/docs/api_c/env_set_lk_max_lockers.html BitKeeper/deleted/.del-env_set_mp_mmapsize.html~21f27997f00accfe: Delete: bdb/docs/api_c/env_set_mp_mmapsize.html BitKeeper/deleted/.del-set_func_read.html~c8f6ece1ed408bf8: Delete: bdb/docs/api_c/set_func_read.html BitKeeper/deleted/.del-set_func_seek.html~fdf1b31d3f6c7473: Delete: bdb/docs/api_c/set_func_seek.html BitKeeper/deleted/.del-txn_prepare.html~19f84203db4e6608: Delete: bdb/docs/api_c/txn_prepare.html BitKeeper/deleted/.del-txn_stat.html~f57a656bfbac12bf: Delete: bdb/docs/api_c/txn_stat.html BitKeeper/deleted/.del-db_cursor.html~7431dd96ed3492c: Delete: bdb/docs/api_c/db_cursor.html BitKeeper/deleted/.del-db_err.html~3696088bd85eeda3: Delete: bdb/docs/api_c/db_err.html BitKeeper/deleted/.del-db_set_errcall.html~faf92be4ee8bc634: Delete: bdb/docs/api_c/db_set_errcall.html BitKeeper/deleted/.del-dbm.html~ebf1d8e329b06bba: Delete: bdb/docs/api_c/dbm.html BitKeeper/deleted/.del-env_set_errfile.html~3b6b0822f29fc3d4: Delete: bdb/docs/api_c/env_set_errfile.html BitKeeper/deleted/.del-env_set_tx_recover.html~8dd351545b444a24: Delete: bdb/docs/api_c/env_set_tx_recover.html BitKeeper/deleted/.del-set_func_close.html~8981d16589844161: Delete: bdb/docs/api_c/set_func_close.html BitKeeper/deleted/.del-env_set_lk_max_locks.html~1baf2d63a6fb418d: Delete: bdb/docs/api_c/env_set_lk_max_locks.html BitKeeper/deleted/.del-log_compare.html~4f12fdf04d30ab94: Delete: bdb/docs/api_c/log_compare.html BitKeeper/deleted/.del-log_register.html~5381c1fad82d6527: Delete: bdb/docs/api_c/log_register.html BitKeeper/deleted/.del-log_stat.html~36b87b19ee2c5bba: Delete: bdb/docs/api_c/log_stat.html BitKeeper/deleted/.del-memp_fsync.html~a95ab802bb28646f: Delete: bdb/docs/api_c/memp_fsync.html BitKeeper/deleted/.del-memp_stat.html~55a9521fe04b03bd: Delete: bdb/docs/api_c/memp_stat.html BitKeeper/deleted/.del-set_func_exists.html~23f077e82ca8f827: Delete: bdb/docs/api_c/set_func_exists.html BitKeeper/deleted/.del-set_func_realloc.html~e8e78e57c005c7c4: Delete: bdb/docs/api_c/set_func_realloc.html BitKeeper/deleted/.del-db_del.html~e8bffcf9be371317: Delete: bdb/docs/api_c/db_del.html BitKeeper/deleted/.del-dbc_put.html~a2c4a52329376657: Delete: bdb/docs/api_c/dbc_put.html BitKeeper/deleted/.del-env_set_pageyield.html~8aa4a6cb2f18cad7: Delete: bdb/docs/api_c/env_set_pageyield.html BitKeeper/deleted/.del-env_set_paniccall.html~97a1d58189199453: Delete: bdb/docs/api_c/env_set_paniccall.html BitKeeper/deleted/.del-env_set_shm_key.html~cf5aaa6a995cbf55: Delete: bdb/docs/api_c/env_set_shm_key.html BitKeeper/deleted/.del-lock_stat.html~d9a98bb949070b: Delete: bdb/docs/api_c/lock_stat.html BitKeeper/deleted/.del-db_set_pagesize.html~9644fa0f538cde17: Delete: bdb/docs/api_c/db_set_pagesize.html BitKeeper/deleted/.del-env_set_data_dir.html~437cec65e441c60: Delete: bdb/docs/api_c/env_set_data_dir.html BitKeeper/deleted/.del-env_set_panicstate.html~43228366ca64363c: Delete: bdb/docs/api_c/env_set_panicstate.html BitKeeper/deleted/.del-env_set_tx_max.html~71a739e46faf33a9: Delete: bdb/docs/api_c/env_set_tx_max.html BitKeeper/deleted/.del-env_set_verbose.html~344f5119536cae0: Delete: bdb/docs/api_c/env_set_verbose.html BitKeeper/deleted/.del-log_flush.html~bb8bc4fc43c9f63d: Delete: bdb/docs/api_c/log_flush.html BitKeeper/deleted/.del-set_func_map.html~d90bbc8462ef43a6: Delete: bdb/docs/api_c/set_func_map.html BitKeeper/deleted/.del-set_func_yield.html~ca5e359bcbeca7fd: Delete: bdb/docs/api_c/set_func_yield.html BitKeeper/deleted/.del-config.html~c7337cb30f9bf66: Delete: bdb/docs/ref/txn/config.html BitKeeper/deleted/.del-contact.html~55b4da3d7bf7655b: Delete: bdb/docs/sleepycat/contact.html BitKeeper/deleted/.del-intro.html~85fabd5518fb26be: Delete: bdb/docs/ref/txn/intro.html BitKeeper/deleted/.del-legal.html~7388af4c578cacf6: Delete: bdb/docs/sleepycat/legal.html BitKeeper/deleted/.del-license.html~9371001bbf0ba2dd: Delete: bdb/docs/sleepycat/license.html BitKeeper/deleted/.del-nested.html~6860bbf2f29aa93b: Delete: bdb/docs/ref/txn/nested.html BitKeeper/deleted/.del-other.html~4991722636b3a46d: Delete: bdb/docs/ref/txn/other.html BitKeeper/deleted/.del-flags.html~a739404f90eb8c3d: Delete: bdb/docs/ref/build_unix/flags.html BitKeeper/deleted/.del-hpux.html~d34942564699608: Delete: bdb/docs/ref/build_unix/hpux.html BitKeeper/deleted/.del-limits.html~3004b7a93dab148b: Delete: bdb/docs/ref/txn/limits.html BitKeeper/deleted/.del-linux.html~f9f2d09dc6df75e: Delete: bdb/docs/ref/build_unix/linux.html BitKeeper/deleted/.del-sco.html~e25f6271a1b753d0: Delete: bdb/docs/ref/build_unix/sco.html BitKeeper/deleted/.del-shlib.html~7168ed40f2e1155d: Delete: bdb/docs/ref/build_unix/shlib.html BitKeeper/deleted/.del-test.html~b2c2f275a0c3e783: Delete: bdb/docs/ref/build_unix/test.html BitKeeper/deleted/.del-aix.html~e8ae448bdb85fa22: Delete: bdb/docs/ref/build_unix/aix.html BitKeeper/deleted/.del-install.html~660222dd1feffc4: Delete: bdb/docs/ref/build_unix/install.html BitKeeper/deleted/.del-intro.html~f261022c26987d7f: Delete: bdb/docs/ref/build_unix/intro.html BitKeeper/deleted/.del-irix.html~95833aedc3a82f0: Delete: bdb/docs/ref/build_unix/irix.html BitKeeper/deleted/.del-notes.html~97e9b52853db15ea: Delete: bdb/docs/ref/build_unix/notes.html BitKeeper/deleted/.del-qnx.html~6d2849a8e8038dc9: Delete: bdb/docs/ref/build_unix/qnx.html BitKeeper/deleted/.del-ultrix.html~a1dd780edcde11f6: Delete: bdb/docs/ref/build_unix/ultrix.html BitKeeper/deleted/.del-conf.html~d0378c69618b790b: Delete: bdb/docs/ref/build_unix/conf.html BitKeeper/deleted/.del-freebsd.html~8ed2a42e1668004c: Delete: bdb/docs/ref/build_unix/freebsd.html BitKeeper/deleted/.del-open.html~37a6e67d520d6c00: Delete: bdb/docs/ref/env/open.html BitKeeper/deleted/.del-osf1.html~9d4ebabfe3af8970: Delete: bdb/docs/ref/build_unix/osf1.html BitKeeper/deleted/.del-solaris.html~3a85fb541538d0d7: Delete: bdb/docs/ref/build_unix/solaris.html BitKeeper/deleted/.del-sunos.html~fc41965e9d95985c: Delete: bdb/docs/ref/build_unix/sunos.html BitKeeper/deleted/.del-create.html~9f454cb1910df0b8: Delete: bdb/docs/ref/env/create.html BitKeeper/deleted/.del-error.html~acbbdb848c9fe70f: Delete: bdb/docs/ref/env/error.html BitKeeper/deleted/.del-intro.html~96dd1090729e06b: Delete: bdb/docs/ref/env/intro.html BitKeeper/deleted/.del-naming.html~1f041789686cc8a0: Delete: bdb/docs/ref/env/naming.html BitKeeper/deleted/.del-remote.html~52a3a79fdff8f7bd: Delete: bdb/docs/ref/env/remote.html BitKeeper/deleted/.del-security.html~e455f95aee7f5cd2: Delete: bdb/docs/ref/env/security.html BitKeeper/deleted/.del-config.html~aedc53caf49c51c9: Delete: bdb/docs/ref/log/config.html BitKeeper/deleted/.del-convert.html~d7f18eb34c1b6ae: Delete: bdb/docs/ref/upgrade.2.0/convert.html BitKeeper/deleted/.del-disk.html~94dc4e6e3668e613: Delete: bdb/docs/ref/upgrade.2.0/disk.html BitKeeper/deleted/.del-intro.html~8bfd3804a2da1598: Delete: bdb/docs/ref/upgrade.2.0/intro.html BitKeeper/deleted/.del-region.html~cc94139c8daa7f6a: Delete: bdb/docs/ref/env/region.html BitKeeper/deleted/.del-system.html~eae0256a127c3c89: Delete: bdb/docs/ref/upgrade.2.0/system.html BitKeeper/deleted/.del-toc.html~670791f294a61494: Delete: bdb/docs/ref/upgrade.2.0/toc.html BitKeeper/deleted/.del-callback.html~64a2b2b85cc253c1: Delete: bdb/docs/ref/upgrade.3.2/callback.html BitKeeper/deleted/.del-db_dump.html~7d1cac3358c0482e: Delete: bdb/docs/ref/upgrade.3.2/db_dump.html BitKeeper/deleted/.del-handle.html~bb8a73b74d4399ae: Delete: bdb/docs/ref/upgrade.3.2/handle.html BitKeeper/deleted/.del-incomplete.html~af86a649a878a124: Delete: bdb/docs/ref/upgrade.3.2/incomplete.html BitKeeper/deleted/.del-intro.html~31e7055d83ca8757: Delete: bdb/docs/ref/log/intro.html BitKeeper/deleted/.del-limits.html~26fac1e32387b7c9: Delete: bdb/docs/ref/log/limits.html BitKeeper/deleted/.del-process.html~78f9ca966a587234: Delete: bdb/docs/ref/upgrade/process.html BitKeeper/deleted/.del-renumber.html~d6cd798434da81aa: Delete: bdb/docs/ref/upgrade.3.2/renumber.html BitKeeper/deleted/.del-disk.html~61799ebebe78ebb2: Delete: bdb/docs/ref/upgrade.3.2/disk.html BitKeeper/deleted/.del-intro.html~984a9f7dd07e0c14: Delete: bdb/docs/ref/upgrade.3.2/intro.html BitKeeper/deleted/.del-mutexlock.html~972b710c5bdba67c: Delete: bdb/docs/ref/upgrade.3.2/mutexlock.html BitKeeper/deleted/.del-notfound.html~dc91c094aba92838: Delete: bdb/docs/ref/upgrade.3.2/notfound.html BitKeeper/deleted/.del-set_flags.html~213809ca8d7802d0: Delete: bdb/docs/ref/upgrade.3.2/set_flags.html BitKeeper/deleted/.del-toc.html~9c94c533ada43c1a: Delete: bdb/docs/ref/upgrade.3.2/toc.html BitKeeper/deleted/.del-tx_recover.html~132a354cde7a8286: Delete: bdb/docs/ref/upgrade.3.2/tx_recover.html BitKeeper/deleted/.del-bdb_usenix.html~bad2247b4f8c582b: Delete: bdb/docs/ref/refs/bdb_usenix.html BitKeeper/deleted/.del-dbisnot.html~5ce7aed7ce41c9e6: Delete: bdb/docs/ref/intro/dbisnot.html BitKeeper/deleted/.del-embedded.html~d25b9719d24df88c: Delete: bdb/docs/ref/refs/embedded.html BitKeeper/deleted/.del-layout.html~5aeb292fbd987cf8: Delete: bdb/docs/ref/distrib/layout.html BitKeeper/deleted/.del-refs.html~30490b237ba9b61: Delete: bdb/docs/ref/refs/refs.html BitKeeper/deleted/.del-witold.html~ad6c866cf48734b5: Delete: bdb/docs/ref/refs/witold.html BitKeeper/deleted/.del-dbis.html~e672b7615d70be2c: Delete: bdb/docs/ref/intro/dbis.html BitKeeper/deleted/.del-need.html~43950806e35d71f: Delete: bdb/docs/ref/intro/need.html BitKeeper/deleted/.del-where.html~6cb9ec27f19ecbbb: Delete: bdb/docs/ref/intro/where.html BitKeeper/deleted/.del-data.html~33fbf7496c58cf63: Delete: bdb/docs/ref/intro/data.html BitKeeper/deleted/.del-dbinfo.html~7529af7145c0680a: Delete: bdb/docs/ref/upgrade.3.0/dbinfo.html BitKeeper/deleted/.del-distrib.html~84b56709310017f2: Delete: bdb/docs/ref/intro/distrib.html BitKeeper/deleted/.del-products.html~f37221772a3b589d: Delete: bdb/docs/ref/intro/products.html BitKeeper/deleted/.del-terrain.html~b396d6447a59435f: Delete: bdb/docs/ref/intro/terrain.html BitKeeper/deleted/.del-what.html~dd70b9e6e085725d: Delete: bdb/docs/ref/intro/what.html BitKeeper/deleted/.del-cxx.html~7f3bfc9bba854d48: Delete: bdb/docs/ref/upgrade.3.0/cxx.html BitKeeper/deleted/.del-eacces.html~f0299373d8b2f65c: Delete: bdb/docs/ref/upgrade.3.0/eacces.html BitKeeper/deleted/.del-jump_set.html~718c098a91db9dba: Delete: bdb/docs/ref/upgrade.3.0/jump_set.html BitKeeper/deleted/.del-lock_detect.html~fb307b10156762ca: Delete: bdb/docs/ref/upgrade.3.0/lock_detect.html BitKeeper/deleted/.del-txn_begin.html~53512180de5fec80: Delete: bdb/docs/ref/upgrade.3.0/txn_begin.html BitKeeper/deleted/.del-txn_commit.html~e1debf9ea769426c: Delete: bdb/docs/ref/upgrade.3.0/txn_commit.html BitKeeper/deleted/.del-xa.html~1af042e462ab829: Delete: bdb/docs/ref/upgrade.3.0/xa.html BitKeeper/deleted/.del-db_cxx.html~5c17d6a360205140: Delete: bdb/docs/ref/upgrade.3.0/db_cxx.html BitKeeper/deleted/.del-eagain.html~920800d8eb450f79: Delete: bdb/docs/ref/upgrade.3.0/eagain.html BitKeeper/deleted/.del-func.html~c06e5bc63ddf7a64: Delete: bdb/docs/ref/upgrade.3.0/func.html BitKeeper/deleted/.del-lock_notheld.html~ed6853b6daa5531b: Delete: bdb/docs/ref/upgrade.3.0/lock_notheld.html BitKeeper/deleted/.del-lock_put.html~fd9ed0b04b465af: Delete: bdb/docs/ref/upgrade.3.0/lock_put.html BitKeeper/deleted/.del-open.html~8b1e2a969e97069a: Delete: bdb/docs/ref/upgrade.3.0/open.html BitKeeper/deleted/.del-stat.html~775d75e3ba02d15c: Delete: bdb/docs/ref/upgrade.3.0/stat.html BitKeeper/deleted/.del-dbenv.html~f9863847dc1ed617: Delete: bdb/docs/ref/upgrade.3.0/dbenv.html BitKeeper/deleted/.del-dbenv_cxx.html~7f4fd0ebace36d8e: Delete: bdb/docs/ref/upgrade.3.0/dbenv_cxx.html BitKeeper/deleted/.del-envopen.html~5e768fd180f471e4: Delete: bdb/docs/ref/upgrade.3.0/envopen.html BitKeeper/deleted/.del-intro.html~7ecd16967b0bc868: Delete: bdb/docs/ref/upgrade.3.0/intro.html BitKeeper/deleted/.del-java.html~300acccbb633e335: Delete: bdb/docs/ref/upgrade.3.0/java.html BitKeeper/deleted/.del-join.html~ec21d874caa0654: Delete: bdb/docs/ref/upgrade.3.0/join.html BitKeeper/deleted/.del-close.html~c79c866b393785cc: Delete: bdb/docs/ref/upgrade.3.0/close.html BitKeeper/deleted/.del-disk.html~eb79d1157ef44d3c: Delete: bdb/docs/ref/upgrade.3.0/disk.html BitKeeper/deleted/.del-rmw.html~992b0143d13a3ec0: Delete: bdb/docs/ref/upgrade.3.0/rmw.html BitKeeper/deleted/.del-txn_stat.html~516f1870c6127351: Delete: bdb/docs/ref/upgrade.3.0/txn_stat.html BitKeeper/deleted/.del-lock_stat.html~c49716e693ce225b: Delete: bdb/docs/ref/upgrade.3.0/lock_stat.html BitKeeper/deleted/.del-log_register.html~399320e965adf598: Delete: bdb/docs/ref/upgrade.3.0/log_register.html BitKeeper/deleted/.del-log_stat.html~20b5898ba061557d: Delete: bdb/docs/ref/upgrade.3.0/log_stat.html BitKeeper/deleted/.del-memp_stat.html~79e1141c63f7357: Delete: bdb/docs/ref/upgrade.3.0/memp_stat.html BitKeeper/deleted/.del-toc.html~16e7d8e76496cbc9: Delete: bdb/docs/ref/upgrade.3.0/toc.html BitKeeper/deleted/.del-value_set.html~f0b0c770a81b90b6: Delete: bdb/docs/ref/upgrade.3.0/value_set.html BitKeeper/deleted/.del-cam_conv.html~63844ff6fa95f0c: Delete: bdb/docs/ref/lock/cam_conv.html BitKeeper/deleted/.del-config.html~a593ea4c87467ddd: Delete: bdb/docs/ref/lock/config.html BitKeeper/deleted/.del-db.html~e7d63f4bb8e989e8: Delete: bdb/docs/ref/upgrade.3.0/db.html BitKeeper/deleted/.del-max.html~f0fb32ebc251f636: Delete: bdb/docs/ref/lock/max.html BitKeeper/deleted/.del-notxn.html~beec805d9f05e2bc: Delete: bdb/docs/ref/lock/notxn.html BitKeeper/deleted/.del-twopl.html~b3f3aee667bc381d: Delete: bdb/docs/ref/lock/twopl.html BitKeeper/deleted/.del-am_conv.html~3bab32d969f21b77: Delete: bdb/docs/ref/lock/am_conv.html BitKeeper/deleted/.del-compat.html~b39d173789bbf70d: Delete: bdb/docs/ref/java/compat.html BitKeeper/deleted/.del-dead.html~f5c7debd9ba739bb: Delete: bdb/docs/ref/lock/dead.html BitKeeper/deleted/.del-faq.html~7ca2474ba1f6676f: Delete: bdb/docs/ref/java/faq.html BitKeeper/deleted/.del-intro.html~e1e07e71f3198be: Delete: bdb/docs/ref/lock/intro.html BitKeeper/deleted/.del-nondb.html~863fe076a46378d7: Delete: bdb/docs/ref/lock/nondb.html BitKeeper/deleted/.del-page.html~d56876b2565cbee: Delete: bdb/docs/ref/lock/page.html BitKeeper/deleted/.del-stdmode.html~4048a052ea129ca3: Delete: bdb/docs/ref/lock/stdmode.html BitKeeper/deleted/.del-conf.html~ef560bcf13a71cd5: Delete: bdb/docs/ref/java/conf.html BitKeeper/deleted/.del-faq.html~34704a907168cea7: Delete: bdb/docs/ref/build_win/faq.html BitKeeper/deleted/.del-intro.html~2975a07b53b12046: Delete: bdb/docs/ref/build_win/intro.html BitKeeper/deleted/.del-intro.html~4c497b1a18c4c7f5: Delete: bdb/docs/ref/cam/intro.html BitKeeper/deleted/.del-notes.html~4058bf968f287f7: Delete: bdb/docs/ref/build_win/notes.html BitKeeper/deleted/.del-program.html~e9bbc08bccf5d396: Delete: bdb/docs/ref/java/program.html BitKeeper/deleted/.del-test.html~84090b57cb7f0cf8: Delete: bdb/docs/ref/build_win/test.html BitKeeper/deleted/.del-byteorder.html~f7fa52b53e4c8838: Delete: bdb/docs/ref/program/byteorder.html BitKeeper/deleted/.del-extending.html~6a86a40872d6b8bc: Delete: bdb/docs/ref/program/extending.html BitKeeper/deleted/.del-format.html~9fa10ca3c7ae6751: Delete: bdb/docs/ref/dumpload/format.html BitKeeper/deleted/.del-text.html~88b57a73860b423: Delete: bdb/docs/ref/dumpload/text.html BitKeeper/deleted/.del-utility.html~8fc100fdb58adb3c: Delete: bdb/docs/ref/dumpload/utility.html BitKeeper/deleted/.del-appsignals.html~3ab63bf9399d7ead: Delete: bdb/docs/ref/program/appsignals.html BitKeeper/deleted/.del-diskspace.html~959508f155721ee8: Delete: bdb/docs/ref/program/diskspace.html BitKeeper/deleted/.del-environ.html~dc4a48aa531bd399: Delete: bdb/docs/ref/program/environ.html BitKeeper/deleted/.del-errorret.html~23491397d7e704e9: Delete: bdb/docs/ref/program/errorret.html BitKeeper/deleted/.del-scope.html~2987f97781410bc1: Delete: bdb/docs/ref/program/scope.html BitKeeper/deleted/.del-version.html~d266e819d1531df8: Delete: bdb/docs/ref/program/version.html BitKeeper/deleted/.del-compatible.html~237b98e6a6d7ed35: Delete: bdb/docs/ref/program/compatible.html BitKeeper/deleted/.del-copy.html~bcf5ff9656fafcd3: Delete: bdb/docs/ref/program/copy.html BitKeeper/deleted/.del-dbsizes.html~d70da530573b9b38: Delete: bdb/docs/ref/program/dbsizes.html BitKeeper/deleted/.del-mt.html~552ab570b657fc0e: Delete: bdb/docs/ref/program/mt.html BitKeeper/deleted/.del-namespace.html~182f8f762343bdc1: Delete: bdb/docs/ref/program/namespace.html BitKeeper/deleted/.del-recimp.html~bbdb0feb7d467a80: Delete: bdb/docs/ref/program/recimp.html BitKeeper/deleted/.del-runtime.html~6853fdbfe15df788: Delete: bdb/docs/ref/program/runtime.html BitKeeper/deleted/.del-common.html~607061232e2532df: Delete: bdb/docs/ref/debug/common.html BitKeeper/deleted/.del-compile.html~12785e3091b78bfd: Delete: bdb/docs/ref/debug/compile.html BitKeeper/deleted/.del-faq.html~cdb7646d3d2e6374: Delete: bdb/docs/ref/build_vxworks/faq.html BitKeeper/deleted/.del-intro.html~2eed15d25078711: Delete: bdb/docs/ref/build_vxworks/intro.html BitKeeper/deleted/.del-intro.html~57ef29f26341ea: Delete: bdb/docs/ref/debug/intro.html BitKeeper/deleted/.del-notes.html~7e53a042c5c4d350: Delete: bdb/docs/ref/build_vxworks/notes.html BitKeeper/deleted/.del-runtime.html~d50f2fea4a8e58c: Delete: bdb/docs/ref/debug/runtime.html BitKeeper/deleted/.del-config.html~771c2c91fc0b6b17: Delete: bdb/docs/ref/mp/config.html BitKeeper/deleted/.del-faq.html~f95038006d18229: Delete: bdb/docs/ref/test/faq.html BitKeeper/deleted/.del-file.html~d4ba2317db7c064b: Delete: bdb/docs/ref/install/file.html BitKeeper/deleted/.del-intro.html~34937731cafcf1b1: Delete: bdb/docs/ref/mp/intro.html BitKeeper/deleted/.del-printlog.html~9fa9894f839fad95: Delete: bdb/docs/ref/debug/printlog.html BitKeeper/deleted/.del-run.html~63c0398e7e2a29e2: Delete: bdb/docs/ref/test/run.html BitKeeper/deleted/.del-curdup.html~5c855e1f5b99d990: Delete: bdb/docs/ref/am/curdup.html BitKeeper/deleted/.del-curput.html~c7e4fa0a68170c3d: Delete: bdb/docs/ref/am/curput.html BitKeeper/deleted/.del-open.html~c9a7e23579a5e93a: Delete: bdb/docs/ref/am/open.html BitKeeper/deleted/.del-opensub.html~81c79cce793fb343: Delete: bdb/docs/ref/am/opensub.html BitKeeper/deleted/.del-stability.html~a92faac934d69cef: Delete: bdb/docs/ref/am/stability.html BitKeeper/deleted/.del-verify.html~badaeba91bda50e1: Delete: bdb/docs/ref/am/verify.html BitKeeper/deleted/.del-curclose.html~8b6b8442fc8382f7: Delete: bdb/docs/ref/am/curclose.html BitKeeper/deleted/.del-cursor.html~6dbcdb3b7d552f58: Delete: bdb/docs/ref/am/cursor.html BitKeeper/deleted/.del-delete.html~9195664374690b24: Delete: bdb/docs/ref/am/delete.html BitKeeper/deleted/.del-partial.html~db4a970c839b3051: Delete: bdb/docs/ref/am/partial.html BitKeeper/deleted/.del-stat.html~fafc0f88571d9395: Delete: bdb/docs/ref/am/stat.html BitKeeper/deleted/.del-count.html~8fd8daf2e2cbd7c7: Delete: bdb/docs/ref/am/count.html BitKeeper/deleted/.del-curget.html~d7dd42affcd54073: Delete: bdb/docs/ref/am/curget.html BitKeeper/deleted/.del-error.html~45ac854e68196844: Delete: bdb/docs/ref/am/error.html BitKeeper/deleted/.del-get.html~96c9c9a01c32d16: Delete: bdb/docs/ref/am/get.html BitKeeper/deleted/.del-join.html~acc16686a78a732: Delete: bdb/docs/ref/am/join.html BitKeeper/deleted/.del-sync.html~381722c07c9d8825: Delete: bdb/docs/ref/am/sync.html BitKeeper/deleted/.del-upgrade.html~c7499736f03c1a1c: Delete: bdb/docs/ref/am/upgrade.html BitKeeper/deleted/.del-close.html~ed6f7427edc0431: Delete: bdb/docs/ref/am/close.html BitKeeper/deleted/.del-curdel.html~39bf0a8cba99c064: Delete: bdb/docs/ref/am/curdel.html BitKeeper/deleted/.del-ops.html~9b24db9ba4f45724: Delete: bdb/docs/ref/am/ops.html BitKeeper/deleted/.del-put.html~8e18b0af61eb7f0f: Delete: bdb/docs/ref/am/put.html BitKeeper/deleted/.del-read.html~fc8b056380e09887: Delete: bdb/docs/ref/transapp/read.html BitKeeper/deleted/.del-term.html~d6f3fa4fc5a630ec: Delete: bdb/docs/ref/transapp/term.html BitKeeper/deleted/.del-app.html~6dc3c82982164fa8: Delete: bdb/docs/ref/transapp/app.html BitKeeper/deleted/.del-checkpoint.html~29e077c954369ed: Delete: bdb/docs/ref/transapp/checkpoint.html BitKeeper/deleted/.del-cursor.html~824b2f28c9e8d610: Delete: bdb/docs/ref/transapp/cursor.html BitKeeper/deleted/.del-deadlock.html~34914b9dc6b01703: Delete: bdb/docs/ref/transapp/deadlock.html BitKeeper/deleted/.del-env_open.html~c8d61102658c3bbf: Delete: bdb/docs/ref/transapp/env_open.html BitKeeper/deleted/.del-reclimit.html~5f54174bf6026bd5: Delete: bdb/docs/ref/transapp/reclimit.html BitKeeper/deleted/.del-archival.html~7631314d840be181: Delete: bdb/docs/ref/transapp/archival.html BitKeeper/deleted/.del-data_open.html~413c1d8aba9d8018: Delete: bdb/docs/ref/transapp/data_open.html BitKeeper/deleted/.del-filesys.html~ebee24f726f99bf6: Delete: bdb/docs/ref/transapp/filesys.html BitKeeper/deleted/.del-intro.html~22096cea9fe159ac: Delete: bdb/docs/ref/transapp/intro.html BitKeeper/deleted/.del-logfile.html~1c3002fcb6581e8c: Delete: bdb/docs/ref/transapp/logfile.html BitKeeper/deleted/.del-throughput.html~8a7d5a958df7f91a: Delete: bdb/docs/ref/transapp/throughput.html BitKeeper/deleted/.del-admin.html~cf867ed0b00cccef: Delete: bdb/docs/ref/transapp/admin.html BitKeeper/deleted/.del-inc.html~5ea32b4e2a2107b3: Delete: bdb/docs/ref/transapp/inc.html BitKeeper/deleted/.del-put.html~8cc785aeecff8535: Delete: bdb/docs/ref/transapp/put.html BitKeeper/deleted/.del-recovery.html~6e3a0c07b997c3b2: Delete: bdb/docs/ref/transapp/recovery.html BitKeeper/deleted/.del-why.html~c941c1a56a0adbaf: Delete: bdb/docs/ref/transapp/why.html BitKeeper/deleted/.del-error.html~37b817c57777b460: Delete: bdb/docs/ref/tcl/error.html BitKeeper/deleted/.del-faq.html~f8433900f7f85400: Delete: bdb/docs/ref/tcl/faq.html BitKeeper/deleted/.del-intro.html~d66c6c398e2ace0b: Delete: bdb/docs/ref/tcl/intro.html BitKeeper/deleted/.del-program.html~2f5bf497ae226ed5: Delete: bdb/docs/ref/tcl/program.html BitKeeper/deleted/.del-script.html~6796fd0a63161a0c: Delete: bdb/docs/ref/arch/script.html BitKeeper/deleted/.del-using.html~28856d8c72d0660b: Delete: bdb/docs/ref/tcl/using.html BitKeeper/deleted/.del-apis.html~a84570e410b11a6a: Delete: bdb/docs/ref/arch/apis.html BitKeeper/deleted/.del-bigpic.html~ab5254bc99af0d5c: Delete: bdb/docs/ref/arch/bigpic.html BitKeeper/deleted/.del-logalloc.html~30563c544b8ddd54: Delete: bdb/docs/ref/upgrade.3.1/logalloc.html BitKeeper/deleted/.del-progmodel.html~caa422dc155b6370: Delete: bdb/docs/ref/arch/progmodel.html BitKeeper/deleted/.del-set_paniccall.html~8f9741244fb6e9f6: Delete: bdb/docs/ref/upgrade.3.1/set_paniccall.html BitKeeper/deleted/.del-tcl.html~f5c85b09c33bda4: Delete: bdb/docs/ref/upgrade.3.1/tcl.html BitKeeper/deleted/.del-utilities.html~54d7014fab332c7a: Delete: bdb/docs/ref/arch/utilities.html BitKeeper/deleted/.del-btstat.html~40a76aef8b25a948: Delete: bdb/docs/ref/upgrade.3.1/btstat.html BitKeeper/deleted/.del-config.html~d2ace28f39ab0f8d: Delete: bdb/docs/ref/upgrade.3.1/config.html BitKeeper/deleted/.del-dup.html~911018877c118b45: Delete: bdb/docs/ref/upgrade.3.1/dup.html BitKeeper/deleted/.del-env.html~381e366a9c9c9a37: Delete: bdb/docs/ref/upgrade.3.1/env.html BitKeeper/deleted/.del-set_tx_recover.html~ada65907ba98eee8: Delete: bdb/docs/ref/upgrade.3.1/set_tx_recover.html BitKeeper/deleted/.del-tmp.html~ef3450f6fa89f2dc: Delete: bdb/docs/ref/upgrade.3.1/tmp.html BitKeeper/deleted/.del-disk.html~2abdaf9059265ba9: Delete: bdb/docs/ref/upgrade.3.1/disk.html BitKeeper/deleted/.del-intro.html~64592a50b1c634d6: Delete: bdb/docs/ref/upgrade.3.1/intro.html BitKeeper/deleted/.del-memp_register.html~7d92464a1029d53e: Delete: bdb/docs/ref/upgrade.3.1/memp_register.html BitKeeper/deleted/.del-put.html~961a1a689be6ce: Delete: bdb/docs/ref/upgrade.3.1/put.html BitKeeper/deleted/.del-set_feedback.html~6d7de50be92a5488: Delete: bdb/docs/ref/upgrade.3.1/set_feedback.html BitKeeper/deleted/.del-sysmem.html~3d088eb0ef1b27e0: Delete: bdb/docs/ref/upgrade.3.1/sysmem.html BitKeeper/deleted/.del-txn_check.html~2405b25bc92cc476: Delete: bdb/docs/ref/upgrade.3.1/txn_check.html BitKeeper/deleted/.del-intro.html~ce7e794e619e1e1d: Delete: bdb/docs/ref/perl/intro.html BitKeeper/deleted/.del-intro.html~ecac45d7e2bcf51c: Delete: bdb/docs/ref/sendmail/intro.html BitKeeper/deleted/.del-log_register.html~7177eeb2fc099317: Delete: bdb/docs/ref/upgrade.3.1/log_register.html BitKeeper/deleted/.del-toc.html~af1a24798980ad1: Delete: bdb/docs/ref/upgrade.3.1/toc.html BitKeeper/deleted/.del-config.html~3f3f449c305e66b4: Delete: bdb/docs/ref/xa/config.html BitKeeper/deleted/.del-faq.html~7aa890c7b70f1293: Delete: bdb/docs/ref/xa/faq.html BitKeeper/deleted/.del-intro.html~8ac020ffb869e9a8: Delete: bdb/docs/ref/xa/intro.html BitKeeper/deleted/.del-toc.html~ab1fa294d5ef4b69: Delete: bdb/docs/ref/toc.html BitKeeper/deleted/.del-del.html~514a1bd568ed4c1d: Delete: bdb/docs/ref/simple_tut/del.html BitKeeper/deleted/.del-errors.html~be11ff6410e1db2c: Delete: bdb/docs/ref/simple_tut/errors.html BitKeeper/deleted/.del-get.html~211de230d6a6cbc5: Delete: bdb/docs/ref/simple_tut/get.html BitKeeper/deleted/.del-intro.html~7544c4688623a54c: Delete: bdb/docs/ref/simple_tut/intro.html BitKeeper/deleted/.del-keydata.html~530b1581aeba63ca: Delete: bdb/docs/ref/simple_tut/keydata.html BitKeeper/deleted/.del-open.html~5d6eb5c3df68eeee: Delete: bdb/docs/ref/simple_tut/open.html BitKeeper/deleted/.del-client.html~824178f8626e45b7: Delete: bdb/docs/ref/rpc/client.html BitKeeper/deleted/.del-close.html~1fe3a82f28e7ed32: Delete: bdb/docs/ref/simple_tut/close.html BitKeeper/deleted/.del-handles.html~18a14f4a50e7bad0: Delete: bdb/docs/ref/simple_tut/handles.html BitKeeper/deleted/.del-intro.html~ad16bc20623e1192: Delete: bdb/docs/ref/rpc/intro.html BitKeeper/deleted/.del-put.html~bdd2629c212af471: Delete: bdb/docs/ref/simple_tut/put.html BitKeeper/deleted/.del-bt_compare.html~c1e847e651704c89: Delete: bdb/docs/ref/am_conf/bt_compare.html BitKeeper/deleted/.del-byteorder.html~999a22f727e2dae0: Delete: bdb/docs/ref/am_conf/byteorder.html BitKeeper/deleted/.del-h_ffactor.html~5eb87b7ce99f3362: Delete: bdb/docs/ref/am_conf/h_ffactor.html BitKeeper/deleted/.del-pagesize.html~eb4800704ae1131b: Delete: bdb/docs/ref/am_conf/pagesize.html BitKeeper/deleted/.del-recno.html~c2ae722138309e95: Delete: bdb/docs/ref/am_conf/recno.html BitKeeper/deleted/.del-server.html~79f560205494295: Delete: bdb/docs/ref/rpc/server.html BitKeeper/deleted/.del-cachesize.html~99dcd466dc881093: Delete: bdb/docs/ref/am_conf/cachesize.html BitKeeper/deleted/.del-dup.html~523731632fca7343: Delete: bdb/docs/ref/am_conf/dup.html BitKeeper/deleted/.del-h_nelem.html~979995db477052ad: Delete: bdb/docs/ref/am_conf/h_nelem.html BitKeeper/deleted/.del-malloc.html~cb0e6d7e9448d93e: Delete: bdb/docs/ref/am_conf/malloc.html BitKeeper/deleted/.del-renumber.html~b7df79bf32240b5c: Delete: bdb/docs/ref/am_conf/renumber.html BitKeeper/deleted/.del-select.html~57b1c99f6a8ea93f: Delete: bdb/docs/ref/am_conf/select.html BitKeeper/deleted/.del-bt_recnum.html~f081f10254e86e75: Delete: bdb/docs/ref/am_conf/bt_recnum.html BitKeeper/deleted/.del-intro.html~dd1647202258ee28: Delete: bdb/docs/ref/am_conf/intro.html BitKeeper/deleted/.del-logrec.html~5edeb34d63936e2: Delete: bdb/docs/ref/am_conf/logrec.html BitKeeper/deleted/.del-bt_minkey.html~b4708e561be92b83: Delete: bdb/docs/ref/am_conf/bt_minkey.html BitKeeper/deleted/.del-bt_prefix.html~4e7602aa68d50fe1: Delete: bdb/docs/ref/am_conf/bt_prefix.html BitKeeper/deleted/.del-db_set_h_hash.html~c6eb825c706a9548: Delete: bdb/docs/api_java/db_set_h_hash.html BitKeeper/deleted/.del-extentsize.html~fdcfb5572974545c: Delete: bdb/docs/ref/am_conf/extentsize.html BitKeeper/deleted/.del-h_hash.html~3a0174586fbcfcdf: Delete: bdb/docs/ref/am_conf/h_hash.html BitKeeper/deleted/.del-re_source.html~b000d11ca4a0f9a: Delete: bdb/docs/ref/am_conf/re_source.html BitKeeper/deleted/.del-dbc_close.html~e3bf1f36bc0e8e7e: Delete: bdb/docs/api_java/dbc_close.html BitKeeper/deleted/.del-env_close.html~c4e2ec77d7d14d4f: Delete: bdb/docs/api_java/env_close.html BitKeeper/deleted/.del-env_set_feedback.html~9748745e65f070d5: Delete: bdb/docs/api_java/env_set_feedback.html BitKeeper/deleted/.del-env_set_lk_detect.html~9fc15a1a95b0dfa1: Delete: bdb/docs/api_java/env_set_lk_detect.html BitKeeper/deleted/.del-lock_vec.html~df5eb838fdbe1eab: Delete: bdb/docs/api_java/lock_vec.html BitKeeper/deleted/.del-log_file.html~74a49bae2532199a: Delete: bdb/docs/api_java/log_file.html BitKeeper/deleted/.del-db_set_bt_prefix.html~a3269aad23e6dbc: Delete: bdb/docs/api_java/db_set_bt_prefix.html BitKeeper/deleted/.del-db_sync.html~42391f7d5f200b90: Delete: bdb/docs/api_java/db_sync.html BitKeeper/deleted/.del-env_set_errcall.html~4e206d08cbb39ab7: Delete: bdb/docs/api_java/env_set_errcall.html BitKeeper/deleted/.del-log_archive.html~b4a9483dbb5a2b58: Delete: bdb/docs/api_java/log_archive.html BitKeeper/deleted/.del-memp_trickle.html~4d5c4e83a4a5c638: Delete: bdb/docs/api_java/memp_trickle.html BitKeeper/deleted/.del-db_key_range.html~8834de5873a6acb5: Delete: bdb/docs/api_java/db_key_range.html BitKeeper/deleted/.del-db_set_errpfx.html~c446da51277796df: Delete: bdb/docs/api_java/db_set_errpfx.html BitKeeper/deleted/.del-except_class.html~195c00e4a7cbe648: Delete: bdb/docs/api_java/except_class.html BitKeeper/deleted/.del-log_get.html~5fbbbd4baa60e052: Delete: bdb/docs/api_java/log_get.html BitKeeper/deleted/.del-txn_begin.html~553bf78bd7fc3e0a: Delete: bdb/docs/api_java/txn_begin.html BitKeeper/deleted/.del-txn_commit.html~c265042f3340baa1: Delete: bdb/docs/api_java/txn_commit.html BitKeeper/deleted/.del-db_set_bt_minkey.html~c7e1f184bdca25fa: Delete: bdb/docs/api_java/db_set_bt_minkey.html BitKeeper/deleted/.del-db_set_cachesize.html~22d172a2d29f276b: Delete: bdb/docs/api_java/db_set_cachesize.html BitKeeper/deleted/.del-db_set_re_len.html~8448826ea78c630e: Delete: bdb/docs/api_java/db_set_re_len.html BitKeeper/deleted/.del-env_set_flags.html~690847bb5e205c21: Delete: bdb/docs/api_java/env_set_flags.html BitKeeper/deleted/.del-lock_detect.html~14d4e7c7dca0dad7: Delete: bdb/docs/api_java/lock_detect.html BitKeeper/deleted/.del-db_get.html~87b8316c55b24739: Delete: bdb/docs/api_java/db_get.html BitKeeper/deleted/.del-db_get_type.html~4cfb6f09cbe0b8ae: Delete: bdb/docs/api_java/db_get_type.html BitKeeper/deleted/.del-db_set_re_source.html~b29827dbf47537d1: Delete: bdb/docs/api_java/db_set_re_source.html BitKeeper/deleted/.del-dbc_dup.html~aa141014c4d7f9b0: Delete: bdb/docs/api_java/dbc_dup.html BitKeeper/deleted/.del-env_open.html~2df0f0ef544da715: Delete: bdb/docs/api_java/env_open.html BitKeeper/deleted/.del-txn_abort.html~ec9a3517748bfa3: Delete: bdb/docs/api_java/txn_abort.html BitKeeper/deleted/.del-dbt_class.html~f6b04ff142e332f8: Delete: bdb/docs/api_java/dbt_class.html BitKeeper/deleted/.del-deadlock_class.html~b587b2d8c9e5d0b0: Delete: bdb/docs/api_java/deadlock_class.html BitKeeper/deleted/.del-env_set_lg_dir.html~484cad2123994e14: Delete: bdb/docs/api_java/env_set_lg_dir.html BitKeeper/deleted/.del-lock_id.html~737cf8d8dc74084e: Delete: bdb/docs/api_java/lock_id.html BitKeeper/deleted/.del-db_put.html~c476abe5599f21cf: Delete: bdb/docs/api_java/db_put.html BitKeeper/deleted/.del-db_set_append_recno.html~d28bf857803b93a2: Delete: bdb/docs/api_java/db_set_append_recno.html BitKeeper/deleted/.del-db_set_feedback.html~69b4c07b3dbe383: Delete: bdb/docs/api_java/db_set_feedback.html BitKeeper/deleted/.del-db_upgrade.html~782fa4cc6c633990: Delete: bdb/docs/api_java/db_upgrade.html BitKeeper/deleted/.del-dbenv_class.html~92c7a4a6c22090c7: Delete: bdb/docs/api_java/dbenv_class.html BitKeeper/deleted/.del-env_set_lk_max.html~12b6e34ac5a53281: Delete: bdb/docs/api_java/env_set_lk_max.html BitKeeper/deleted/.del-mem_class.html~2e5052b5b2bea584: Delete: bdb/docs/api_java/mem_class.html BitKeeper/deleted/.del-db_close.html~21595167f4fdbe88: Delete: bdb/docs/api_java/db_close.html BitKeeper/deleted/.del-db_set_bt_compare.html~e972f964d042b35e: Delete: bdb/docs/api_java/db_set_bt_compare.html BitKeeper/deleted/.del-db_set_flags.html~b6b9d271bd42a94e: Delete: bdb/docs/api_java/db_set_flags.html BitKeeper/deleted/.del-env_set_lk_conflicts.html~8951eb975a90918b: Delete: bdb/docs/api_java/env_set_lk_conflicts.html BitKeeper/deleted/.del-get_errno.html~89a89f8efe3a9360: Delete: bdb/docs/api_java/get_errno.html BitKeeper/deleted/.del-db_open.html~bfc13736b96ac509: Delete: bdb/docs/api_java/db_open.html BitKeeper/deleted/.del-db_set_q_extentsize.html~6ac26239fc538cb: Delete: bdb/docs/api_java/db_set_q_extentsize.html BitKeeper/deleted/.del-dbc_get.html~e66e387b83681e73: Delete: bdb/docs/api_java/dbc_get.html BitKeeper/deleted/.del-env_version.html~854d26806930cab6: Delete: bdb/docs/api_java/env_version.html BitKeeper/deleted/.del-txn_id.html~798720b73cc9391: Delete: bdb/docs/api_java/txn_id.html BitKeeper/deleted/.del-db_rename.html~19b20feaa815bc27: Delete: bdb/docs/api_java/db_rename.html BitKeeper/deleted/.del-db_set_lorder.html~f64cbdd62bbbdd7c: Delete: bdb/docs/api_java/db_set_lorder.html BitKeeper/deleted/.del-env_set_mutexlocks.html~aad8e4a059075bb6: Delete: bdb/docs/api_java/env_set_mutexlocks.html BitKeeper/deleted/.del-lock_put.html~5af89e4cbf29c694: Delete: bdb/docs/api_java/lock_put.html BitKeeper/deleted/.del-memp_sync.html~5b401daadc7261eb: Delete: bdb/docs/api_java/memp_sync.html BitKeeper/deleted/.del-env_remove.html~e92277e3dfd9bba1: Delete: bdb/docs/api_java/env_remove.html BitKeeper/deleted/.del-env_set_errpfx.html~a3b9a09670f6912: Delete: bdb/docs/api_java/env_set_errpfx.html BitKeeper/deleted/.del-env_set_tas_spins.html~2f9963827fbcb3f: Delete: bdb/docs/api_java/env_set_tas_spins.html BitKeeper/deleted/.del-log_put.html~ad7e9f382abde491: Delete: bdb/docs/api_java/log_put.html BitKeeper/deleted/.del-lsn_class.html~b1458208b6c81016: Delete: bdb/docs/api_java/lsn_class.html BitKeeper/deleted/.del-memp_fput.html~6ba75e517a259703: Delete: bdb/docs/api_java/memp_fput.html BitKeeper/deleted/.del-memp_fset.html~5c5371a93b83275: Delete: bdb/docs/api_java/memp_fset.html BitKeeper/deleted/.del-db_class.html~b957a4d2b77acb1e: Delete: bdb/docs/api_java/db_class.html BitKeeper/deleted/.del-db_remove.html~49d3b8c7e5a5b000: Delete: bdb/docs/api_java/db_remove.html BitKeeper/deleted/.del-db_set_h_ffactor.html~edcc10024104d57e: Delete: bdb/docs/api_java/db_set_h_ffactor.html BitKeeper/deleted/.del-env_set_lg_max.html~c9f705492162e175: Delete: bdb/docs/api_java/env_set_lg_max.html BitKeeper/deleted/.del-txn_class.html~c7bb2a3393ca9488: Delete: bdb/docs/api_java/txn_class.html BitKeeper/deleted/.del-db_set_re_delim.html~78fcf2d750fb26ef: Delete: bdb/docs/api_java/db_set_re_delim.html BitKeeper/deleted/.del-db_verify.html~20873ab17f6ed922: Delete: bdb/docs/api_java/db_verify.html BitKeeper/deleted/.del-env_set_lk_max_objects.html~d1ed194631ffeb2a: Delete: bdb/docs/api_java/env_set_lk_max_objects.html BitKeeper/deleted/.del-env_set_region_init.html~30534afa94cbf54e: Delete: bdb/docs/api_java/env_set_region_init.html BitKeeper/deleted/.del-java_pindex.html~f8bc0811d8eda8e9: Delete: bdb/docs/api_java/java_pindex.html BitKeeper/deleted/.del-memp_register.html~8331390a1c66fefd: Delete: bdb/docs/api_java/memp_register.html BitKeeper/deleted/.del-db_join.html~a3a6dead9cae65f9: Delete: bdb/docs/api_java/db_join.html BitKeeper/deleted/.del-db_set_re_pad.html~2729c192747ac7af: Delete: bdb/docs/api_java/db_set_re_pad.html BitKeeper/deleted/.del-dbc_class.html~8ee03c40ae0dbcb8: Delete: bdb/docs/api_java/dbc_class.html BitKeeper/deleted/.del-env_strerror.html~fceebaa94cf9aafd: Delete: bdb/docs/api_java/env_strerror.html BitKeeper/deleted/.del-txn_checkpoint.html~2565ac892d04b63d: Delete: bdb/docs/api_java/txn_checkpoint.html BitKeeper/deleted/.del-db_set_dup_compare.html~3dabd840a1d9e5f3: Delete: bdb/docs/api_java/db_set_dup_compare.html BitKeeper/deleted/.del-db_set_h_nelem.html~fc6f22a4c285fcef: Delete: bdb/docs/api_java/db_set_h_nelem.html BitKeeper/deleted/.del-env_set_rec_init.html~1fdb2c5fc3b6407: Delete: bdb/docs/api_java/env_set_rec_init.html BitKeeper/deleted/.del-memp_fget.html~ca84dee01997eb89: Delete: bdb/docs/api_java/memp_fget.html BitKeeper/deleted/.del-db_fd.html~1f70020c37023baa: Delete: bdb/docs/api_java/db_fd.html BitKeeper/deleted/.del-db_stat.html~bc253f0883e9c82b: Delete: bdb/docs/api_java/db_stat.html BitKeeper/deleted/.del-env_set_cachesize.html~f3700cd19856f14e: Delete: bdb/docs/api_java/env_set_cachesize.html BitKeeper/deleted/.del-env_set_lg_bsize.html~6c67beed877df84c: Delete: bdb/docs/api_java/env_set_lg_bsize.html BitKeeper/deleted/.del-env_set_server.html~d901cdab9698605d: Delete: bdb/docs/api_java/env_set_server.html BitKeeper/deleted/.del-memp_fopen.html~f7cf58725aa1c406: Delete: bdb/docs/api_java/memp_fopen.html BitKeeper/deleted/.del-dbc_count.html~9c239575f4550756: Delete: bdb/docs/api_java/dbc_count.html BitKeeper/deleted/.del-env_set_tmp_dir.html~f23e4f614f6d975a: Delete: bdb/docs/api_java/env_set_tmp_dir.html BitKeeper/deleted/.del-java_index.html~8ecfcef4a702011d: Delete: bdb/docs/api_java/java_index.html BitKeeper/deleted/.del-lock_get.html~fd52de261831f9b5: Delete: bdb/docs/api_java/lock_get.html BitKeeper/deleted/.del-memp_fclose.html~d08f0c134361f802: Delete: bdb/docs/api_java/memp_fclose.html BitKeeper/deleted/.del-db_get_byteswapped.html~edbc66a9d5491a1: Delete: bdb/docs/api_java/db_get_byteswapped.html BitKeeper/deleted/.del-dbc_del.html~6ec2b8a4b8dde996: Delete: bdb/docs/api_java/dbc_del.html BitKeeper/deleted/.del-env_set_lk_max_lockers.html~7896265ea77829b3: Delete: bdb/docs/api_java/env_set_lk_max_lockers.html BitKeeper/deleted/.del-env_set_tx_timestamp.html~457eeb135f1f8bc0: Delete: bdb/docs/api_java/env_set_tx_timestamp.html BitKeeper/deleted/.del-log_unregister.html~eee284e0da176d0a: Delete: bdb/docs/api_java/log_unregister.html BitKeeper/deleted/.del-txn_stat.html~9a6ef8c262f218f9: Delete: bdb/docs/api_java/txn_stat.html BitKeeper/deleted/.del-db_cursor.html~2181d652bd1c1ff: Delete: bdb/docs/api_java/db_cursor.html BitKeeper/deleted/.del-db_set_errcall.html~4e4743f5b4277199: Delete: bdb/docs/api_java/db_set_errcall.html BitKeeper/deleted/.del-env_set_mp_mmapsize.html~b7dea9108fa65dfa: Delete: bdb/docs/api_java/env_set_mp_mmapsize.html BitKeeper/deleted/.del-env_set_tx_recover.html~40280da113fc9d2b: Delete: bdb/docs/api_java/env_set_tx_recover.html BitKeeper/deleted/.del-lock_class.html~880aa614d1469304: Delete: bdb/docs/api_java/lock_class.html BitKeeper/deleted/.del-txn_prepare.html~510a245c80e715c: Delete: bdb/docs/api_java/txn_prepare.html BitKeeper/deleted/.del-env_set_lk_max_locks.html~f0114205b169de39: Delete: bdb/docs/api_java/env_set_lk_max_locks.html BitKeeper/deleted/.del-log_compare.html~756622b42572ecb: Delete: bdb/docs/api_java/log_compare.html BitKeeper/deleted/.del-log_stat.html~d186a08662046aba: Delete: bdb/docs/api_java/log_stat.html BitKeeper/deleted/.del-memp_stat.html~4628462474db62b4: Delete: bdb/docs/api_java/memp_stat.html BitKeeper/deleted/.del-runrec_class.html~49c5cb3efe0c201: Delete: bdb/docs/api_java/runrec_class.html BitKeeper/deleted/.del-db_del.html~f4f15b362b114506: Delete: bdb/docs/api_java/db_del.html BitKeeper/deleted/.del-dbc_put.html~da0f0fa974385abd: Delete: bdb/docs/api_java/dbc_put.html BitKeeper/deleted/.del-env_set_pageyield.html~774b3da0306a6767: Delete: bdb/docs/api_java/env_set_pageyield.html BitKeeper/deleted/.del-env_set_shm_key.html~8c576698882f0edc: Delete: bdb/docs/api_java/env_set_shm_key.html BitKeeper/deleted/.del-log_register.html~c68fc6fb22dd594a: Delete: bdb/docs/api_java/log_register.html BitKeeper/deleted/.del-memp_fsync.html~e767b233fe7730a2: Delete: bdb/docs/api_java/memp_fsync.html BitKeeper/deleted/.del-db_set_pagesize.html~d899ea90b20b7b31: Delete: bdb/docs/api_java/db_set_pagesize.html BitKeeper/deleted/.del-env_set_error_stream.html~a738119910b452b8: Delete: bdb/docs/api_java/env_set_error_stream.html BitKeeper/deleted/.del-env_set_panicstate.html~72846d9a97cb80bb: Delete: bdb/docs/api_java/env_set_panicstate.html BitKeeper/deleted/.del-env_set_tx_max.html~70f356b8b67782fe: Delete: bdb/docs/api_java/env_set_tx_max.html BitKeeper/deleted/.del-lock_stat.html~71b81d8567befc43: Delete: bdb/docs/api_java/lock_stat.html BitKeeper/deleted/.del-log_flush.html~1691d6a3c8cc284e: Delete: bdb/docs/api_java/log_flush.html BitKeeper/deleted/.del-db_sync.html~3b615ca64d934602: Delete: bdb/docs/api_tcl/db_sync.html BitKeeper/deleted/.del-dbc_close.html~ef431e58d72accc3: Delete: bdb/docs/api_tcl/dbc_close.html BitKeeper/deleted/.del-env_close.html~bf191b2673a2b19e: Delete: bdb/docs/api_tcl/env_close.html BitKeeper/deleted/.del-env_set_data_dir.html~b7b3f35e96804650: Delete: bdb/docs/api_java/env_set_data_dir.html BitKeeper/deleted/.del-env_set_verbose.html~9dcda0399c8256e7: Delete: bdb/docs/api_java/env_set_verbose.html BitKeeper/deleted/.del-db_get.html~127bd361ee695c71: Delete: bdb/docs/api_tcl/db_get.html BitKeeper/deleted/.del-dbc_dup.html~325121689412d70b: Delete: bdb/docs/api_tcl/dbc_dup.html BitKeeper/deleted/.del-txn_abort.html~8cc23b6ef6f457d2: Delete: bdb/docs/api_tcl/txn_abort.html BitKeeper/deleted/.del-txn_commit.html~25150b20b84cd519: Delete: bdb/docs/api_tcl/txn_commit.html BitKeeper/deleted/.del-version.html~eeb51f4de1bbfe8e: Delete: bdb/docs/api_tcl/version.html BitKeeper/deleted/.del-db_get_join.html~1c737805c2c49cf9: Delete: bdb/docs/api_tcl/db_get_join.html BitKeeper/deleted/.del-db_get_type.html~7202f3ca793e6ec3: Delete: bdb/docs/api_tcl/db_get_type.html BitKeeper/deleted/.del-db_put.html~380c7caeced55512: Delete: bdb/docs/api_tcl/db_put.html BitKeeper/deleted/.del-env_open.html~39b63925d45a637e: Delete: bdb/docs/api_tcl/env_open.html BitKeeper/deleted/.del-tcl_index.html~443e6b9a10ef4139: Delete: bdb/docs/api_tcl/tcl_index.html BitKeeper/deleted/.del-db_close.html~f40794b17e0fe443: Delete: bdb/docs/api_tcl/db_close.html BitKeeper/deleted/.del-db_is_byteswapped.html~8fb9e2c58051c769: Delete: bdb/docs/api_tcl/db_is_byteswapped.html BitKeeper/deleted/.del-db_open.html~f588cc9bc694cbf0: Delete: bdb/docs/api_tcl/db_open.html BitKeeper/deleted/.del-dbc_get.html~5bbb80cf51aff594: Delete: bdb/docs/api_tcl/dbc_get.html BitKeeper/deleted/.del-db_count.html~4812f3756a75437: Delete: bdb/docs/api_tcl/db_count.html BitKeeper/deleted/.del-db_join.html~cb3eb61ed17a1f8: Delete: bdb/docs/api_tcl/db_join.html BitKeeper/deleted/.del-db_remove.html~3b2be4b0b1b3dc98: Delete: bdb/docs/api_tcl/db_remove.html BitKeeper/deleted/.del-db_rename.html~909bc643d5455b54: Delete: bdb/docs/api_tcl/db_rename.html BitKeeper/deleted/.del-db_stat.html~3bb57be2de907fd2: Delete: bdb/docs/api_tcl/db_stat.html BitKeeper/deleted/.del-env_remove.html~9090900413ff0280: Delete: bdb/docs/api_tcl/env_remove.html BitKeeper/deleted/.del-db_cursor.html~e035b3c11a91c5d6: Delete: bdb/docs/api_tcl/db_cursor.html BitKeeper/deleted/.del-db_del.html~400c7a72fb10d6f4: Delete: bdb/docs/api_tcl/db_del.html BitKeeper/deleted/.del-dbc_del.html~7e94f9f01e7e4453: Delete: bdb/docs/api_tcl/dbc_del.html BitKeeper/deleted/.del-dbc_put.html~290ecb1275d4270: Delete: bdb/docs/api_tcl/dbc_put.html BitKeeper/deleted/.del-tcl_pindex.html~259f0e062eee63c7: Delete: bdb/docs/api_tcl/tcl_pindex.html BitKeeper/deleted/.del-db_checkpoint.html~c040e4424edcc451: Delete: bdb/docs/utility/db_checkpoint.html BitKeeper/deleted/.del-db_deadlock.html~f23f99911c3e5784: Delete: bdb/docs/utility/db_deadlock.html BitKeeper/deleted/.del-db_printlog.html~fcc4075ad0232842: Delete: bdb/docs/utility/db_printlog.html BitKeeper/deleted/.del-index.html~66c82ee036c1b369: Delete: bdb/docs/utility/index.html BitKeeper/deleted/.del-txn.html~8e345950e6029230: Delete: bdb/docs/api_tcl/txn.html BitKeeper/deleted/.del-db_archive.html~ab2c66e01b3e3626: Delete: bdb/docs/utility/db_archive.html BitKeeper/deleted/.del-db_dump.html~5de7ade427f20332: Delete: bdb/docs/utility/db_dump.html BitKeeper/deleted/.del-db_recover.html~1b63f2acdc0b0af7: Delete: bdb/docs/utility/db_recover.html BitKeeper/deleted/.del-db_stat.html~9582c327964e1f9: Delete: bdb/docs/utility/db_stat.html BitKeeper/deleted/.del-db_upgrade.html~6444f26a93f77ea: Delete: bdb/docs/utility/db_upgrade.html BitKeeper/deleted/.del-db_verify.html~4fee9bfa2f9ab41a: Delete: bdb/docs/utility/db_verify.html BitKeeper/deleted/.del-berkeley_db_svc.html~91fe012778882ce4: Delete: bdb/docs/utility/berkeley_db_svc.html BitKeeper/deleted/.del-db_load.html~981095940db0197: Delete: bdb/docs/utility/db_load.html BitKeeper/deleted/.del-pindex.src~7d74723f9fd25801: Delete: bdb/docs/ref/pindex.src BitKeeper/deleted/.del-pindex.src~d1ecd116c42e0e23: Delete: bdb/docs/api_c/pindex.src BitKeeper/deleted/.del-pindex.src~d65361c4acfcef06: Delete: bdb/docs/api_cxx/pindex.src BitKeeper/deleted/.del-pindex.src~de828917f041d27b: Delete: bdb/docs/api_java/pindex.src BitKeeper/deleted/.del-pindex.src~f8754fff24f2cb24: Delete: bdb/docs/api_tcl/pindex.src BitKeeper/deleted/.del-api.gif~dec2d4fe5f39dffe: Delete: bdb/docs/images/api.gif BitKeeper/deleted/.del-next.gif~ddab96466674135b: Delete: bdb/docs/images/next.gif BitKeeper/deleted/.del-prev.gif~9448d24755d708a0: Delete: bdb/docs/images/prev.gif BitKeeper/deleted/.del-ps.gif~f6b1b372cb2cda4c: Delete: bdb/docs/images/ps.gif BitKeeper/deleted/.del-ref.gif~add30c753dc1972d: Delete: bdb/docs/images/ref.gif BitKeeper/deleted/.del-sleepycat.gif~ea63aaaa508ef096: Delete: bdb/docs/images/sleepycat.gif BitKeeper/deleted/.del-bdb_usenix.ps~9851f6cdeff17481: Delete: bdb/docs/ref/refs/bdb_usenix.ps BitKeeper/deleted/.del-hash_usenix.ps~11cad226b0aa012b: Delete: bdb/docs/ref/refs/hash_usenix.ps BitKeeper/deleted/.del-libtp_usenix.ps~73329b041f7e8c41: Delete: bdb/docs/ref/refs/libtp_usenix.ps BitKeeper/deleted/.del-bigpic.gif~fe43e7415b3bbdb0: Delete: bdb/docs/ref/arch/bigpic.gif BitKeeper/deleted/.del-smallpic.gif~fdf77055d7e711: Delete: bdb/docs/ref/arch/smallpic.gif BitKeeper/deleted/.del-magic.s5.be.txt~cf7d25e758432ab6: Delete: bdb/docs/ref/install/magic.s5.be.txt BitKeeper/deleted/.del-magic.s5.le.txt~528ef76418c8b45c: Delete: bdb/docs/ref/install/magic.s5.le.txt BitKeeper/deleted/.del-example.txt~9ff88f22565208bf: Delete: bdb/docs/ref/simple_tut/example.txt BitKeeper/deleted/.del-magic.txt~3894a46ea11ce25a: Delete: bdb/docs/ref/install/magic.txt BitKeeper/deleted/.del-solaris.txt~8b6bb29de0d58ffe: Delete: bdb/docs/ref/program/solaris.txt BitKeeper/deleted/.del-transapp.txt~337576ea2aae23b0: Delete: bdb/docs/ref/transapp/transapp.txt BitKeeper/deleted/.del-writetest.txt~4de1fc39894cd760: Delete: bdb/docs/ref/transapp/writetest.txt BitKeeper/deleted/.del-pg++~3beac0502025d766: Delete: mit-pthreads/pg++ BitKeeper/deleted/.del-pgcc~154a03d0c1a0a600: Delete: mit-pthreads/pgcc bdb/Makefile.in: Remove docs from the distribution (copyright problem) mit-pthreads/Changes-mysql: Hack to get MIT-pthreads to compile with glibc 2.2 mit-pthreads/GNUmakefile: Hack to get MIT-pthreads to compile with glibc 2.2 mit-pthreads/include/pthread/ac-types.h: Hack to get MIT-pthreads to compile with glibc 2.2 mit-pthreads/include/pthread/paths.h: Hack to get MIT-pthreads to compile with glibc 2.2 mit-pthreads/machdep/engine-i386-linux-2.0.h: Hack to get MIT-pthreads to compile with glibc 2.2 mit-pthreads/machdep/linux-2.0/__signal.h: Hack to get MIT-pthreads to compile with glibc 2.2 mit-pthreads/machdep/linux-2.0/__stdio.h: Hack to get MIT-pthreads to compile with glibc 2.2 mit-pthreads/machdep/linux-2.0/extra/bits/socket.h: Hack to get MIT-pthreads to compile with glibc 2.2 mit-pthreads/machdep/linux-2.0/socket.h: Hack to get MIT-pthreads to compile with glibc 2.2 BitKeeper/etc/ignore: Added mit-pthreads/syscall.S to the ignore list BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted --- bdb/docs/api_c/c_index.html | 172 ---------- bdb/docs/api_c/c_pindex.html | 530 ----------------------------- bdb/docs/api_c/db_close.html | 119 ------- bdb/docs/api_c/db_create.html | 107 ------ bdb/docs/api_c/db_cursor.html | 103 ------ bdb/docs/api_c/db_del.html | 101 ------ bdb/docs/api_c/db_err.html | 93 ----- bdb/docs/api_c/db_fd.html | 92 ----- bdb/docs/api_c/db_get.html | 156 --------- bdb/docs/api_c/db_get_byteswapped.html | 84 ----- bdb/docs/api_c/db_get_type.html | 81 ----- bdb/docs/api_c/db_join.html | 151 -------- bdb/docs/api_c/db_key_range.html | 106 ------ bdb/docs/api_c/db_lsn.html | 36 -- bdb/docs/api_c/db_open.html | 182 ---------- bdb/docs/api_c/db_put.html | 136 -------- bdb/docs/api_c/db_remove.html | 108 ------ bdb/docs/api_c/db_rename.html | 109 ------ bdb/docs/api_c/db_set_append_recno.html | 66 ---- bdb/docs/api_c/db_set_bt_compare.html | 105 ------ bdb/docs/api_c/db_set_bt_minkey.html | 92 ----- bdb/docs/api_c/db_set_bt_prefix.html | 106 ------ bdb/docs/api_c/db_set_cachesize.html | 107 ------ bdb/docs/api_c/db_set_dup_compare.html | 102 ------ bdb/docs/api_c/db_set_errcall.html | 76 ----- bdb/docs/api_c/db_set_errfile.html | 73 ---- bdb/docs/api_c/db_set_errpfx.html | 62 ---- bdb/docs/api_c/db_set_feedback.html | 95 ------ bdb/docs/api_c/db_set_flags.html | 181 ---------- bdb/docs/api_c/db_set_h_ffactor.html | 93 ----- bdb/docs/api_c/db_set_h_hash.html | 97 ------ bdb/docs/api_c/db_set_h_nelem.html | 88 ----- bdb/docs/api_c/db_set_lorder.html | 94 ----- bdb/docs/api_c/db_set_malloc.html | 98 ------ bdb/docs/api_c/db_set_pagesize.html | 90 ----- bdb/docs/api_c/db_set_paniccall.html | 70 ---- bdb/docs/api_c/db_set_q_extentsize.html | 90 ----- bdb/docs/api_c/db_set_re_delim.html | 90 ----- bdb/docs/api_c/db_set_re_len.html | 94 ----- bdb/docs/api_c/db_set_re_pad.html | 88 ----- bdb/docs/api_c/db_set_re_source.html | 130 ------- bdb/docs/api_c/db_set_realloc.html | 99 ------ bdb/docs/api_c/db_stat.html | 195 ----------- bdb/docs/api_c/db_sync.html | 98 ------ bdb/docs/api_c/db_upgrade.html | 135 -------- bdb/docs/api_c/db_verify.html | 150 -------- bdb/docs/api_c/dbc_close.html | 64 ---- bdb/docs/api_c/dbc_count.html | 55 --- bdb/docs/api_c/dbc_del.html | 68 ---- bdb/docs/api_c/dbc_dup.html | 72 ---- bdb/docs/api_c/dbc_get.html | 167 --------- bdb/docs/api_c/dbc_put.html | 154 --------- bdb/docs/api_c/dbm.html | 220 ------------ bdb/docs/api_c/dbt.html | 158 --------- bdb/docs/api_c/env_close.html | 84 ----- bdb/docs/api_c/env_create.html | 74 ---- bdb/docs/api_c/env_open.html | 205 ----------- bdb/docs/api_c/env_remove.html | 125 ------- bdb/docs/api_c/env_set_cachesize.html | 87 ----- bdb/docs/api_c/env_set_data_dir.html | 77 ----- bdb/docs/api_c/env_set_errcall.html | 73 ---- bdb/docs/api_c/env_set_errfile.html | 70 ---- bdb/docs/api_c/env_set_errpfx.html | 59 ---- bdb/docs/api_c/env_set_feedback.html | 69 ---- bdb/docs/api_c/env_set_flags.html | 84 ----- bdb/docs/api_c/env_set_lg_bsize.html | 68 ---- bdb/docs/api_c/env_set_lg_dir.html | 73 ---- bdb/docs/api_c/env_set_lg_max.html | 68 ---- bdb/docs/api_c/env_set_lk_conflicts.html | 69 ---- bdb/docs/api_c/env_set_lk_detect.html | 72 ---- bdb/docs/api_c/env_set_lk_max.html | 72 ---- bdb/docs/api_c/env_set_lk_max_lockers.html | 68 ---- bdb/docs/api_c/env_set_lk_max_locks.html | 67 ---- bdb/docs/api_c/env_set_lk_max_objects.html | 68 ---- bdb/docs/api_c/env_set_mp_mmapsize.html | 71 ---- bdb/docs/api_c/env_set_mutexlocks.html | 59 ---- bdb/docs/api_c/env_set_pageyield.html | 68 ---- bdb/docs/api_c/env_set_paniccall.html | 67 ---- bdb/docs/api_c/env_set_panicstate.html | 64 ---- bdb/docs/api_c/env_set_rec_init.html | 71 ---- bdb/docs/api_c/env_set_region_init.html | 77 ----- bdb/docs/api_c/env_set_server.html | 77 ----- bdb/docs/api_c/env_set_shm_key.html | 87 ----- bdb/docs/api_c/env_set_tas_spins.html | 70 ---- bdb/docs/api_c/env_set_tmp_dir.html | 89 ----- bdb/docs/api_c/env_set_tx_max.html | 67 ---- bdb/docs/api_c/env_set_tx_recover.html | 75 ---- bdb/docs/api_c/env_set_tx_timestamp.html | 63 ---- bdb/docs/api_c/env_set_verbose.html | 78 ----- bdb/docs/api_c/env_strerror.html | 60 ---- bdb/docs/api_c/env_version.html | 57 ---- bdb/docs/api_c/hsearch.html | 107 ------ bdb/docs/api_c/lock_detect.html | 73 ---- bdb/docs/api_c/lock_get.html | 91 ----- bdb/docs/api_c/lock_id.html | 57 ---- bdb/docs/api_c/lock_put.html | 59 ---- bdb/docs/api_c/lock_stat.html | 92 ----- bdb/docs/api_c/lock_vec.html | 123 ------- bdb/docs/api_c/log_archive.html | 102 ------ bdb/docs/api_c/log_compare.html | 51 --- bdb/docs/api_c/log_file.html | 76 ----- bdb/docs/api_c/log_flush.html | 62 ---- bdb/docs/api_c/log_get.html | 114 ------- bdb/docs/api_c/log_put.html | 81 ----- bdb/docs/api_c/log_register.html | 64 ---- bdb/docs/api_c/log_stat.html | 90 ----- bdb/docs/api_c/log_unregister.html | 59 ---- bdb/docs/api_c/memp_fclose.html | 61 ---- bdb/docs/api_c/memp_fget.html | 98 ------ bdb/docs/api_c/memp_fopen.html | 157 --------- bdb/docs/api_c/memp_fput.html | 79 ----- bdb/docs/api_c/memp_fset.html | 72 ---- bdb/docs/api_c/memp_fsync.html | 59 ---- bdb/docs/api_c/memp_register.html | 93 ----- bdb/docs/api_c/memp_stat.html | 118 ------- bdb/docs/api_c/memp_sync.html | 83 ----- bdb/docs/api_c/memp_trickle.html | 66 ---- bdb/docs/api_c/pindex.src | 301 ---------------- bdb/docs/api_c/set_func_close.html | 66 ---- bdb/docs/api_c/set_func_dirfree.html | 75 ---- bdb/docs/api_c/set_func_dirlist.html | 78 ----- bdb/docs/api_c/set_func_exists.html | 75 ---- bdb/docs/api_c/set_func_free.html | 67 ---- bdb/docs/api_c/set_func_fsync.html | 66 ---- bdb/docs/api_c/set_func_ioinfo.html | 83 ----- bdb/docs/api_c/set_func_malloc.html | 67 ---- bdb/docs/api_c/set_func_map.html | 86 ----- bdb/docs/api_c/set_func_open.html | 66 ---- bdb/docs/api_c/set_func_read.html | 66 ---- bdb/docs/api_c/set_func_realloc.html | 67 ---- bdb/docs/api_c/set_func_rename.html | 66 ---- bdb/docs/api_c/set_func_seek.html | 81 ----- bdb/docs/api_c/set_func_sleep.html | 76 ----- bdb/docs/api_c/set_func_unlink.html | 66 ---- bdb/docs/api_c/set_func_unmap.html | 75 ---- bdb/docs/api_c/set_func_write.html | 67 ---- bdb/docs/api_c/set_func_yield.html | 84 ----- bdb/docs/api_c/txn_abort.html | 63 ---- bdb/docs/api_c/txn_begin.html | 93 ----- bdb/docs/api_c/txn_checkpoint.html | 75 ---- bdb/docs/api_c/txn_commit.html | 83 ----- bdb/docs/api_c/txn_id.html | 50 --- bdb/docs/api_c/txn_prepare.html | 63 ---- bdb/docs/api_c/txn_stat.html | 94 ----- 144 files changed, 13506 deletions(-) delete mode 100644 bdb/docs/api_c/c_index.html delete mode 100644 bdb/docs/api_c/c_pindex.html delete mode 100644 bdb/docs/api_c/db_close.html delete mode 100644 bdb/docs/api_c/db_create.html delete mode 100644 bdb/docs/api_c/db_cursor.html delete mode 100644 bdb/docs/api_c/db_del.html delete mode 100644 bdb/docs/api_c/db_err.html delete mode 100644 bdb/docs/api_c/db_fd.html delete mode 100644 bdb/docs/api_c/db_get.html delete mode 100644 bdb/docs/api_c/db_get_byteswapped.html delete mode 100644 bdb/docs/api_c/db_get_type.html delete mode 100644 bdb/docs/api_c/db_join.html delete mode 100644 bdb/docs/api_c/db_key_range.html delete mode 100644 bdb/docs/api_c/db_lsn.html delete mode 100644 bdb/docs/api_c/db_open.html delete mode 100644 bdb/docs/api_c/db_put.html delete mode 100644 bdb/docs/api_c/db_remove.html delete mode 100644 bdb/docs/api_c/db_rename.html delete mode 100644 bdb/docs/api_c/db_set_append_recno.html delete mode 100644 bdb/docs/api_c/db_set_bt_compare.html delete mode 100644 bdb/docs/api_c/db_set_bt_minkey.html delete mode 100644 bdb/docs/api_c/db_set_bt_prefix.html delete mode 100644 bdb/docs/api_c/db_set_cachesize.html delete mode 100644 bdb/docs/api_c/db_set_dup_compare.html delete mode 100644 bdb/docs/api_c/db_set_errcall.html delete mode 100644 bdb/docs/api_c/db_set_errfile.html delete mode 100644 bdb/docs/api_c/db_set_errpfx.html delete mode 100644 bdb/docs/api_c/db_set_feedback.html delete mode 100644 bdb/docs/api_c/db_set_flags.html delete mode 100644 bdb/docs/api_c/db_set_h_ffactor.html delete mode 100644 bdb/docs/api_c/db_set_h_hash.html delete mode 100644 bdb/docs/api_c/db_set_h_nelem.html delete mode 100644 bdb/docs/api_c/db_set_lorder.html delete mode 100644 bdb/docs/api_c/db_set_malloc.html delete mode 100644 bdb/docs/api_c/db_set_pagesize.html delete mode 100644 bdb/docs/api_c/db_set_paniccall.html delete mode 100644 bdb/docs/api_c/db_set_q_extentsize.html delete mode 100644 bdb/docs/api_c/db_set_re_delim.html delete mode 100644 bdb/docs/api_c/db_set_re_len.html delete mode 100644 bdb/docs/api_c/db_set_re_pad.html delete mode 100644 bdb/docs/api_c/db_set_re_source.html delete mode 100644 bdb/docs/api_c/db_set_realloc.html delete mode 100644 bdb/docs/api_c/db_stat.html delete mode 100644 bdb/docs/api_c/db_sync.html delete mode 100644 bdb/docs/api_c/db_upgrade.html delete mode 100644 bdb/docs/api_c/db_verify.html delete mode 100644 bdb/docs/api_c/dbc_close.html delete mode 100644 bdb/docs/api_c/dbc_count.html delete mode 100644 bdb/docs/api_c/dbc_del.html delete mode 100644 bdb/docs/api_c/dbc_dup.html delete mode 100644 bdb/docs/api_c/dbc_get.html delete mode 100644 bdb/docs/api_c/dbc_put.html delete mode 100644 bdb/docs/api_c/dbm.html delete mode 100644 bdb/docs/api_c/dbt.html delete mode 100644 bdb/docs/api_c/env_close.html delete mode 100644 bdb/docs/api_c/env_create.html delete mode 100644 bdb/docs/api_c/env_open.html delete mode 100644 bdb/docs/api_c/env_remove.html delete mode 100644 bdb/docs/api_c/env_set_cachesize.html delete mode 100644 bdb/docs/api_c/env_set_data_dir.html delete mode 100644 bdb/docs/api_c/env_set_errcall.html delete mode 100644 bdb/docs/api_c/env_set_errfile.html delete mode 100644 bdb/docs/api_c/env_set_errpfx.html delete mode 100644 bdb/docs/api_c/env_set_feedback.html delete mode 100644 bdb/docs/api_c/env_set_flags.html delete mode 100644 bdb/docs/api_c/env_set_lg_bsize.html delete mode 100644 bdb/docs/api_c/env_set_lg_dir.html delete mode 100644 bdb/docs/api_c/env_set_lg_max.html delete mode 100644 bdb/docs/api_c/env_set_lk_conflicts.html delete mode 100644 bdb/docs/api_c/env_set_lk_detect.html delete mode 100644 bdb/docs/api_c/env_set_lk_max.html delete mode 100644 bdb/docs/api_c/env_set_lk_max_lockers.html delete mode 100644 bdb/docs/api_c/env_set_lk_max_locks.html delete mode 100644 bdb/docs/api_c/env_set_lk_max_objects.html delete mode 100644 bdb/docs/api_c/env_set_mp_mmapsize.html delete mode 100644 bdb/docs/api_c/env_set_mutexlocks.html delete mode 100644 bdb/docs/api_c/env_set_pageyield.html delete mode 100644 bdb/docs/api_c/env_set_paniccall.html delete mode 100644 bdb/docs/api_c/env_set_panicstate.html delete mode 100644 bdb/docs/api_c/env_set_rec_init.html delete mode 100644 bdb/docs/api_c/env_set_region_init.html delete mode 100644 bdb/docs/api_c/env_set_server.html delete mode 100644 bdb/docs/api_c/env_set_shm_key.html delete mode 100644 bdb/docs/api_c/env_set_tas_spins.html delete mode 100644 bdb/docs/api_c/env_set_tmp_dir.html delete mode 100644 bdb/docs/api_c/env_set_tx_max.html delete mode 100644 bdb/docs/api_c/env_set_tx_recover.html delete mode 100644 bdb/docs/api_c/env_set_tx_timestamp.html delete mode 100644 bdb/docs/api_c/env_set_verbose.html delete mode 100644 bdb/docs/api_c/env_strerror.html delete mode 100644 bdb/docs/api_c/env_version.html delete mode 100644 bdb/docs/api_c/hsearch.html delete mode 100644 bdb/docs/api_c/lock_detect.html delete mode 100644 bdb/docs/api_c/lock_get.html delete mode 100644 bdb/docs/api_c/lock_id.html delete mode 100644 bdb/docs/api_c/lock_put.html delete mode 100644 bdb/docs/api_c/lock_stat.html delete mode 100644 bdb/docs/api_c/lock_vec.html delete mode 100644 bdb/docs/api_c/log_archive.html delete mode 100644 bdb/docs/api_c/log_compare.html delete mode 100644 bdb/docs/api_c/log_file.html delete mode 100644 bdb/docs/api_c/log_flush.html delete mode 100644 bdb/docs/api_c/log_get.html delete mode 100644 bdb/docs/api_c/log_put.html delete mode 100644 bdb/docs/api_c/log_register.html delete mode 100644 bdb/docs/api_c/log_stat.html delete mode 100644 bdb/docs/api_c/log_unregister.html delete mode 100644 bdb/docs/api_c/memp_fclose.html delete mode 100644 bdb/docs/api_c/memp_fget.html delete mode 100644 bdb/docs/api_c/memp_fopen.html delete mode 100644 bdb/docs/api_c/memp_fput.html delete mode 100644 bdb/docs/api_c/memp_fset.html delete mode 100644 bdb/docs/api_c/memp_fsync.html delete mode 100644 bdb/docs/api_c/memp_register.html delete mode 100644 bdb/docs/api_c/memp_stat.html delete mode 100644 bdb/docs/api_c/memp_sync.html delete mode 100644 bdb/docs/api_c/memp_trickle.html delete mode 100644 bdb/docs/api_c/pindex.src delete mode 100644 bdb/docs/api_c/set_func_close.html delete mode 100644 bdb/docs/api_c/set_func_dirfree.html delete mode 100644 bdb/docs/api_c/set_func_dirlist.html delete mode 100644 bdb/docs/api_c/set_func_exists.html delete mode 100644 bdb/docs/api_c/set_func_free.html delete mode 100644 bdb/docs/api_c/set_func_fsync.html delete mode 100644 bdb/docs/api_c/set_func_ioinfo.html delete mode 100644 bdb/docs/api_c/set_func_malloc.html delete mode 100644 bdb/docs/api_c/set_func_map.html delete mode 100644 bdb/docs/api_c/set_func_open.html delete mode 100644 bdb/docs/api_c/set_func_read.html delete mode 100644 bdb/docs/api_c/set_func_realloc.html delete mode 100644 bdb/docs/api_c/set_func_rename.html delete mode 100644 bdb/docs/api_c/set_func_seek.html delete mode 100644 bdb/docs/api_c/set_func_sleep.html delete mode 100644 bdb/docs/api_c/set_func_unlink.html delete mode 100644 bdb/docs/api_c/set_func_unmap.html delete mode 100644 bdb/docs/api_c/set_func_write.html delete mode 100644 bdb/docs/api_c/set_func_yield.html delete mode 100644 bdb/docs/api_c/txn_abort.html delete mode 100644 bdb/docs/api_c/txn_begin.html delete mode 100644 bdb/docs/api_c/txn_checkpoint.html delete mode 100644 bdb/docs/api_c/txn_commit.html delete mode 100644 bdb/docs/api_c/txn_id.html delete mode 100644 bdb/docs/api_c/txn_prepare.html delete mode 100644 bdb/docs/api_c/txn_stat.html (limited to 'bdb/docs/api_c') diff --git a/bdb/docs/api_c/c_index.html b/bdb/docs/api_c/c_index.html deleted file mode 100644 index 4b6023c8057..00000000000 --- a/bdb/docs/api_c/c_index.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - -Berkeley DB: C Interface by Function/Structure - - - - -

C Interface by Function/Structure

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Database EnvironmentDescription
db_env_createCreate an environment handle
DBENV->closeClose an environment
DBENV->errError message with error string
DBENV->errxError message
DBENV->openOpen an environment
DBENV->removeRemove an environment
DBENV->set_cachesizeSet the environment cache size
DBENV->set_data_dirSet the environment data directory
DBENV->set_errcallSet error message callback
DBENV->set_errfileSet error message FILE
DBENV->set_errpfxSet error message prefix
DBENV->set_feedbackSet feedback callback
DBENV->set_flagsEnvironment configuration
DBENV->set_mutexlocksTurn off mutual exclusion locking
DBENV->set_paniccallSet panic callback
DBENV->set_recovery_initSet recovery initialization callback
DBENV->set_serverEstablish server connection
DBENV->set_shm_keySet system memory shared segment ID
DBENV->set_tmp_dirSet the environment temporary file directory
DBENV->set_verboseSet verbose messages
db_strerrorError strings
db_versionReturn version information
Database OperationsDescription
db_createCreate a database handle
DB->closeClose a database
DB->delDelete items from a database
DB->errError message with error string
DB->errxError message
DB->fdReturn a file descriptor from a database
DB->getGet items from a database
DB->get_byteswappedReturn if the underlying database is in host order
DB->get_typeReturn the database type
DB->joinPerform a database join on cursors
DB->key_rangeReturn estimate of key location
DB->openOpen a database
DB->putStore items into a database
DB->removeRemove a database
DB->renameRename a database
DB->set_append_recnoSet record append callback
DB->set_bt_compareSet a Btree comparison function
DB->set_bt_minkeySet the minimum number of keys per Btree page
DB->set_bt_prefixSet a Btree prefix comparison function
DB->set_cachesizeSet the database cache size
DB->set_dup_compareSet a duplicate comparison function
DB->set_errcallSet error message callback
DB->set_errfileSet error message FILE
DB->set_errpfxSet error message prefix
DB->set_feedbackSet feedback callback
DB->set_flagsGeneral database configuration
DB->set_h_ffactorSet the Hash table density
DB->set_h_hashSet a hashing function
DB->set_h_nelemSet the Hash table size
DB->set_lorderSet the database byte order
DB->set_mallocSet a local space allocation function
DB->set_pagesizeSet the underlying database page size
DB->set_paniccallSet panic callback
DB->set_q_extentsizeSet Queue database extent size
DB->set_re_delimSet the variable-length record delimiter
DB->set_re_lenSet the fixed-length record length
DB->set_re_padSet the fixed-length record pad byte
DB->set_re_sourceSet the backing Recno text file
DB->set_reallocSet a local space allocation function
DB->statReturn database statistics
DB->syncFlush a database to stable storage
DB->upgradeUpgrade a database
DB->verifyVerify/salvage a database
Database CursorsDescription
DB->cursorOpen a cursor into a database
DBcursor->c_closeClose a cursor
DBcursor->c_countReturn count of duplicates
DBcursor->c_delDelete by cursor
DBcursor->c_dupDuplicate a cursor
DBcursor->c_getRetrieve by cursor
DBcursor->c_putStore by cursor
Lock ManagerDescription
DBENV->set_lk_conflictsSet lock conflicts matrix
DBENV->set_lk_detectSet automatic deadlock detection
DBENV->set_lk_maxSet maximum number of locks (Deprecated)
DBENV->set_lk_max_locksSet maximum number of locks
DBENV->set_lk_max_lockersSet maximum number of lockers
DBENV->set_lk_max_objectsSet maximum number of lock objects
lock_detectPerform deadlock detection
lock_getAcquire a lock
lock_idAcquire a locker ID
lock_putRelease a lock
lock_statReturn lock subsystem statistics
lock_vecAcquire/release locks
Log ManagerDescription
DBENV->set_lg_bsizeSet log buffer size
DBENV->set_lg_dirSet the environment logging directory
DBENV->set_lg_maxSet log file size
log_archiveList log and database files
log_compareCompare two Log Sequence Numbers
log_fileMap Log Sequence Numbers to log files
log_flushFlush log records
log_getGet a log record
log_putWrite a log record
log_registerRegister a file name with the log manager
log_statReturn log subsystem statistics
log_unregisterUnregister a file name with the log manager
Buffer PoolDescription
DBENV->set_cachesizeSet the environment cache size
DBENV->set_mp_mmapsizeSet maximum mapped-in database file size
memp_fcloseClose a file in a buffer pool
memp_fgetGet a page from a file in a buffer pool
memp_fopenOpen a file in a buffer pool
memp_fputReturn a page to a buffer pool
memp_fsetModify meta information for buffer pool page
memp_fsyncFlush pages from a file in a buffer pool
memp_registerRegister input/output functions for a file in a buffer pool
memp_statReturn buffer pool statistics
memp_syncFlush pages from a buffer pool
memp_trickleTrickle flush pages from a buffer pool
Transaction ManagerDescription
DBENV->set_tx_maxSet maximum number of transactions
DBENV->set_tx_recoverSet transaction abort recover function
DBENV->set_tx_timestampSet recovery timestamp
txn_abortAbort a transaction
txn_beginBegin a transaction
txn_checkpointCheckpoint the transaction subsystem
txn_commitCommit a transaction
txn_idReturn a transaction ID
txn_preparePrepare a transaction for commit
txn_statReturn transaction subsystem statistics
Historic InterfacesDescription
dbmUNIX Dbm/Ndbm Interfaces
hsearchUNIX Hsearch Interfaces
Data StructuresDescription
DBTDBT structures
DB_LSNDB_LSN structures
DB Library ConfigurationDescription
db_env_set_pageyieldYield the processor on each page access
db_env_set_panicstateReset panic state
db_env_set_region_initFault in shared regions on initial access
db_env_set_tas_spinsSet the number of test-and-set spins
DB System Call ConfigurationDescription
db_env_set_func_closeReplace underlying Berkeley DB system interfaces
db_env_set_func_dirfree
db_env_set_func_dirlist
db_env_set_func_exists
db_env_set_func_free
db_env_set_func_fsync
db_env_set_func_ioinfo
db_env_set_func_malloc
db_env_set_func_map
db_env_set_func_open
db_env_set_func_read
db_env_set_func_realloc
db_env_set_func_rename
db_env_set_func_seek
db_env_set_func_sleep
db_env_set_func_unlink
db_env_set_func_unmap
db_env_set_func_write
db_env_set_func_yield
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/c_pindex.html b/bdb/docs/api_c/c_pindex.html deleted file mode 100644 index 725bf0068a9..00000000000 --- a/bdb/docs/api_c/c_pindex.html +++ /dev/null @@ -1,530 +0,0 @@ - - -Berkeley DB: C Interface Index - - - - -

C Interface Index

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
configuring Berkeley DB 1.85 API compatibility
building a utility to dump Berkeley DB 1.85 databases
Upgrading to release 2.0
Upgrading to release 3.0
Upgrading to release 3.1
Upgrading to release 3.2
selecting an access method
access methods
AIX
data alignment
programmatic APIs
utility to archive log files
berkeley_db_svc
building for UNIX
building for UNIX FAQ
building for VxWorks
building for VxWorks FAQ
building for Win32
building for Windows FAQ
selecting a byte order
byte ordering
configuring the C++ API
flushing the database cache
selecting a cache size
catastrophic recovery
Patches, Updates and Change logs
utility to take checkpoints
memp_fopenclear_len
closing a cursor
closing a database
specifying a Btree comparison function
changing compile or load options
Concurrent Data Store
configuring Berkeley DB for UNIX systems
recovering corrupted databases
counting data items for a key
closing a cursor
deleting records with a cursor
duplicating a cursor
retrieving records with a cursor
storing records with a cursor
cursor stability
database cursors
DBTdata
utility to upgrade database files
utility to verify database files
DBcursor->c_putDB_AFTER
DB->verifyDB_AGGRESSIVE
DB->putDB_APPEND
log_archiveDB_ARCH_ABS
log_archiveDB_ARCH_DATA
db_archive
log_archiveDB_ARCH_LOG
DBcursor->c_putDB_BEFORE
DB->statDB_CACHED_COUNTS
DBENV->set_flagsDB_CDB_ALLDB
log_getDB_CHECKPOINT
log_putDB_CHECKPOINT
db_checkpoint
db_env_createDB_CLIENT
File namingDB_CONFIG
DB->getDB_CONSUME
DB->getDB_CONSUME_WAIT
db_create
DB->openDB_CREATE
DBENV->openDB_CREATE
memp_fopenDB_CREATE
log_putDB_CURLSN
DBcursor->c_getDB_CURRENT
DBcursor->c_putDB_CURRENT
log_getDB_CURRENT
DBcursor->c_close
DBcursor->c_count
DBcursor->c_del
DBcursor->c_dup
DBcursor->c_get
DBcursor->c_put
DBTDB_DBT_MALLOC
DBTDB_DBT_PARTIAL
DBTDB_DBT_REALLOC
DBTDB_DBT_USERMEM
db_deadlock
db_dump
DB->set_flagsDB_DUP
DB->set_flagsDB_DUPSORT
DB->upgradeDB_DUPSORT
db_env_create
DBENV->close
DBENV->err
DBENV->open
DBENV->remove
DBENV->set_cachesize
DBENV->set_data_dir
DBENV->set_errcall
DBENV->set_errfile
DBENV->set_errpfx
DBENV->set_feedback
DBENV->set_flags
DBENV->set_lg_bsize
DBENV->set_lg_dir
DBENV->set_lg_max
DBENV->set_lk_conflicts
DBENV->set_lk_detect
DBENV->set_lk_max
DBENV->set_lk_max_lockers
DBENV->set_lk_max_locks
DBENV->set_lk_max_objects
DBENV->set_mp_mmapsize
DBENV->set_mutexlocks
DBENV->set_paniccall
DBENV->set_recovery_init
DBENV->set_server
DBENV->set_shm_key
DBENV->set_tmp_dir
DBENV->set_tx_max
DBENV->set_tx_recover
DBENV->set_tx_timestamp
DBENV->set_verbose
db_env_set_func_close
db_env_set_func_dirfree
db_env_set_func_dirlist
db_env_set_func_exists
db_env_set_func_free
db_env_set_func_fsync
db_env_set_func_ioinfo
db_env_set_func_malloc
db_env_set_func_map
db_env_set_func_open
db_env_set_func_read
db_env_set_func_realloc
db_env_set_func_rename
db_env_set_func_seek
db_env_set_func_sleep
db_env_set_func_unlink
db_env_set_func_unmap
db_env_set_func_write
db_env_set_func_yield
db_env_set_pageyield
db_env_set_panicstate
db_env_set_region_init
db_env_set_tas_spins
DB->openDB_EXCL
DBcursor->c_getDB_FIRST
log_getDB_FIRST
log_putDB_FLUSH
DBENV->removeDB_FORCE
txn_checkpointDB_FORCE
DB->getDB_GET_BOTH
DBcursor->c_getDB_GET_BOTH
DBcursor->c_getDB_GET_RECNO
DB->close
DB->cursor
DB->del
DB->fd
DB->get
DB->get_byteswapped
DB->get_type
DB->join
DB->key_range
DB->open
DB->put
DB->remove
DB->rename
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_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
DB->verify
File namingDB_HOME
File namingdb_home
DB->close DB_INCOMPLETE
DBENV->openDB_INIT_CDB
DBENV->openDB_INIT_LOCK
DBENV->openDB_INIT_LOG
DBENV->openDB_INIT_MPOOL
DBENV->openDB_INIT_TXN
DBENV->openDB_JOINENV
DB->joinDB_JOIN_ITEM
DBcursor->c_getDB_JOIN_ITEM
DB->joinDB_JOIN_NOSORT
Error returns to applicationsDB_KEYEMPTY
DBcursor->c_putDB_KEYFIRST
DBcursor->c_putDB_KEYLAST
DBcursor->c_getDB_LAST
log_getDB_LAST
db_load
lock_detectDB_LOCK_CONFLICT
Error returns to applicationsDB_LOCK_DEADLOCK
DBENV->set_lk_detectDB_LOCK_DEFAULT
DBENV->openDB_LOCKDOWN
lock_vecDB_LOCK_GET
lock_getDB_LOCK_NOTGRANTED
lock_vecDB_LOCK_NOTGRANTED
Error returns to applicationsDB_LOCK_NOTGRANTED
lock_getDB_LOCK_NOWAIT
lock_vecDB_LOCK_NOWAIT
DBENV->set_lk_detectDB_LOCK_OLDEST
lock_vecDB_LOCK_PUT
lock_vecDB_LOCK_PUT_ALL
lock_vecDB_LOCK_PUT_OBJ
DBENV->set_lk_detectDB_LOCK_RANDOM
DBENV->set_lk_detectDB_LOCK_YOUNGEST
DB_LSN
dbm/ndbm
memp_fputDB_MPOOL_CLEAN
memp_fsetDB_MPOOL_CLEAN
memp_fgetDB_MPOOL_CREATE
memp_fputDB_MPOOL_DIRTY
memp_fsetDB_MPOOL_DIRTY
memp_fputDB_MPOOL_DISCARD
memp_fsetDB_MPOOL_DISCARD
memp_fgetDB_MPOOL_LAST
memp_fgetDB_MPOOL_NEW
DBcursor->c_getDB_NEXT
log_getDB_NEXT
DBcursor->c_getDB_NEXT_DUP
DBcursor->c_getDB_NEXT_NODUP
DB->putDB_NODUPDATA
DBcursor->c_putDB_NODUPDATA
DB->openDB_NOMMAP
DBENV->set_flagsDB_NOMMAP
memp_fopenDB_NOMMAP
DB->verifyDB_NOORDERCHK
DB->putDB_NOOVERWRITE
DBENV->set_serverDB_NOSERVER
DBENV->set_serverDB_NOSERVER_ID
DB->closeDB_NOSYNC
Error returns to applicationsDB_NOTFOUND
DB->openDB_OLD_VERSION
DB->upgradeDB_OLD_VERSION
DB->verifyDB_ORDERCHKONLY
DBcursor->c_dupDB_POSITION
DBcursor->c_getDB_PREV
log_getDB_PREV
DBcursor->c_getDB_PREV_NODUP
db_printlog
DBENV->openDB_PRIVATE
DB->openDB_RDONLY
memp_fopenDB_RDONLY
DB->set_flagsDB_RECNUM
DB->statDB_RECORDCOUNT
DBENV->openDB_RECOVER
DBENV->set_feedbackDB_RECOVER
db_recover
DBENV->openDB_RECOVER_FATAL
DB->set_flagsDB_RENUMBER
DB->set_flagsDB_REVSPLITOFF
DB->getDB_RMW
DB->joinDB_RMW
DBcursor->c_getDB_RMW
Error returns to applicationsDB_RUNRECOVERY
DB->verifyDB_SALVAGE
DBcursor->c_getDB_SET
log_getDB_SET
DBcursor->c_getDB_SET_RANGE
DB->getDB_SET_RECNO
DBcursor->c_getDB_SET_RECNO
DB->set_flagsDB_SNAPSHOT
db_stat
db_strerror
DBENV->openDB_SYSTEM_MEM
DB->openDB_THREAD
DBENV->openDB_THREAD
DB->openDB_TRUNCATE
DBENV->set_tx_recoverDB_TXN_ABORT
DBENV->set_tx_recoverDB_TXN_BACKWARD_ROLL
DBENV->set_tx_recoverDB_TXN_FORWARD_ROLL
DBENV->set_flagsDB_TXN_NOSYNC
txn_beginDB_TXN_NOSYNC
txn_commitDB_TXN_NOSYNC
txn_beginDB_TXN_NOWAIT
txn_beginDB_TXN_SYNC
txn_commitDB_TXN_SYNC
DB->set_feedbackDB_UPGRADE
db_upgrade
DBENV->openDB_USE_ENVIRON
DBENV->removeDB_USE_ENVIRON
DBENV->openDB_USE_ENVIRON_ROOT
DBENV->removeDB_USE_ENVIRON_ROOT
DBENV->set_verboseDB_VERB_CHKPOINT
DBENV->set_verboseDB_VERB_DEADLOCK
DBENV->set_verboseDB_VERB_RECOVERY
DBENV->set_verboseDB_VERB_WAITSFOR
DB->set_feedbackDB_VERIFY
db_verify
db_version
DB->cursorDB_WRITECURSOR
db_createDB_XA_CREATE
deadlocks
utility to detect deadlocks
debugging applications
deleting records
deleting records with a cursor
Configuring Berkeley DB--disable-bigfile
disk space requirements
DBTdlen
DBTdoff
utility to dump databases as text files
duplicate data items
duplicating a cursor
configuring dynamic shared libraries
Configuring Berkeley DB--enable-compat185
Configuring Berkeley DB--enable-cxx
Configuring Berkeley DB--enable-debug
Configuring Berkeley DB--enable-debug_rop
Configuring Berkeley DB--enable-debug_wop
Configuring Berkeley DB--enable-diagnostic
Configuring Berkeley DB--enable-dump185
Configuring Berkeley DB--enable-dynamic
Configuring Berkeley DB--enable-java
Configuring Berkeley DB--enable-posixmutexes
Configuring Berkeley DB--enable-rpc
Configuring Berkeley DB--enable-shared
Configuring Berkeley DB--enable-tcl
Configuring Berkeley DB--enable-test
Configuring Berkeley DB--enable-uimutexes
Configuring Berkeley DB--enable-umrw
byte endian
database environment
environment variables
error handling
error name space
error returns
/etc/magic
selecting a Queue extent size
Java FAQ
Tcl FAQ
configuring without large file support
file utility
memp_fopenfileid
recovery and filesystem operations
remote filesystems
page fill factor
FreeBSD
Berkeley DB free-threaded handles
memp_fopenftype
specifying a database hash
hash table size
HP-UX
hsearch
installing Berkeley DB for UNIX systems
interface compatibility
IRIX
configuring the Java API
Java compatibility
Java configuration
Java FAQ
logical join
key/data pairs
retrieved key/data permanence
database limits
Linux
changing compile or load options
utility to load text files into databases
lock_veclock
standard lock modes
lock_detect
lock_get
lock_id
page-level locking
two-phase locking
locking and non-Berkeley DB applications
locking configuration
locking conventions
Berkeley DB Concurrent Data Store locking conventions
locking introduction
sizing the locking subsystem
locking without transactions
lock_put
lock_stat
lock_vec
log file limits
log file removal
utility to display log files as text
log_archive
log_compare
log_file
log_flush
log_get
logging configuration
logging introduction
log_put
log_register
log_stat
log_unregister
memp_fopenlsn_offset
memory pool configuration
memp_fclose
memp_fget
memp_fopen
memp_fput
memp_fset
memp_fsync
memp_register
memp_stat
memp_sync
memp_trickle
lock_vecmode
Berkeley DB library name spaces
file naming
retrieving Btree records by number
lock_vecobj
lock_vecop
opening a database
OSF/1
selecting a page size
partial record storage and retrieval
Patches, Updates and Change logs
Perl
retrieved key/data permanence
memp_fopenpgcookie
Sleepycat Software's Berkeley DB products
QNX
logical record number format
logical record numbers
managing record-based databases
logically renumbering records
utility to recover database environments
Berkeley DB recoverability
retrieving records
retrieving records with a cursor
RPC client
configuring a RPC client/server
utility to support RPC client/server
RPC server
database salvage
SCO
Berkeley DB handle scope
security
Sendmail
configuring shared libraries
shared libraries
application signal handling
DBTsize
Sleepycat Software
Solaris
source code layout
cursor stability
database statistics
utility to display database and environment statistics
storing records
storing records with a cursor
SunOS
loading Berkeley DB with Tcl
using Berkeley DB with Tcl
configuring the Tcl API
Tcl API programming notes
Tcl FAQ
configuring the test suite
running the test suite
running the test suite under UNIX
running the test suite under Windows
text backing files
loading text into databases
dumping/loading text to/from databases
building threaded applications
transaction configuration
transaction limits
administering transaction protected applications
archival in transaction protected applications
checkpoints in transaction protected applications
deadlock detection in transaction protected applications
recovery in transaction protected applications
transaction throughput
Transactional Data Store
Berkeley DB and transactions
nested transactions
configuring Berkeley DB with the Tuxedo System
txn_abort
txn_begin
txn_checkpoint
txn_commit
txn_id
txn_prepare
txn_stat
DBTulen
Ultrix
building for UNIX FAQ
configuring Berkeley DB for UNIX systems
Patches, Updates and Change logs
utility to upgrade database files
upgrading databases
utilities
database verification
utility to verify database files
building for VxWorks FAQ
VxWorks notes
running the test suite under Windows
building for Windows FAQ
Windows notes
Configuring Berkeley DB--with-tcl=DIR
XA Resource Manager
-
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_close.html b/bdb/docs/api_c/db_close.html deleted file mode 100644 index f6c763c5b12..00000000000 --- a/bdb/docs/api_c/db_close.html +++ /dev/null @@ -1,119 +0,0 @@ - - - - - -Berkeley DB: DB->close - - - - - - - -
-

DB->close

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->close(DB *db, u_int32_t flags);
-

-

Description

-

The DB->close function flushes any cached database information to disk, -closes any open cursors, frees any allocated resources, and closes any -underlying files. Since key/data pairs are cached in memory, failing to -sync the file with the DB->close or DB->sync function may result -in inconsistent or lost information. -

The flags parameter must be set to 0 or the following value: -

-

DB_NOSYNC
Do not flush cached information to disk. -

The DB_NOSYNC flag is a dangerous option. It should only be set -if the application is doing logging (with transactions) so that the -database is recoverable after a system or application crash, or if the -database is always generated from scratch after any system or application -crash. -

It is important to understand that flushing cached information to disk -only minimizes the window of opportunity for corrupted data. -While unlikely, it is possible for database corruption to happen if a -system or application crash occurs while writing data to the database. -To ensure that database corruption never occurs, applications must either: -use transactions and logging with automatic recovery, use logging and -application-specific recovery, or edit a copy of the database, -and, once all applications using the database have successfully called -DB->close, atomically replace the original database with the -updated copy. -

-

When multiple threads are using the Berkeley DB handle concurrently, only a single -thread may call the DB->close function. -

Once DB->close has been called, regardless of its return, the -DB handle may not be accessed again. - -

The DB->close function returns a non-zero error value on failure, 0 on success, and returns DB_INCOMPLETE if the underlying database still has -dirty pages in the cache. (The only reason to return -DB_INCOMPLETE is if another thread of control was writing pages -in the underlying database file at the same time as the -DB->close function was called. For this reason, a return of -DB_INCOMPLETE can normally be ignored, or, in cases where it is -a possible return value, the DB_NOSYNC option should probably -have been specified.) -

The DB->close function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DB->close 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->close function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_create.html b/bdb/docs/api_c/db_create.html deleted file mode 100644 index c1fd3fca10b..00000000000 --- a/bdb/docs/api_c/db_create.html +++ /dev/null @@ -1,107 +0,0 @@ - - - - - -Berkeley DB: db_create - - - - - - - -
-

db_create

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_create(DB **dbp, DB_ENV *dbenv, u_int32_t flags);
-

-

Description

-

The db_create function creates a DB structure which is the -handle for a Berkeley DB database. A pointer to this structure is returned -in the memory referenced by db. -

If the dbenv argument is NULL, the database is standalone, i.e., -it is not part of any Berkeley DB environment. -

If the dbenv argument is not NULL, the database is created within -the specified Berkeley DB environment. The database access methods -automatically make calls to the other subsystems in Berkeley DB based on the -enclosing environment. For example, if the environment has been -configured to use locking, then the access methods will automatically -acquire the correct locks when reading and writing pages of the database. -

The flags parameter must be set to 0 or one of the following -values: -

-

DB_XA_CREATE
Instead of creating a standalone database, create a database intended to -be accessed via applications running under a X/Open conformant Transaction -Manager. The database will be opened in the environment specified by the -OPENINFO parameter of the GROUPS section of the ubbconfig file. See the -XA Resource Manager chapter in the -Reference Guide for more information. -
-

The DB handle contains a special field, "app_private", which -is declared as type "void *". This field is provided for the use of -the application program. It is initialized to NULL and is not further -used by Berkeley DB in any way. -

The db_create function returns a non-zero error value on failure and 0 on success. -

Errors

-

The db_create 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_create function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_cursor.html b/bdb/docs/api_c/db_cursor.html deleted file mode 100644 index 1fb6616ab63..00000000000 --- a/bdb/docs/api_c/db_cursor.html +++ /dev/null @@ -1,103 +0,0 @@ - - - - - -Berkeley DB: DB->cursor - - - - - - - -
-

DB->cursor

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->cursor(DB *db,
-    DB_TXN *txnid, DBC **cursorp, u_int32_t flags);
-

-

Description

-

The DB->cursor function -creates a cursor and copies a pointer to it into the memory referenced -by cursorp. -

If the file is being accessed under transaction protection, the -txnid parameter is a transaction ID returned from -txn_begin, otherwise, NULL. -

If transaction protection is enabled, cursors must be opened and closed -within the context of a transaction, and the txnid parameter -specifies the transaction context in which the cursor may be used. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_WRITECURSOR
Specify that the cursor will be used to update the database. This -flag should only be set when the DB_INIT_CDB flag -was specified to DBENV->open. -
-

The DB->cursor function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DB->cursor function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The DB->cursor 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->cursor function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_del.html b/bdb/docs/api_c/db_del.html deleted file mode 100644 index b273d29fd14..00000000000 --- a/bdb/docs/api_c/db_del.html +++ /dev/null @@ -1,101 +0,0 @@ - - - - - -Berkeley DB: DB->del - - - - - - - -
-

DB->del

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->del(DB *db, DB_TXN *txnid, DBT *key, u_int32_t flags);
-

-

Description

-

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. -

If the file is being accessed under transaction protection, the -txnid parameter is a transaction ID 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. -

Errors

-

The DB->del function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

EACCES
An attempt was made to modify a read-only database. -
-

-

EINVAL
An invalid flag value or parameter was specified. -
-

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. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_err.html b/bdb/docs/api_c/db_err.html deleted file mode 100644 index 1eae12fabf0..00000000000 --- a/bdb/docs/api_c/db_err.html +++ /dev/null @@ -1,93 +0,0 @@ - - - - - -Berkeley DB: DBENV->err - - - - - - - -
-

DBENV->err

-		 -APIRef -
-

- -

-#include <db.h>
-

-void
-DBENV->err(DB_ENV *dbenv, int error, const char *fmt, ...);
-

-void
-DBENV->errx(DB_ENV *dbenv, const char *fmt, ...);
-

-void
-DB->err(DB *db, int error, const char *fmt, ...);
-

-void
-DB->errx(DB *db, const char *fmt, ...);
-

-

Description

-

The DBENV->err, DBENV->errx, DB->err and -DB->errx functions provide error messaging functionality for -applications written using the Berkeley DB library. -

The DBENV->err function constructs an error message consisting of the -following elements: -

-

An optional prefix string
If no error callback function has been set using the -DBENV->set_errcall function, any prefix string specified using the -DBENV->set_errpfx function, followed by two separating characters: a colon -and a <space> character. -

An optional printf-style message
The supplied message fmt, if non-NULL, where the ANSI C X3.159-1989 (ANSI C) -printf function specifies how subsequent arguments are converted for -output. -

A separator
Two separating characters: a colon and a <space> character. -

A standard error string
The standard system or Berkeley DB library error string associated with the -error value, as returned by the db_strerror function. -
-
-

This constructed error message is then handled as follows: -

-

If an error callback function has been set (see DB->set_errcall -and DBENV->set_errcall), that function is called with two -arguments: any prefix string specified (see DB->set_errpfx and -DBENV->set_errpfx), and the error message. -

If a C library FILE * has been set (see DB->set_errfile and -DBENV->set_errfile), the error message is written to that output -stream. -

If none of these output options has been configured, the error message -is written to stderr, the standard error output stream.

-

The DBENV->errx and DB->errx functions perform identically to the -DBENV->err and DB->err functions except that they do not append -the final separator characters and standard error string to the error -message. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_fd.html b/bdb/docs/api_c/db_fd.html deleted file mode 100644 index 2a385c1b3d1..00000000000 --- a/bdb/docs/api_c/db_fd.html +++ /dev/null @@ -1,92 +0,0 @@ - - - - - -Berkeley DB: DB->fd - - - - - - - -
-

DB->fd

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->fd(DB *db, int *fdp);
-

-

Description

-

The DB->fd function -copies a file descriptor representative of the underlying database into -the memory referenced by fdp. A file descriptor referencing the -same file will be returned to all processes that call DB->open with -the same file argument. This file descriptor may be safely used -as an argument to the fcntl(2) and flock(2) locking -functions. The file descriptor is not necessarily associated with any of -the underlying files actually used by the access method. -

The DB->fd function only supports a coarse-grained form of locking. -Applications should use the lock manager where possible. -

The DB->fd function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DB->fd 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->fd function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_get.html b/bdb/docs/api_c/db_get.html deleted file mode 100644 index c6cc3fcce43..00000000000 --- a/bdb/docs/api_c/db_get.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - -Berkeley DB: DB->get - - - - - - - -
-

DB->get

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->get(DB *db,
-    DB_TXN *txnid, DBT *key, DBT *data, u_int32_t flags);
-

-

Description

-

The DB->get function retrieves key/data pairs from the database. The -address -and length of the data associated with the specified key are -returned in the structure referenced by data. -

In the presence of duplicate key values, DB->get will return the -first data item for the designated key. Duplicates are sorted by insert -order except where this order has been overridden by cursor operations. -Retrieval of duplicates requires the use of cursor operations. -See DBcursor->c_get for details. -

If the file is being accessed under transaction protection, the -txnid parameter is a transaction ID returned from -txn_begin, otherwise, NULL. -

The flags parameter must be set to 0 or one of the following -values: -

-

DB_CONSUME
Return the record number and data from the available record closest to -the head of the queue and delete the record. The cursor will be -positioned on the deleted record. The record number will be returned -in key as described in DBT. The data will be returned -in the data parameter. A record is available if it is not -deleted and is not currently locked. The underlying database must be -of type Queue for DB_CONSUME to be specified. -

DB_CONSUME_WAIT
The DB_CONSUME_WAIT flag is the same as the DB_CONSUME -flag except that if the Queue database is empty, the thread of control -will wait until there is data in the queue before returning. The -underlying database must be of type Queue for DB_CONSUME_WAIT -to be specified. -

DB_GET_BOTH
Retrieve the key/data pair only if both the key and data match the -arguments. -

DB_SET_RECNO
Retrieve the specified numbered key/data pair from a database. -Upon return, both the key and data items will have been -filled in, not just the data item as is done for all other uses of the -DB->get function. -

The data field of the specified key -must be a pointer to a logical record number (i.e., a db_recno_t). -This record number determines the record to be retrieved. -

For DB_SET_RECNO to be specified, the underlying database must be -of type Btree and it must have been created with the DB_RECNUM flag. -

-

In addition, the following flag may be set by bitwise inclusively OR'ing it into the -flags parameter: -

-

DB_RMW
Acquire write locks instead of read locks when doing the retrieval. -Setting this flag may decrease the likelihood of deadlock during a -read-modify-write cycle by immediately acquiring the write lock during -the read part of the cycle so that another thread of control acquiring -a read lock for the same item, in its own read-modify-write cycle, will -not result in deadlock. -

As the DB->get interface will not hold locks across -Berkeley DB interface calls in non-transactional environments, the -DB_RMW flag to the DB->get call is only meaningful in -the presence of transactions. -

-

If the database is a Queue or Recno database and the requested key exists, -but was never explicitly created by the application or was later deleted, -the DB->get function returns DB_KEYEMPTY. -

Otherwise, if the requested key is not in the database, the -DB->get function returns DB_NOTFOUND. -

Otherwise, the DB->get function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DB->get function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

ENOMEM
There was insufficient memory to return the requested item. -
-

-

EINVAL
An invalid flag value or parameter was specified. -

A record number of 0 was specified. -

The DB_THREAD flag was specified to the -DB->open function and none of the DB_DBT_MALLOC, -DB_DBT_REALLOC or DB_DBT_USERMEM flags were set in the -DBT. -

-

The DB->get 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->get function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_get_byteswapped.html b/bdb/docs/api_c/db_get_byteswapped.html deleted file mode 100644 index 205ddb79467..00000000000 --- a/bdb/docs/api_c/db_get_byteswapped.html +++ /dev/null @@ -1,84 +0,0 @@ - - - - - -Berkeley DB: DB->get_byteswapped - - - - - - - -
-

DB->get_byteswapped

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->get_byteswapped(DB *db);
-

-

Description

-

The DB->get_byteswapped function returns -0 -if the underlying database files were created on an architecture -of the same byte order as the current one, and -1 -if they were not (i.e., big-endian on a little-endian machine or -vice-versa). This field may be used to determine if application -data needs to be adjusted for this architecture or not. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_get_type.html b/bdb/docs/api_c/db_get_type.html deleted file mode 100644 index a1905c782e4..00000000000 --- a/bdb/docs/api_c/db_get_type.html +++ /dev/null @@ -1,81 +0,0 @@ - - - - - -Berkeley DB: DB->get_type - - - - - - - -
-

DB->get_type

-		 -APIRef -
-

- -

-#include <db.h>
-

-DBTYPE
-DB->get_type(DB *db);
-

-

Description

-

The DB->get_type function returns the type of the underlying access method -(and file format). It returns one of DB_BTREE, -DB_HASH or DB_RECNO. This value may be used to -determine the type of the database after a return from DB->open -with the type argument set to DB_UNKNOWN. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_join.html b/bdb/docs/api_c/db_join.html deleted file mode 100644 index 13fe95d84d7..00000000000 --- a/bdb/docs/api_c/db_join.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - -Berkeley DB: DB->join - - - - - - - -
-

DB->join

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->join(DB *primary,
-	DBC **curslist, DBC **dbcp, u_int32_t flags);
-

-

Description

-

The DB->join function creates a specialized cursor for use in performing -joins on secondary indexes. For information on how to organize your data -to use this functionality, see Logical -join. -

The primary argument contains the DB handle of the primary -database, which is keyed by the data values found in entries in the -curslist. -

The curslist argument contains a NULL terminated array of cursors. -Each cursor must have been initialized to reference the key on which the -underlying database should be joined. Typically, this initialization is done -by a DBcursor->c_get call with the DB_SET flag specified. Once the -cursors have been passed as part of a curslist, they should not -be accessed or modified until the newly created join cursor has been closed, -or else inconsistent results may be returned. -

Joined values are retrieved by doing a sequential iteration over the first -cursor in the curslist argument, and a nested iteration over each -secondary cursor in the order they are specified in the curslist -argument. This requires database traversals to search for the current -datum in all the cursors after the first. For this reason, the best join -performance normally results from sorting the cursors from the one that -references the least number of data items to the one that references the -most. By default, DB->join does this sort on behalf of its caller. -

The flags parameter must be set to 0 or the following value: -

-

DB_JOIN_NOSORT
Do not sort the cursors based on the number of data items they reference. -If the data are structured such that cursors with many data items also -share many common elements, higher performance will result from listing -those cursors before cursors with fewer data items, that is, a sort order -other than the default. The DB_JOIN_NOSORT flag permits -applications to perform join optimization prior to calling DB->join. -
-

A newly created cursor is returned in the memory location referenced by -dbcp and has the standard cursor functions: -

-

DBcursor->c_get
Iterates over the values associated with the keys to which each item in -curslist has been initialized. Any data value which appears in -all items specified by the curslist argument is then used as a -key into the primary, and the key/data pair found in the -primary is returned. -

The flags parameter must be set to 0 or the following value: -

-

DB_JOIN_ITEM
Do not use the data value found in all of the cursors as a lookup -key for the primary, but simply return it in the key parameter -instead. The data parameter is left unchanged. -
-

In addition, the following flag may be set by bitwise inclusively OR'ing it into the -flags parameter: -

-

DB_RMW
Acquire write locks instead of read locks when doing the retrieval. -Setting this flag may decrease the likelihood of deadlock during a -read-modify-write cycle by immediately acquiring the write lock during -the read part of the cycle so that another thread of control acquiring -a read lock for the same item, in its own read-modify-write cycle, will -not result in deadlock. -
-

DBcursor->c_put
Returns EINVAL. -

DBcursor->c_del
Returns EINVAL. -

DBcursor->c_close
Close the returned cursor and release all resources. (Closing the cursors -in curslist is the responsibility of the caller.) -
-

For the returned join cursor to be used in a transaction protected manner, -the cursors listed in curslist must have been created within the -context of the same transaction. -

The DB->join function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DB->join function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -

The DBcursor->c_put or DBcursor->c_del functions were called. -

-

The DB->join 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->join function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_key_range.html b/bdb/docs/api_c/db_key_range.html deleted file mode 100644 index 1e3c4c91f99..00000000000 --- a/bdb/docs/api_c/db_key_range.html +++ /dev/null @@ -1,106 +0,0 @@ - - - - - -Berkeley DB: DB->key_range - - - - - - - -
-

DB->key_range

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->key_range(DB *db, DB_TXN *txnid,
-	DBT *key, DB_KEY_RANGE *key_range, u_int32_t flags);
-

-

Description

-

The DB->key_range function returns an estimate of the proportion of keys -that are less than, equal to and greater than the specified key. The -underlying database must be of type Btree. -

The information is returned in the key_range argument, which -contains three elements of type double, less, equal and -greater. Values are in the range of 0 to 1, e.g., if the field -less is 0.05, that indicates that 5% of the keys in the database -are less than the key argument. The value for equal will be zero -if there is no matching key and non-zero otherwise. -

If the file is being accessed under transaction protection, the -txnid parameter is a transaction ID returned from -txn_begin, otherwise, NULL. -The DB->key_range function does not retain the locks it acquires for the -life of the transaction, so estimates may not be repeatable. -

The flags parameter is currently unused, and must be set to 0. -

The DB->key_range function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DB->key_range function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

EINVAL
An invalid flag value or parameter was specified. -

The underlying database was not of type Btree. -

-

The DB->key_range 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->key_range function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_lsn.html b/bdb/docs/api_c/db_lsn.html deleted file mode 100644 index 1fc62e5e688..00000000000 --- a/bdb/docs/api_c/db_lsn.html +++ /dev/null @@ -1,36 +0,0 @@ - - - - - -Berkeley DB: DB_LSN - - - - - - - -
-

DB_LSN

-		 -APIRef -
-

- -

-#include <db.h>
-

-

Description

-

A DB_LSN is a log sequence number, which indicates a -unique position in the log. The DB_LSN structure is completely -opaque, and no application should ever need to look inside. -DB_LSN structures are used by the logging and memory pool -subsystems. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_open.html b/bdb/docs/api_c/db_open.html deleted file mode 100644 index afd410223a6..00000000000 --- a/bdb/docs/api_c/db_open.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - -Berkeley DB: DB->open - - - - - - - -
-

DB->open

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->open(DB *db, const char *file,
-    const char *database, DBTYPE type, u_int32_t flags, int mode);
-

-

Description

-

The currently supported Berkeley DB file formats (or access methods) -are Btree, Hash, Queue and Recno. The Btree format is a representation -of a sorted, balanced tree structure. The Hash format is an extensible, -dynamic hashing scheme. The Queue format supports fast access to -fixed-length records accessed by sequentially or logical record number. -The Recno format supports fixed- or variable-length records, accessed -sequentially or by logical record number, and optionally retrieved from -a flat text file. -

Storage and retrieval for the Berkeley DB access methods are based on key/data -pairs, see DBT for more information. -

The DB->open interface opens the database represented by the -file and database arguments for both reading and writing. -The file argument is used as the name of a physical file on disk -that will be used to back the database. The database argument is -optional and allows applications to have multiple logical databases in a -single physical file. While no database argument needs to be -specified, it is an error to attempt to open a second database in a -file that was not initially created using a database name. -In-memory databases never intended to be preserved on disk may -be created by setting both the file and database arguments -to NULL. Note that in-memory databases can only ever be shared by -sharing the single database handle that created them, in circumstances -where doing so is safe. -

The type argument is of type DBTYPE -and must be set to one of DB_BTREE, DB_HASH, -DB_QUEUE, DB_RECNO or DB_UNKNOWN, except -that databases of type DB_QUEUE are restricted to one per -file. If type is DB_UNKNOWN, the database must -already exist and DB->open will automatically determine its type. -The DB->get_type function may be used to determine the underlying type of -databases opened using DB_UNKNOWN. -

The flags and mode arguments specify how files will be opened -and/or created if they do not already exist. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_CREATE
Create any underlying files, as necessary. If the files do not already -exist and the DB_CREATE flag is not specified, the call will fail. -

DB_EXCL
Return an error if the file already exists. Underlying filesystem -primitives are used to implement this flag. For this reason it is only -applicable to the physical file and cannot be used to test if a database -in a file already exists. -

The DB_EXCL flag is only meaningful when specified with the -DB_CREATE flag. -

DB_NOMMAP
Do not map this database into process memory (see the description of the -DBENV->set_mp_mmapsize function for further information). -

DB_RDONLY
Open the database for reading only. Any attempt to modify items in the -database will fail regardless of the actual permissions of any underlying -files. -

DB_THREAD
Cause the DB handle returned by DB->open to be -free-threaded, that is, useable by multiple threads within a -single address space. -

DB_TRUNCATE
Physically truncate the underlying file, discarding all previous databases -it might have held. Underlying filesystem primitives are used to -implement this flag. For this reason it is only applicable to the -physical file and cannot be used to discard databases within a file. -

The DB_TRUNCATE flag cannot be transaction protected, and it is -an error to specify it in a transaction protected environment. -

-

On UNIX systems, or in IEEE/ANSI Std 1003.1 (POSIX) environments, all files created by the access methods -are created with mode mode (as described in chmod(2)) and -modified by the process' umask value at the time of creation (see -umask(2)). The group ownership of created files is based on -the system and directory defaults, and is not further specified by Berkeley DB. -If mode is 0, files are created readable and writeable by both -owner and group. On Windows systems, the mode argument is ignored. -

Calling DB->open is a reasonably expensive operation, and -maintaining a set of open databases will normally be preferable to -repeatedly open and closing the database for each new query. -

The DB->open function returns a non-zero error value on failure and 0 on success. -

Environment Variables

-

-

DB_HOME
If the dbenv argument to db_create was initialized using -DBENV->open the environment variable DB_HOME may be used -as the path of the database environment home. Specifically, DB->open -is affected by the configuration value DB_DATA_DIR. -
-

-

TMPDIR
If the file and dbenv arguments to DB->open are -NULL, the environment variable TMPDIR may be used as a -directory in which to create a temporary backing file. -
-

Errors

-

The DB->open function may fail and return a non-zero error for the following conditions: -

-

DB_OLD_VERSION
The database cannot be opened without being first upgraded. -

EEXIST
DB_CREATE and DB_EXCL were specified and the file exists. -

EINVAL
An invalid flag value or parameter was specified (e.g., unknown database -type, page size, hash function, pad byte, byte order) or a flag value -or parameter that is incompatible with the specified database. -

-The DB_THREAD flag was specified and spinlocks are not -implemented for this architecture. -

The DB_THREAD flag was specified to DB->open, but was not -specified to the DBENV->open call for the environment in which the -DB handle was created. -

A re_source file was specified with either the DB_THREAD -flag or the provided database environment supports transaction -processing. -

ENOENT
A non-existent re_source file was specified. -
-

The DB->open 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->open function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_put.html b/bdb/docs/api_c/db_put.html deleted file mode 100644 index 85c63b7cc7e..00000000000 --- a/bdb/docs/api_c/db_put.html +++ /dev/null @@ -1,136 +0,0 @@ - - - - - -Berkeley DB: DB->put - - - - - - - -
-

DB->put

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->put(DB *db,
-    DB_TXN *txnid, DBT *key, DBT *data, u_int32_t flags);
-

-

Description

-

The DB->put function stores key/data pairs in the database. The default -behavior of the DB->put function is to enter the new key/data -pair, replacing any previously existing key if duplicates are disallowed, -or adding a duplicate data item if duplicates are allowed. If the database -supports duplicates, the DB->put function adds the new data value at the -end of the duplicate set. If the database supports sorted duplicates, -the new data value is inserted at the correct sorted location. -

If the file is being accessed under transaction protection, the -txnid parameter is a transaction ID returned from -txn_begin, otherwise, NULL. -

The flags parameter must be set to 0 or one of the following -values: -

-

DB_APPEND
Append the key/data pair to the end of the database. For the -DB_APPEND flag to be specified, the underlying database must be -a Queue or Recno database. The record number allocated to the record is -returned in the specified key. -

There is a minor behavioral difference between the Recno and Queue access -methods for the DB_APPEND flag. If a transaction enclosing a -DB->put operation with the DB_APPEND flag aborts, the -record number may be decremented (and later re-allocated by a subsequent -DB_APPEND operation) by the Recno access method, but will not be -decremented or re-allocated by the Queue access method. -

DB_NODUPDATA
In the case of the Btree and Hash access methods, enter the new key/data -pair only if it does not already appear in the database. If the -key/data pair already appears in the database, DB_KEYEXIST is -returned. The DB_NODUPDATA flag may only be specified if the -underlying database has been configured to support sorted duplicates. -

The DB_NODUPDATA flag may not be specified to the Queue or Recno -access methods. -

DB_NOOVERWRITE
Enter the new key/data pair only if the key does not already appear in -the database. If the key already appears in the database, -DB_KEYEXIST is returned. Even if the database allows duplicates, -a call to DB->put with the DB_NOOVERWRITE flag set will -fail if the key already exists in the database. -
-

Otherwise, the DB->put function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DB->put function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

EACCES
An attempt was made to modify a read-only database. -
-

-

EINVAL
An invalid flag value or parameter was specified. -

A record number of 0 was specified. -

An attempt was made to add a record to a fixed-length database that was too -large to fit. -

An attempt was made to do a partial put. -

-

-

ENOSPC
A btree exceeded the maximum btree depth (255). -
-

The DB->put 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->put function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_remove.html b/bdb/docs/api_c/db_remove.html deleted file mode 100644 index e8dae864538..00000000000 --- a/bdb/docs/api_c/db_remove.html +++ /dev/null @@ -1,108 +0,0 @@ - - - - - -Berkeley DB: DB->remove - - - - - - - -
-

DB->remove

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->remove(DB *db,
-	const char *file, const char *database, u_int32_t flags);
-

-

Description

-

The DB->remove interface removes the database specified by the -file and database arguments. If no database is -specified, the physical file represented by file is removed, -incidentally removing all databases that it contained. -

If a physical 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. Otherwise, no reference count of database -use is maintained by Berkeley DB. Applications should not remove databases that -are currently in use. 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 will fail. -

The flags parameter is currently unused, and must be set to 0. -

Once 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. -

Environment Variables

-

-

DB_HOME
If the dbenv argument to db_create was initialized using -DBENV->open the environment variable DB_HOME may be used -as the path of the database environment home. Specifically, DB->remove -is affected by the configuration value DB_DATA_DIR. -
-

Errors

-

The DB->remove function may fail and return a non-zero error for the following conditions: -

-

EINVAL
A database in the file is currently open. -
-

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. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_rename.html b/bdb/docs/api_c/db_rename.html deleted file mode 100644 index ff90836c6b2..00000000000 --- a/bdb/docs/api_c/db_rename.html +++ /dev/null @@ -1,109 +0,0 @@ - - - - - -Berkeley DB: DB->rename - - - - - - - -
-

DB->rename

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->rename(DB *db, const char *file,
-	const char *database, const char *newname, u_int32_t flags);
-

-

Description

-

The DB->rename interface renames the database specified by the -file and database arguments to newname. If no -database is specified, the physical file represented by -file is renamed, incidentally renaming all databases that it -contained. -

If a physical file is being renamed and logging is currently enabled in -the database environment, no database in the file may be open when the -DB->rename function is called. Otherwise, no reference count of database -use is maintained by Berkeley DB. Applications should not rename databases that -are currently in use. In particular, some architectures do not permit -renaming files with open handles. On these architectures, attempts to -rename databases that are currently in use will fail. -

The flags parameter is currently unused, and must be set to 0. -

Once DB->rename has been called, regardless of its return, the -DB handle may not be accessed again. -

The DB->rename function returns a non-zero error value on failure and 0 on success. -

Environment Variables

-

-

DB_HOME
If the dbenv argument to db_create was initialized using -DBENV->open the environment variable DB_HOME may be used -as the path of the database environment home. Specifically, DB->rename -is affected by the configuration value DB_DATA_DIR. -
-

Errors

-

The DB->rename function may fail and return a non-zero error for the following conditions: -

-

EINVAL
A database in the file is currently open. -
-

The DB->rename 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->rename function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_append_recno.html b/bdb/docs/api_c/db_set_append_recno.html deleted file mode 100644 index 4b90190ffbd..00000000000 --- a/bdb/docs/api_c/db_set_append_recno.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - -Berkeley DB: DB->set_append_recno - - - - - - - -
-

DB->set_append_recno

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_append_recno(DB *,
-    int (*db_append_recno_fcn)(DB *dbp, DBT *data, db_recno_t recno));
-

-

Description

-

When using the DB_APPEND option of the DB->put method, -it may be useful to modify the stored data based on the generated key. -If a callback function is specified using the -DB->set_append_recno function, it will be called after the record number -has been selected but before the data has been stored. -The callback function must return 0 on success and errno or -a value outside of the Berkeley DB error name space on failure. -

The called function must take three arguments: a reference to the -enclosing database handle, the data DBT to be stored and the -selected record number. The called function may then modify the data -DBT. -

The DB->set_append_recno interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_append_recno function returns a non-zero error value on failure and 0 on success. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_bt_compare.html b/bdb/docs/api_c/db_set_bt_compare.html deleted file mode 100644 index bf38ee51d94..00000000000 --- a/bdb/docs/api_c/db_set_bt_compare.html +++ /dev/null @@ -1,105 +0,0 @@ - - - - - -Berkeley DB: DB->set_bt_compare - - - - - - - -
-

DB->set_bt_compare

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_bt_compare(DB *db,
-    int (*bt_compare_fcn)(DB *, const DBT *, const DBT *));
-

-

Description

-

Set the Btree key comparison function. The comparison function is -called when it is necessary to compare a key specified by the -application with a key currently stored in the tree. The first argument -to the comparison function is the DBT representing the -application supplied key, the second is the current tree's key. -

The comparison function must return an integer value less than, equal -to, or greater than zero if the first key argument is considered to be -respectively less than, equal to, or greater than the second key -argument. In addition, the comparison function must cause the keys in -the database to be well-ordered. The comparison function -must correctly handle any key values used by the application (possibly -including zero-length keys). In addition, when Btree key prefix -comparison is being performed (see DB->set_bt_prefix for more -information), the comparison routine may be passed a prefix of any -database key. The data and size fields of the -DBT are the only fields that may be used for the purposes of -this comparison. -

If no comparison function is specified, the keys are compared lexically, -with shorter keys collating before longer keys. The same comparison -method must be used each time a particular Btree is opened. -

The DB->set_bt_compare interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_bt_compare function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_bt_minkey.html b/bdb/docs/api_c/db_set_bt_minkey.html deleted file mode 100644 index c36f3637ba5..00000000000 --- a/bdb/docs/api_c/db_set_bt_minkey.html +++ /dev/null @@ -1,92 +0,0 @@ - - - - - -Berkeley DB: DB->set_bt_minkey - - - - - - - -
-

DB->set_bt_minkey

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_bt_minkey(DB *db, u_int32_t bt_minkey);
-

-

Description

-

Set the minimum number of keys that will be stored on any single -Btree page. -

This value is used to determine which keys will be stored on overflow -pages, i.e. if a key or data item is larger than the underlying database -page size divided by the bt_minkey value, it will be stored on -overflow pages instead of within the page itself. The bt_minkey -value specified must be at least 2; if bt_minkey is not explicitly -set, a value of 2 is used. -

The DB->set_bt_minkey interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_bt_minkey function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_bt_prefix.html b/bdb/docs/api_c/db_set_bt_prefix.html deleted file mode 100644 index 88bf3157f97..00000000000 --- a/bdb/docs/api_c/db_set_bt_prefix.html +++ /dev/null @@ -1,106 +0,0 @@ - - - - - -Berkeley DB: DB->set_bt_prefix - - - - - - - -
-

DB->set_bt_prefix

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_bt_prefix(DB *db,
-    size_t (*bt_prefix_fcn)(DB *, const DBT *, const DBT *));
-

-

Description

-

Set the Btree prefix function. The prefix function must return the -number of bytes of the second key argument that would be required by -the Btree key comparison function to determine the second key argument's -ordering relationship with respect to the first key argument. If the -two keys are equal, the key length should be returned. The prefix -function must correctly handle any key values used by the application -(possibly including zero-length keys). The data and -size fields of the DBT are the only fields that may be -used for the purposes of this determination. -

The prefix function is used to determine the amount by which keys stored -on the Btree internal pages can be safely truncated without losing their -uniqueness. See the Btree -prefix comparison section of the Reference Guide for more details about -how this works. The usefulness of this is data dependent, but in some -data sets can produce significantly reduced tree sizes and search times. -

If no prefix function or key comparison function is specified by the -application, a default lexical comparison function is used as the prefix -function. If no prefix function is specified and a key comparison -function is specified, no prefix function is used. It is an error to -specify a prefix function without also specifying a key comparison -function. -

The DB->set_bt_prefix interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_bt_prefix function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_cachesize.html b/bdb/docs/api_c/db_set_cachesize.html deleted file mode 100644 index fd7176cbf7d..00000000000 --- a/bdb/docs/api_c/db_set_cachesize.html +++ /dev/null @@ -1,107 +0,0 @@ - - - - - - -Berkeley DB: DB->set_cachesize - - - - - - - -
-

DB->set_cachesize

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_cachesize(DB *db,
-    u_int32_t gbytes, u_int32_t bytes, int ncache);
-

-

Description

-

Set the size of the database's shared memory buffer pool, i.e., the cache, -to gbytes gigabytes plus bytes. The cache should be the -size of the normal working data set of the application, with some small -amount of additional memory for unusual situations. (Note, the working -set is not the same as the number of simultaneously referenced pages, and -should be quite a bit larger!) -

The default cache size is 256KB, and may not be specified as less than -20KB. Any cache size less than 500MB is automatically increased by 25% -to account for buffer pool overhead, cache sizes larger than 500MB are -used as specified. For information on tuning the Berkeley DB cache size, see -Selecting a cache size. -

It is possible to specify caches to Berkeley DB that are large enough so that -they cannot be allocated contiguously on some architectures, e.g., some -releases of Solaris limit the amount of memory that may be allocated -contiguously by a process. If ncache is 0 or 1, the cache will -be allocated contiguously in memory. If it is greater than 1, the cache -will be broken up into ncache equally sized separate pieces of -memory. -

As databases opened within Berkeley DB environments use the cache specified to -the environment, it is an error to attempt to set a cache in a database -created within an environment. -

The DB->set_cachesize interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_cachesize function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

The specified cache size was impossibly small. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_dup_compare.html b/bdb/docs/api_c/db_set_dup_compare.html deleted file mode 100644 index 2ac6ed9dec2..00000000000 --- a/bdb/docs/api_c/db_set_dup_compare.html +++ /dev/null @@ -1,102 +0,0 @@ - - - - - -Berkeley DB: DB->set_dup_compare - - - - - - - -
-

DB->set_dup_compare

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_dup_compare(DB *db,
-    int (*dup_compare_fcn)(DB *, const DBT *, const DBT *));
-

-

Description

-

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. -

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 only be used 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. -

Errors

-

-

EINVAL
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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_errcall.html b/bdb/docs/api_c/db_set_errcall.html deleted file mode 100644 index 97d8d9a3aca..00000000000 --- a/bdb/docs/api_c/db_set_errcall.html +++ /dev/null @@ -1,76 +0,0 @@ - - - - - - -Berkeley DB: DB->set_errcall - - - - - - - -
-

DB->set_errcall

-		 -APIRef -
-

- -

-#include <db.h>
-

-void
-DB->set_errcall(DB *,
-    void (*db_errcall_fcn)(const char *errpfx, char *msg));
-

-

Description

-When an error occurs in the Berkeley DB library, a Berkeley DB error or an error -return value is returned by the function. In some cases, however, -the errno value may be insufficient to completely describe -the cause of the error especially during initial application debugging. -

The DB->set_errcall function is used to enhance the mechanism for reporting error -messages to the application. In some cases, when an error occurs, Berkeley DB -will call db_errcall_fcn with additional error information. The -function must be declared with two arguments; the first will be the prefix -string (as previously set by DB->set_errpfx or -DBENV->set_errpfx), the second will be the error message string. -It is up to the db_errcall_fcn function to display the error -message in an appropriate manner. -

Alternatively, you can use the DB->set_errfile or -DBENV->set_errfile functions to display the additional information -via a C library FILE *. -

This error logging enhancement does not slow performance or significantly -increase application size, and may be run during normal operation as well -as during application debugging. -

For DB handles opened inside of Berkeley DB environments, calling the -DB->set_errcall function affects the entire environment and is equivalent to calling -the DBENV->set_errcall function. -

The DB->set_errcall interface may be used to configure Berkeley DB at any time -during the life of the application. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_errfile.html b/bdb/docs/api_c/db_set_errfile.html deleted file mode 100644 index 5d160ed5cf2..00000000000 --- a/bdb/docs/api_c/db_set_errfile.html +++ /dev/null @@ -1,73 +0,0 @@ - - - - - - -Berkeley DB: DB->set_errfile - - - - - - - -
-

DB->set_errfile

-		 -APIRef -
-

- -

-#include <db.h>
-

-void
-DB->set_errfile(DB *db, FILE *errfile);
-

-

Description

-When an error occurs in the Berkeley DB library, a Berkeley DB error or an error -return value is returned by the function. In some cases, however, -the errno value may be insufficient to completely describe -the cause of the error especially during initial application debugging. -

The DB->set_errfile function is used to enhance the mechanism for reporting error -messages to the application by setting a C library FILE * to be used for -displaying additional Berkeley DB error messages. In some cases, when an error -occurs, Berkeley DB will output an additional error message to the specified -file reference. -

The error message will consist of the prefix string and a colon -(":") (if a prefix string was previously specified using -DB->set_errpfx or DBENV->set_errpfx), an error string, and -a trailing <newline> character. -

This error logging enhancement does not slow performance or significantly -increase application size, and may be run during normal operation as well -as during application debugging. -

For DB handles opened inside of Berkeley DB environments, calling the -DB->set_errfile function affects the entire environment and is equivalent to calling -the DBENV->set_errfile function. -

The DB->set_errfile interface may be used to configure Berkeley DB at any time -during the life of the application. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_errpfx.html b/bdb/docs/api_c/db_set_errpfx.html deleted file mode 100644 index baf8f61fef7..00000000000 --- a/bdb/docs/api_c/db_set_errpfx.html +++ /dev/null @@ -1,62 +0,0 @@ - - - - - -Berkeley DB: DB->set_errpfx - - - - - - - -
-

DB->set_errpfx

-		 -APIRef -
-

- -

-#include <db.h>
-

-void
-DB->set_errpfx(DB *db, const char *errpfx);
-

-

Description

-

Set the prefix string that appears before error messages issued by Berkeley DB. -

The DB->set_errpfx function does not copy the memory referenced by the -errpfx argument, rather, it maintains a reference to it. This -allows applications to modify the error message prefix at any time, -without repeatedly calling DB->set_errpfx, but means that the -memory must be maintained until the handle is closed. -

For DB handles opened inside of Berkeley DB environments, calling the -DB->set_errpfx function affects the entire environment and is equivalent to calling -the DBENV->set_errpfx function. -

The DB->set_errpfx interface may be used to configure Berkeley DB at any time -during the life of the application. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_feedback.html b/bdb/docs/api_c/db_set_feedback.html deleted file mode 100644 index 213060ee765..00000000000 --- a/bdb/docs/api_c/db_set_feedback.html +++ /dev/null @@ -1,95 +0,0 @@ - - - - - -Berkeley DB: DB->set_feedback - - - - - - - -
-

DB->set_feedback

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_feedback(DB *,
-    void (*db_feedback_fcn)(DB *dbp, int opcode, int pct));
-

-

Description

-

Some operations performed by the Berkeley DB library can take non-trivial -amounts of time. The DB->set_feedback function can be used by -applications to monitor progress within these operations. -

When an operation is likely to take a long time, Berkeley DB will call the -specified callback function. This function must be declared with -three arguments: the first will be a reference to the enclosing database -handle, the second a flag value, and the third the percent of the -operation that has been completed, specified as an integer value between -0 and 100. It is up to the callback function to display this -information in an appropriate manner. -

The opcode argument may take on any of the following values: -

-

DB_UPGRADE
The underlying database is being upgraded. -

DB_VERIFY
The underlying database is being verified. -
-

The DB->set_feedback interface may be used to configure Berkeley DB at any time -during the life of the application. -

The DB->set_feedback function returns a non-zero error value on failure and 0 on success. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_flags.html b/bdb/docs/api_c/db_set_flags.html deleted file mode 100644 index f1823381776..00000000000 --- a/bdb/docs/api_c/db_set_flags.html +++ /dev/null @@ -1,181 +0,0 @@ - - - - - -Berkeley DB: DB->set_flags - - - - - - - -
-

DB->set_flags

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_flags(DB *db, u_int32_t flags);
-

-

Description

-

Calling DB->set_flags is additive, there is no way to clear flags. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

Btree

-

The following flags may be specified for the Btree access method: -

-

DB_DUP
Permit duplicate data items in the tree, i.e. insertion when the key of -the key/data pair being inserted already exists in the tree will be -successful. The ordering of duplicates in the tree is determined by the -order of insertion, unless the ordering is otherwise specified by use of -a cursor operation. It is an error to specify both DB_DUP and -DB_RECNUM. -

DB_DUPSORT
Permit duplicate data items in the tree, i.e. insertion when the key of -the key/data pair being inserted already exists in the tree will be -successful. The ordering of duplicates in the tree is determined by the -duplicate comparison function. -If the application does not specify a comparison function using the -DB->set_dup_compare function, a default, lexical comparison will be -used. -It is an error to specify both DB_DUPSORT and DB_RECNUM. -

DB_RECNUM
Support retrieval from the Btree using record numbers. For more -information, see the DB_GET_RECNO flag to the DB->get and -DBcursor->c_get methods. -

Logical record numbers in Btree databases are mutable in the face of -record insertion or deletion. See the DB_RENUMBER flag in the Recno -access method information for further discussion. -

Maintaining record counts within a Btree introduces a serious point of -contention, namely the page locations where the record counts are stored. -In addition, the entire tree must be locked during both insertions and -deletions, effectively single-threading the tree for those operations. -Specifying DB_RECNUM can result in serious performance degradation for -some applications and data sets. -

It is an error to specify both DB_DUP and DB_RECNUM. -

DB_REVSPLITOFF
Turn off reverse splitting in the Btree. As pages are emptied in a -database, the Berkeley DB Btree implementation attempts to coalesce empty pages -into higher-level pages in order to keep the tree as small as possible -and minimize tree search time. This can hurt performance in applications -with cyclical data demands, that is, applications where the database grows -and shrinks repeatedly. For example, because Berkeley DB does page-level -locking, the maximum level of concurrency in a database of 2 pages is far -smaller than that in a database of 100 pages, and so a database that has -shrunk to a minimal size can cause severe deadlocking when a new cycle of -data insertion begins. -
-

Hash

-

The following flags may be specified for the Hash access method: -

-

DB_DUP
Permit duplicate data items in the tree, i.e. insertion when the key of -the key/data pair being inserted already exists in the tree will be -successful. The ordering of duplicates in the tree is determined by the -order of insertion, unless the ordering is otherwise specified by use of -a cursor operation. It is an error to specify both DB_DUP and -DB_RECNUM. -

DB_DUPSORT
Permit duplicate data items in the tree, i.e. insertion when the key of -the key/data pair being inserted already exists in the tree will be -successful. The ordering of duplicates in the tree is determined by the -duplicate comparison function. -If the application does not specify a comparison function using the -DB->set_dup_compare function, a default, lexical comparison will be -used. -It is an error to specify both DB_DUPSORT and DB_RECNUM. -
-

Queue

-

There are no additional flags that may be specified for the Queue access -method. -

Recno

-

The following flags may be specified for the Recno access method: -

-

DB_RENUMBER
Specifying the DB_RENUMBER flag causes the logical record numbers to be -mutable, and change as records are added to and deleted from the database. -For example, the deletion of record number 4 causes records numbered 5 -and greater to be renumbered downward by 1. If a cursor was positioned -to record number 4 before the deletion, it will reference the new record -number 4, if any such record exists, after the deletion. If a cursor was -positioned after record number 4 before the deletion, it will be shifted -downward 1 logical record, continuing to reference the same record as it -did before. -

Using the DB->put or DBcursor->c_put interfaces to create new -records will cause the creation of multiple records if the record number -is more than one greater than the largest record currently in the -database. For example, creating record 28, when record 25 was previously -the last record in the database, will create records 26 and 27 as well as -28. Attempts to retrieve records that were created in this manner will -result in an error return of DB_KEYEMPTY. -

If a created record is not at the end of the database, all records -following the new record will be automatically renumbered upward by 1. -For example, the creation of a new record numbered 8 causes records -numbered 8 and greater to be renumbered upward by 1. If a cursor was -positioned to record number 8 or greater before the insertion, it will be -shifted upward 1 logical record, continuing to reference the same record -as it did before. -

For these reasons, concurrent access to a Recno database with the -DB_RENUMBER flag specified may be largely meaningless, although -it is supported. -

DB_SNAPSHOT
This flag specifies that any specified re_source file be read in -its entirety when DB->open is called. If this flag is not -specified, the re_source file may be read lazily. -
-

The DB->set_flags interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_flags function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_h_ffactor.html b/bdb/docs/api_c/db_set_h_ffactor.html deleted file mode 100644 index c3bbb607ea5..00000000000 --- a/bdb/docs/api_c/db_set_h_ffactor.html +++ /dev/null @@ -1,93 +0,0 @@ - - - - - -Berkeley DB: DB->set_h_ffactor - - - - - - - -
-

DB->set_h_ffactor

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_h_ffactor(DB *db, u_int32_t h_ffactor);
-

-

Description

-

Set the desired density within the hash table. -

The density is an approximation of the number of keys allowed to -accumulate in any one bucket, determining when the hash table grows or -shrinks. If you know the average sizes of the keys and data in your -dataset, setting the fill factor can enhance performance. A reasonable -rule computing fill factor is to set it to: -

(pagesize - 32) / (average_key_size + average_data_size + 8)
-

If no value is specified, the fill factor will be selected dynamically as -pages are filled. -

The DB->set_h_ffactor interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_h_ffactor function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_h_hash.html b/bdb/docs/api_c/db_set_h_hash.html deleted file mode 100644 index cae03fa72b3..00000000000 --- a/bdb/docs/api_c/db_set_h_hash.html +++ /dev/null @@ -1,97 +0,0 @@ - - - - - -Berkeley DB: DB->set_h_hash - - - - - - - -
-

DB->set_h_hash

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_h_hash(DB *db,
-    u_int32_t (*h_hash_fcn)(DB *, const void *bytes, u_int32_t length));
-

-

Description

-

Set a user defined hash method; if no hash method is specified, a default -hash method is used. Since no hash method performs equally well on all -possible data, the user may find that the built-in hash method performs -poorly with a particular data set. User specified hash functions must -take a pointer to a byte string and a length as arguments and return a -value of type -u_int32_t. -The hash function must handle any key values used by the application -(possibly including zero-length keys). -

If a hash method is specified, DB->open will attempt to determine -if the hash method specified is the same as the one with which the database -was created, and will fail if it detects that it is not. -

The DB->set_h_hash interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_h_hash function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_h_nelem.html b/bdb/docs/api_c/db_set_h_nelem.html deleted file mode 100644 index d052afff7dc..00000000000 --- a/bdb/docs/api_c/db_set_h_nelem.html +++ /dev/null @@ -1,88 +0,0 @@ - - - - - -Berkeley DB: DB->set_h_nelem - - - - - - - -
-

DB->set_h_nelem

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_h_nelem(DB *db, u_int32_t h_nelem);
-

-

Description

-

Set an estimate of the final size of the hash table. -

If not set or set too low, hash tables will still expand gracefully -as keys are entered, although a slight performance degradation may be -noticed. -

The DB->set_h_nelem interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_h_nelem function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_lorder.html b/bdb/docs/api_c/db_set_lorder.html deleted file mode 100644 index a9a3c923037..00000000000 --- a/bdb/docs/api_c/db_set_lorder.html +++ /dev/null @@ -1,94 +0,0 @@ - - - - - -Berkeley DB: DB->set_lorder - - - - - - - -
-

DB->set_lorder

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_lorder(DB *db, int lorder);
-

-

Description

-

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. -

Errors

-

-

EINVAL
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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_malloc.html b/bdb/docs/api_c/db_set_malloc.html deleted file mode 100644 index 2d13196a3ad..00000000000 --- a/bdb/docs/api_c/db_set_malloc.html +++ /dev/null @@ -1,98 +0,0 @@ - - - - - -Berkeley DB: DB->set_malloc - - - - - - - -
-

DB->set_malloc

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_malloc(DB *db, void *(*db_malloc)(size_t size));
-

-

Description

-

Set the allocation function used by the DB methods to allocate -memory in which to return key/data items to the application. -

The DB_DBT_MALLOC flag, when specified in the DBT object, -will cause the DB methods to allocate and re-allocate memory which -then becomes the responsibility of the calling application. See DBT -for more information. -

On systems where there may be multiple library versions of malloc (notably -Windows NT), specifying the DB_DBT_MALLOC flag will fail because -the DB library will allocate memory from a different heap than -the application will use to free it. To avoid this problem, the -DB->set_malloc function can be used to pass Berkeley DB a reference to the -application's allocation routine, in which case it will be used to -allocate the memory returned when the DB_DBT_MALLOC flag is set. -

The function specified must match the calling conventions of the -ANSI C X3.159-1989 (ANSI C) library routine of the same name. -

The DB->set_malloc interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_malloc function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_pagesize.html b/bdb/docs/api_c/db_set_pagesize.html deleted file mode 100644 index 7fa4af53dbc..00000000000 --- a/bdb/docs/api_c/db_set_pagesize.html +++ /dev/null @@ -1,90 +0,0 @@ - - - - - -Berkeley DB: DB->set_pagesize - - - - - - - -
-

DB->set_pagesize

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_pagesize(DB *db, u_int32_t pagesize);
-

-

Description

-

Set the size of the pages used to hold items in the database, in bytes. -The minimum page size is 512 bytes and the maximum page size is 64K bytes. -If the page size is not explicitly set, one is selected based on the -underlying filesystem I/O block size. The automatically selected size -has a lower limit of 512 bytes and an upper limit of 16K bytes. -

For information on tuning the Berkeley DB page size, see -Selecting a page size. -

The DB->set_pagesize interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_pagesize function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_paniccall.html b/bdb/docs/api_c/db_set_paniccall.html deleted file mode 100644 index 506272c9630..00000000000 --- a/bdb/docs/api_c/db_set_paniccall.html +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - -Berkeley DB: DB->set_paniccall - - - - - - - -
-

DB->set_paniccall

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_paniccall(DB *db,
-    void (*paniccall)(DB_ENV *, int errval));
-

-

Description

-

Errors can occur in the Berkeley DB library where the only solution is to shut -down the application and run recovery. (For example, if Berkeley DB is unable -to write log records to disk because there is insufficient disk space.) -In these cases, the value DB_RUNRECOVERY is returned by Berkeley DB. -

In these cases, it is also often simpler to shut down the application when -such errors occur rather than attempting to gracefully return up the stack. -The DB->set_paniccall function is used to specify a function to be called when -DB_RUNRECOVERY is about to be returned from a Berkeley DB method. When -called, the dbenv argument will be a reference to the current -environment, and the errval argument is the error value that would -have been returned to the calling function. -

For DB handles opened inside of Berkeley DB environments, calling the -DB->set_paniccall function affects the entire environment and is equivalent to calling -the DBENV->set_paniccall function. -

The DB->set_paniccall interface may be used to configure Berkeley DB at any time -during the life of the application. -

The DB->set_paniccall function returns a non-zero error value on failure and 0 on success. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_q_extentsize.html b/bdb/docs/api_c/db_set_q_extentsize.html deleted file mode 100644 index 7ab89bdba5d..00000000000 --- a/bdb/docs/api_c/db_set_q_extentsize.html +++ /dev/null @@ -1,90 +0,0 @@ - - - - - -Berkeley DB: DB->set_q_extentsize - - - - - - - -
-

DB->set_q_extentsize

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_q_extentsize(DB *db, u_int32_t extentsize);
-

-

Description

-

Set the size of the extents used to hold pages in a Queue database, -specified as a number of pages. Each extent is created as a separate -physical file. If no extent size is set, the default behavior is to -create only a single underlying database file. -

For information on tuning the extent size, see -Selecting a extent size. -

The DB->set_q_extentsize interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_q_extentsize function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_re_delim.html b/bdb/docs/api_c/db_set_re_delim.html deleted file mode 100644 index 6101130a5e5..00000000000 --- a/bdb/docs/api_c/db_set_re_delim.html +++ /dev/null @@ -1,90 +0,0 @@ - - - - - -Berkeley DB: DB->set_re_delim - - - - - - - -
-

DB->set_re_delim

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_re_delim(DB *db, int re_delim);
-

-

Description

-

Set the delimiting byte used to mark the end of a record in the backing -source file for the Recno access method. -

This byte is used for variable length records, if the re_source -file is specified. If the re_source file is specified and no -delimiting byte was specified, <newline> characters (i.e. -ASCII 0x0a) are interpreted as end-of-record markers. -

The DB->set_re_delim interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_re_delim function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_re_len.html b/bdb/docs/api_c/db_set_re_len.html deleted file mode 100644 index 67b67ddfc0a..00000000000 --- a/bdb/docs/api_c/db_set_re_len.html +++ /dev/null @@ -1,94 +0,0 @@ - - - - - -Berkeley DB: DB->set_re_len - - - - - - - -
-

DB->set_re_len

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_re_len(DB *db, u_int32_t re_len);
-

-

Description

-

For the Queue access method, specify that the records are of length -re_len. -

For the Recno access method, specify that the records are fixed-length, -not byte delimited, and are of length re_len. -

Any records added to the database that are less than re_len bytes -long are automatically padded (see DB->set_re_pad for more -information). -

Any attempt to insert records into the database that are greater than -re_len bytes long will cause the call to fail immediately and -return an error. -

The DB->set_re_len interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_re_len function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_re_pad.html b/bdb/docs/api_c/db_set_re_pad.html deleted file mode 100644 index 43a6f947f5d..00000000000 --- a/bdb/docs/api_c/db_set_re_pad.html +++ /dev/null @@ -1,88 +0,0 @@ - - - - - -Berkeley DB: DB->set_re_pad - - - - - - - -
-

DB->set_re_pad

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_re_pad(DB *db, int re_pad);
-

-

Description

-

Set the padding character for short, fixed-length records for the Queue -and Recno access methods. -

If no pad character is specified, <space> characters (i.e., -ASCII 0x20) are used for padding. -

The DB->set_re_pad interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_re_pad function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_re_source.html b/bdb/docs/api_c/db_set_re_source.html deleted file mode 100644 index 1a57cfea339..00000000000 --- a/bdb/docs/api_c/db_set_re_source.html +++ /dev/null @@ -1,130 +0,0 @@ - - - - - -Berkeley DB: DB->set_re_source - - - - - - - -
-

DB->set_re_source

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_re_source(DB *db, char *re_source);
-

-

Description

-

Set the underlying source file for the Recno access method. The purpose -of the re_source value is to provide fast access and modification -to databases that are normally stored as flat text files. -

If the re_source field is set, it specifies an underlying flat -text database file that is read to initialize a transient record number -index. In the case of variable length records, the records are separated -as specified by DB->set_re_delim. For example, standard UNIX -byte stream files can be interpreted as a sequence of variable length -records separated by <newline> characters. -

In addition, when cached data would normally be written back to the -underlying database file (e.g., the DB->close or DB->sync -methods are called), the in-memory copy of the database will be written -back to the re_source file. -

By default, the backing source file is read lazily, i.e., records are not -read from the file until they are requested by the application. -If multiple processes (not threads) are accessing a Recno database -concurrently and either inserting or deleting records, the backing source -file must be read in its entirety before more than a single process -accesses the database, and only that process should specify the backing -source file as part of the DB->open call. See the DB_SNAPSHOT -flag for more information. -

Reading and writing the backing source file specified by re_source -cannot be transactionally protected because it involves filesystem -operations that are not part of the Db transaction methodology. -For this reason, if a temporary database is used to hold the records, -i.e., a NULL was specified as the file argument to DB->open, -it is possible to lose the contents of the re_source file, e.g., -if the system crashes at the right instant. -If a file is used to hold the database, i.e., a file name was specified -as the file argument to DB->open, normal database -recovery on that file can be used to prevent information loss, -although it is still possible that the contents of re_source -will be lost if the system crashes. -

The re_source file must already exist (but may be zero-length) when -DB->open is called. -

It is not an error to specify a read-only re_source file when -creating a database, nor is it an error to modify the resulting database. -However, any attempt to write the changes to the backing source file using -either the DB->sync or DB->close functions will fail, of course. -Specify the DB_NOSYNC flag to the DB->close function to stop it -from attempting to write the changes to the backing file, instead, they -will be silently discarded. -

For all of the above reasons, the re_source field is generally -used to specify databases that are read-only for DB applications, -and that are either generated on the fly by software tools, or modified -using a different mechanism, e.g., a text editor. -

The DB->set_re_source interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_re_source function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DB->open was called. -

-

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_set_realloc.html b/bdb/docs/api_c/db_set_realloc.html deleted file mode 100644 index b3d8a05f771..00000000000 --- a/bdb/docs/api_c/db_set_realloc.html +++ /dev/null @@ -1,99 +0,0 @@ - - - - - -Berkeley DB: DB->set_realloc - - - - - - - -
-

DB->set_realloc

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->set_realloc(DB *db,
-    void *(*db_realloc_fcn)(void *ptr, size_t size));
-

-

Description

-

Set the realloc function used by the DB methods to allocate memory -in which to return key/data items to the application. -

The DB_DBT_REALLOC flag, when specified in the DBT object, -will cause the DB methods to allocate and re-allocate memory which -then becomes the responsibility of the calling application. See DBT -for more information. -

On systems where there may be multiple library versions of realloc (notably -Windows NT), specifying the DB_DBT_REALLOC flag will fail because -the DB library will allocate memory from a different heap than -the application will use to free it. To avoid this problem, the -DB->set_realloc function can be used to pass Berkeley DB a reference to the -application's allocation routine, in which case it will be used to -allocate the memory returned when the DB_DBT_REALLOC flag is set. -

The function specified must match the calling conventions of the -ANSI C X3.159-1989 (ANSI C) library routine of the same name. -

The DB->set_realloc interface may only be used to configure Berkeley DB before -the DB->open interface is called. -

The DB->set_realloc function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_stat.html b/bdb/docs/api_c/db_stat.html deleted file mode 100644 index 92412d76d78..00000000000 --- a/bdb/docs/api_c/db_stat.html +++ /dev/null @@ -1,195 +0,0 @@ - - - - - -Berkeley DB: DB->stat - - - - - - - -
-

DB->stat

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->stat(DB *db,
-	void *sp, void *(*db_malloc)(size_t), u_int32_t flags);
-

-

Description

-

The DB->stat function creates a statistical structure and -copies a pointer to it into user-specified memory locations. -Specifically, if sp is non-NULL, a pointer to the statistics -for the database are copied into the memory location it references. -

Statistical structures are created in allocated memory. If db_malloc is non-NULL, it -is called to allocate the memory, otherwise, the library function -malloc(3) is used. The function db_malloc must match -the calling conventions of the malloc(3) library routine. -Regardless, the caller is responsible for deallocating the returned -memory. To deallocate returned memory, free the returned memory -reference, references inside the returned memory do not need to be -individually freed. -

The flags parameter must be set to 0 or the following value: -

-

DB_CACHED_COUNTS
Return a cached count of the keys and records in a database. This flag -makes it possible for applications to request an possibly approximate key -and record count without incurring the performance penalty of traversing -the entire database. The statistics information described for the access -method XX_nkeys and XX_ndata fields below is filled in, -but no other information is collected. If the cached information has -never been set, the fields will be returned set to 0. -

DB_RECORDCOUNT
Return a count of the records in a Btree or Recno Access Method database. -This flag makes it possible for applications to request a record count -without incurring the performance penalty of traversing the entire -database. The statistics information described for the bt_nkeys -field below is filled in, but no other information is collected. -

This option is only available for Recno databases, or Btree databases -where the underlying database was created with the DB_RECNUM -flag. -

-

The DB->stat function may access all of the pages in the database, -incurring a severe performance penalty as well as possibly flushing the -underlying buffer pool. -

In the presence of multiple threads or processes accessing an active -database, the information returned by DB->stat may be out-of-date. -

If the database was not opened readonly and the DB_CACHED_COUNTS -flag was not specified, the cached key and record numbers will be updated -after the statistical information has been gathered. -

The DB->stat function cannot be transaction protected. For this reason, -it should be called in a thread of control that has no open cursors or -active transactions. -

The DB->stat function returns a non-zero error value on failure and 0 on success. -

Hash Statistics

-

In the case of a Hash database, -the statistics are stored in a structure of type DB_HASH_STAT. The -following fields will be filled in: -

-

u_int32_t hash_magic;
Magic number that identifies the file as a Hash file. -
u_int32_t hash_version;
The version of the Hash database. -
u_int32_t hash_nkeys;
The number of unique keys in the database. -
u_int32_t hash_ndata;
The number of key/data pairs in the database.] -
u_int32_t hash_pagesize;
The underlying Hash database page (and bucket) size. -
u_int32_t hash_nelem;
The estimated size of the hash table specified at database creation time. -
u_int32_t hash_ffactor;
The desired fill factor (number of items per bucket) specified at database -creation time. -
u_int32_t hash_buckets;
The number of hash buckets. -
u_int32_t hash_free;
The number of pages on the free list. -
u_int32_t hash_bfree;
The number of bytes free on bucket pages. -
u_int32_t hash_bigpages;
The number of big key/data pages. -
u_int32_t hash_big_bfree;
The number of bytes free on big item pages. -
u_int32_t hash_overflows;
The number of overflow pages (overflow pages are pages that contain items -that did not fit in the main bucket page). -
u_int32_t hash_ovfl_free;
The number of bytes free on overflow pages. -
u_int32_t hash_dup;
The number of duplicate pages. -
u_int32_t hash_dup_free;
The number of bytes free on duplicate pages. -
-

Btree and Recno Statistics

-

In the case of a Btree or Recno database, -the statistics are stored in a structure of type DB_BTREE_STAT. The -following fields will be filled in: -

-

u_int32_t bt_magic;
Magic number that identifies the file as a Btree database. -
u_int32_t bt_version;
The version of the Btree database. -
u_int32_t bt_nkeys;
For the Btree Access Method, the number of unique keys in the database. -

For the Recno Access Method, the number of records in the database. -

u_int32_t bt_ndata;
For the Btree Access Method, the number of key/data pairs in the database. -

For the Recno Access Method, the number of records in the database. If -the database has been configured to not re-number records during -deletion, the number of records will only reflect undeleted records. -

u_int32_t bt_pagesize;
Underlying database page size. -
u_int32_t bt_minkey;
The minimum keys per page. -
u_int32_t bt_re_len;
The length of fixed-length records. -
u_int32_t bt_re_pad;
The padding byte value for fixed-length records. -
u_int32_t bt_levels;
Number of levels in the database. -
u_int32_t bt_int_pg;
Number of database internal pages. -
u_int32_t bt_leaf_pg;
Number of database leaf pages. -
u_int32_t bt_dup_pg;
Number of database duplicate pages. -
u_int32_t bt_over_pg;
Number of database overflow pages. -
u_int32_t bt_free;
Number of pages on the free list. -
u_int32_t bt_int_pgfree;
Number of bytes free in database internal pages. -
u_int32_t bt_leaf_pgfree;
Number of bytes free in database leaf pages. -
u_int32_t bt_dup_pgfree;
Number of bytes free in database duplicate pages. -
u_int32_t bt_over_pgfree;
Number of bytes free in database overflow pages. -
-

Queue Statistics

-

In the case of a Queue database, -the statistics are stored in a structure of type DB_QUEUE_STAT. The -following fields will be filled in: -

-

u_int32_t qs_magic;
Magic number that identifies the file as a Queue file. -
u_int32_t qs_version;
The version of the Queue file type. -
u_int32_t qs_nkeys;
The number of records in the database. -
u_int32_t qs_ndata;
The number of records in the database. -
u_int32_t qs_pagesize;
Underlying database page size. -
u_int32_t qs_pages;
Number of pages in the database. -
u_int32_t qs_re_len;
The length of the records. -
u_int32_t qs_re_pad;
The padding byte value for the records. -
u_int32_t qs_pgfree;
Number of bytes free in database pages. -
u_int32_t qs_start;
Start offset. -
u_int32_t qs_first_recno;
First undeleted record in the database. -
u_int32_t qs_cur_recno;
Last allocated record number in the database. -
-

The DB->stat function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DB->stat 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->stat function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_sync.html b/bdb/docs/api_c/db_sync.html deleted file mode 100644 index 6af624a88f3..00000000000 --- a/bdb/docs/api_c/db_sync.html +++ /dev/null @@ -1,98 +0,0 @@ - - - - - -Berkeley DB: DB->sync - - - - - - - -
-

DB->sync

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->sync(DB *db, u_int32_t flags);
-

-

Description

-

The DB->sync function flushes any cached information to disk. -

If the database is in memory only, the DB->sync function has no effect and -will always succeed. -

The flags parameter is currently unused, and must be set to 0. -

See DB->close for a discussion of Berkeley DB and cached data. -

The DB->sync function returns a non-zero error value on failure, 0 on success, and returns DB_INCOMPLETE if the underlying database still has -dirty pages in the cache. (The only reason to return -DB_INCOMPLETE is if another thread of control was writing pages -in the underlying database file at the same time as the -DB->sync function was being called. For this reason, a return of -DB_INCOMPLETE can normally be ignored, or, in cases where it is -a possible return value, there may be no reason to call -DB->sync.) -

Errors

-

The DB->sync function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The DB->sync 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->sync function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_upgrade.html b/bdb/docs/api_c/db_upgrade.html deleted file mode 100644 index e31b4d447af..00000000000 --- a/bdb/docs/api_c/db_upgrade.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - -Berkeley DB: DB->upgrade - - - - - - - -
-

DB->upgrade

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->upgrade(DB *db, const char *file, u_int32_t flags);
-

-

Description

-

The DB->upgrade function upgrades all of the databases included in the -file file, if necessary. If no upgrade is necessary, -DB->upgrade always returns success. -

Database upgrades are done in place and are destructive, e.g., if pages -need to be allocated and no disk space is available, the database may be -left corrupted. Backups should be made before databases are upgraded. -See Upgrading databases for more -information. -

Unlike all other database operations, DB->upgrade may only be done -on a system with the same byte-order as the database. -

The flags parameter must be set to 0 or one of the following -values: -

-

DB_DUPSORT
This flag is only meaningful when upgrading databases from -releases before the Berkeley DB 3.1 release. -

As part of the upgrade from the Berkeley DB 3.0 release to the 3.1 release, the -on-disk format of duplicate data items changed. To correctly upgrade the -format requires applications specify if duplicate data items in the -database are sorted or not. Specifying the DB_DUPSORT flag -informs DB->upgrade that the duplicates are sorted, otherwise they -are assumed to be unsorted. Incorrectly specifying the value of this flag -may lead to database corruption. -

Further, because the DB->upgrade function upgrades a physical file -(including all of the databases it contains), it is not possible to use -DB->upgrade to upgrade files where some of the databases it -includes have sorted duplicate data items and some of the databases it -includes have unsorted duplicate data items. If the file does not have -more than a single database, or the databases do not support duplicate -data items, or all of the databases that support duplicate data items -support the same style of duplicates (either sorted or unsorted), -DB->upgrade will work correctly as long as the DB_DUPSORT -flag is correctly specified. Otherwise, the file cannot be upgraded using -DB->upgrade, and must be upgraded manually by dumping and -re-loading the databases. -

-

The DB->upgrade function returns a non-zero error value on failure and 0 on success. -

The DB->upgrade function is the underlying function used by the db_upgrade utility. -See the db_upgrade utility source code for an example of using DB->upgrade -in a IEEE/ANSI Std 1003.1 (POSIX) environment. -

Environment Variables

-

-

DB_HOME
If the dbenv argument to db_create was initialized using -DBENV->open the environment variable DB_HOME may be used -as the path of the database environment home. Specifically, DB->upgrade -is affected by the configuration value DB_DATA_DIR. -
-

Errors

-

The DB->upgrade function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -

The database is not in the same byte-order as the system. -

-

-

DB_OLD_VERSION
The database cannot be upgraded by this version of the Berkeley DB software. -
-

The DB->upgrade 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->upgrade function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/db_verify.html b/bdb/docs/api_c/db_verify.html deleted file mode 100644 index d011d90ab8d..00000000000 --- a/bdb/docs/api_c/db_verify.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - -Berkeley DB: DB->verify - - - - - - - -
-

DB->verify

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DB->verify(DB *db, const char *file,
-    const char *database, FILE *outfile, u_int32_t flags);
-

-

Description

-

The DB->verify function verifies the integrity of all databases in the -file specified by the file argument, and optionally outputs the databases' -key/data pairs to a file stream. -

The flags parameter must be set to 0 or one of the following -values: -

-

DB_SALVAGE
Write the key/data pairs from all databases in the file to the file stream -named in -the outfile argument. The output format is the same as that -specified for the db_dump utility and can be used as input for -the db_load utility. -

Because the key/data pairs are output in page order as opposed to the sort -order used by db_dump, using DB->verify to dump key/data -pairs normally produces less than optimal loads for Btree databases. -

-

In addition, the following flags may be set by bitwise inclusively OR'ing them into the -flags parameter: -

-

DB_AGGRESSIVE
Output all the key/data pairs in the file that can be found. -By default, DB->verify does not assume corruption. For example, -if a key/data pair on a page is marked as deleted, it is not then written -to the output file. When DB_AGGRESSIVE is specified, corruption -is assumed, and any key/data pair that can be found is written. In this -case, key/data pairs that are corrupted or have been deleted may appear -in the output (even if the file being salvaged is in no way corrupt), and -the output will almost certainly require editing before being loaded into -a database. -

DB_NOORDERCHK
Skip the database checks for btree and duplicate sort order and for -hashing. -

The DB->verify function normally verifies that btree keys and duplicate -items are correctly sorted and hash keys are correctly hashed. If the -file being verified contains multiple databases using differing sorting -or hashing algorithms, some of them must necessarily fail database -verification as only one sort order or hash function can be specified -before DB->verify is called. To verify files with multiple -databases having differing sorting orders or hashing functions, first -perform verification of the file as a whole by using the -DB_NOORDERCHK flag, and then individually verify the sort order -and hashing function for each database in the file using the -DB_ORDERCHKONLY flag. -

DB_ORDERCHKONLY
Perform the database checks for btree and duplicate sort order and for -hashing, skipped by DB_NOORDERCHK. -

When this flag is specified, a database argument should also be -specified, indicating the database in the physical file which is to be -checked. This flag is only safe to use on databases that have already -successfully been verified using DB->verify with the -DB_NOORDERCHK flag set. -

-

The database argument must be set to NULL except when the -DB_ORDERCHKONLY flag is set. -

The DB->verify function returns a non-zero error value on failure, 0 on success, and DB_VERIFY_BAD if a database is corrupted. When the -DB_SALVAGE flag is specified, the DB_VERIFY_BAD return -means that all key/data pairs in the file may not have been successfully -output. -

The DB->verify function is the underlying function used by the db_verify utility. -See the db_verify utility source code for an example of using DB->verify -in a IEEE/ANSI Std 1003.1 (POSIX) environment. -

Environment Variables

-

-

DB_HOME
If the dbenv argument to db_create was initialized using -DBENV->open the environment variable DB_HOME may be used -as the path of the database environment home. Specifically, DB->verify -is affected by the configuration value DB_DATA_DIR. -
-

Errors

-

The DB->verify function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The DB->verify 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->verify function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

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. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/dbc_close.html b/bdb/docs/api_c/dbc_close.html deleted file mode 100644 index 20eb28d953d..00000000000 --- a/bdb/docs/api_c/dbc_close.html +++ /dev/null @@ -1,64 +0,0 @@ - - - - - -Berkeley DB: DBcursor->c_close - - - - - - - -
-

DBcursor->c_close

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBcursor->c_close(DBC *cursor);
-

-

Description

-

The DBcursor->c_close function discards the cursor. -

It is possible for the DBcursor->c_close function to return -DB_LOCK_DEADLOCK, signaling that any enclosing transaction should -be aborted. If the application is already intending to abort the -transaction, this error should be ignored, and the application should -proceed. -

Once DBcursor->c_close has been called, regardless of its return, the -cursor handle may not be used again. -

The DBcursor->c_close function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DBcursor->c_close function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

EINVAL
An invalid flag value or parameter was specified. -

The cursor was previously closed. -

-

The DBcursor->c_close 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 DBcursor->c_close function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBcursor->c_close, -DBcursor->c_count, -DBcursor->c_del, -DBcursor->c_dup, -DBcursor->c_get -and -DBcursor->c_put. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/dbc_count.html b/bdb/docs/api_c/dbc_count.html deleted file mode 100644 index 434a0ce8cbb..00000000000 --- a/bdb/docs/api_c/dbc_count.html +++ /dev/null @@ -1,55 +0,0 @@ - - - - - -Berkeley DB: DBcursor->c_count - - - - - - - -
-

DBcursor->c_count

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBC->c_count(DBC *cursor, db_recno_t *countp, u_int32_t flags);
-

-

Description

-

The DBcursor->c_count function returns a count of the number of duplicate data -items for the key referenced by the -cursor into the memory location referenced by countp. -If the underlying database does not support duplicate data items the call -will still succeed and a count of 1 will be returned. -

The flags parameter is currently unused, and must be set to 0. -

If the cursor argument is not yet initialized, the DBcursor->c_count function will return EINVAL. -

Otherwise, the DBcursor->c_count function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DBcursor->c_count 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 DBcursor->c_count function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBcursor->c_close, -DBcursor->c_count, -DBcursor->c_del, -DBcursor->c_dup, -DBcursor->c_get -and -DBcursor->c_put. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/dbc_del.html b/bdb/docs/api_c/dbc_del.html deleted file mode 100644 index 110d97471c8..00000000000 --- a/bdb/docs/api_c/dbc_del.html +++ /dev/null @@ -1,68 +0,0 @@ - - - - - -Berkeley DB: DBcursor->c_del - - - - - - - -
-

DBcursor->c_del

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBcursor->c_del(DBC *cursor, u_int32_t flags);
-

-

Description

-

The DBcursor->c_del function deletes the key/data pair currently referenced by -the cursor. -

The flags parameter is currently unused, and must be set to 0. -

The cursor position is unchanged after a delete, and subsequent calls to -cursor functions expecting the cursor to reference an existing key will -fail. -

If the element has already been deleted, DBcursor->c_del will return -DB_KEYEMPTY. -

If the cursor is not yet initialized, the DBcursor->c_del function will return EINVAL. -

Otherwise, the DBcursor->c_del function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DBcursor->c_del function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

EINVAL
An invalid flag value or parameter was specified. -
-

-

EPERM
Write attempted on read-only cursor when the DB_INIT_CDB flag was -specified to DBENV->open. -
-

The DBcursor->c_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 DBcursor->c_del function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBcursor->c_close, -DBcursor->c_count, -DBcursor->c_del, -DBcursor->c_dup, -DBcursor->c_get -and -DBcursor->c_put. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/dbc_dup.html b/bdb/docs/api_c/dbc_dup.html deleted file mode 100644 index 42e3531ca04..00000000000 --- a/bdb/docs/api_c/dbc_dup.html +++ /dev/null @@ -1,72 +0,0 @@ - - - - - -Berkeley DB: DBcursor->c_dup - - - - - - - -
-

DBcursor->c_dup

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBC->c_dup(DBC *cursor, DBC **cursorp, u_int32_t flags);
-

-

Description

-

The DBcursor->c_dup function creates a new cursor that uses the same transaction -and locker ID as the original cursor. This is useful when an application -is using locking and requires two or more cursors in the same thread of -control. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_POSITION
The newly created cursor is initialized to reference the same position -in the database as the original cursor and hold the same locks. If the -DB_POSITION flag is not specified, then the created cursor is -uninitialized and will behave like a cursor newly created using -DB->cursor. -
-

When using the Berkeley DB Concurrent Data Store product, there can be only one active write cursor -at a time. For this reason, attempting to duplicate a cursor for which -the DB_WRITECURSOR flag was specified during creation will return -an error. -

If the cursor argument is not yet initialized, the DBcursor->c_dup function will return EINVAL. -

Otherwise, the DBcursor->c_dup function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DBcursor->c_dup function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -

The cursor argument was created using the -DB_WRITECURSOR flag in the Berkeley DB Concurrent Data Store product. -

-

The DBcursor->c_dup 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 DBcursor->c_dup function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBcursor->c_close, -DBcursor->c_count, -DBcursor->c_del, -DBcursor->c_dup, -DBcursor->c_get -and -DBcursor->c_put. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/dbc_get.html b/bdb/docs/api_c/dbc_get.html deleted file mode 100644 index 014661f33e7..00000000000 --- a/bdb/docs/api_c/dbc_get.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - -Berkeley DB: DBcursor->c_get - - - - - - - -
-

DBcursor->c_get

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBcursor->c_get(DBC *cursor,
-    DBT *key, DBT *data, u_int32_t flags);
-

-

Description

-

The DBcursor->c_get function retrieves key/data pairs from the database. The -address and length of the key -are returned in the object referenced by key (except for the case -of the DB_SET flag where the key object is unchanged), -and the address and length of -the data are returned in the object referenced by data. -

Modifications to the database during a sequential scan will be reflected -in the scan, i.e. records inserted behind a cursor will not be returned -while records inserted in front of a cursor will be returned. -

In Queue and Recno databases, missing entries (i.e., entries that were -never explicitly created or that were created and then deleted), will be -skipped during a sequential scan. -

If multiple threads or processes insert items into the same database file -without using locking, the results are undefined. -For more detail, -see Cursor stability. -

The flags parameter must be set to one of the following values: -

-

DB_CURRENT
Return the key/data pair currently referenced by the cursor. -

If the cursor key/data pair was deleted, DBcursor->c_get will return -DB_KEYEMPTY. -

If the cursor is not yet initialized, the DBcursor->c_get function will return EINVAL. -

DB_FIRST, DB_LAST
The cursor is set to reference the first (last) key/data pair of the -database, and that pair is returned. In the presence of duplicate key -values, the first (last) data item in the set of duplicates is returned. -

If the database is a Queue or Recno database, DBcursor->c_get using the -DB_FIRST (DB_LAST) flags will ignore any keys that exist -but were never explicitly created by the application or were created and -later deleted. -

If the database is empty, DBcursor->c_get will return DB_NOTFOUND. -

DB_GET_BOTH
The DB_GET_BOTH flag is identical to the DB_SET flag, -except that both the key and the data arguments must be matched by the -key and data item in the database. -

DB_GET_RECNO
Return the record number associated with the cursor. The record number -will be returned in data as described in DBT. The -key parameter is ignored. -

For DB_GET_RECNO to be specified, the underlying database must be -of type Btree and it must have been created with the DB_RECNUM -flag. -

DB_JOIN_ITEM
Do not use the data value found in all of the cursors as a lookup key for -the primary database, but simply return it in the key parameter instead. -The data parameter is left unchanged. -

For DB_JOIN_ITEM to be specified, the underlying cursor must have -been returned from the DB->join function. -

DB_NEXT, DB_PREV
If the cursor is not yet initialized, DB_NEXT (DB_PREV) -is identical to DB_FIRST (DB_LAST). Otherwise, the cursor -is moved to the next (previous) key/data pair of the database, and that -pair is returned. In the presence of duplicate key values, the value of -the key may not change. -

If the database is a Queue or Recno database, DBcursor->c_get using the -DB_NEXT (DB_PREV) flag will skip any keys that exist but -were never explicitly created by the application or were created and later -deleted. -

If the cursor is already on the last (first) record in the database, -DBcursor->c_get will return DB_NOTFOUND. -

DB_NEXT_DUP
If the next key/data pair of the database is a duplicate record for the -current key/data pair, the cursor is moved to the next key/data pair of -the database, and that pair is returned. Otherwise, DBcursor->c_get will -return DB_NOTFOUND. -

If the cursor is not yet initialized, the DBcursor->c_get function will return EINVAL. -

DB_NEXT_NODUP, DB_PREV_NODUP
If the cursor is not yet initialized, DB_NEXT_NODUP -(DB_PREV_NODUP) is identical to DB_FIRST -(DB_LAST). Otherwise, the cursor is moved to the next (previous) -non-duplicate key/data pair of the database, and that pair is returned. -

If the database is a Queue or Recno database, DBcursor->c_get using the -DB_NEXT_NODUP (DB_PREV_NODUP) flags will ignore any keys -that exist but were never explicitly created by the application or were -created and later deleted. -

If no non-duplicate key/data pairs occur after (before) the cursor -position in the database, DBcursor->c_get will return DB_NOTFOUND. -

DB_SET
Move the cursor to the specified key/data pair of the database, and -return the datum associated with the given key. -

In the presence of duplicate key values, DBcursor->c_get will return the -first data item for the given key. -

If the database is a Queue or Recno database and the requested key exists, -but was never explicitly created by the application or was later deleted, -DBcursor->c_get will return DB_KEYEMPTY. -

If no matching keys are found, DBcursor->c_get will return -DB_NOTFOUND. -

DB_SET_RANGE
The DB_SET_RANGE flag is identical to the DB_SET flag, -except that the key is returned as well as the data item, and, in the case -of the Btree access method, the returned key/data pair is the smallest -key greater than or equal to the specified key (as determined by the -comparison function), permitting partial key matches and range -searches. -

DB_SET_RECNO
Move the cursor to the specific numbered record of the database, and -return the associated key/data pair. The data field of the -specified key -must be a pointer to a memory location from which a db_recno_t -may be read, as described in DBT. This memory location will be -read to determine the record to be retrieved. -

For DB_SET_RECNO to be specified, the underlying database must be -of type Btree and it must have been created with the DB_RECNUM -flag. -

-

In addition, the following flag may be set by bitwise inclusively OR'ing it into the -flags parameter: -

-

DB_RMW
Acquire write locks instead of read locks when doing the retrieval. -Setting this flag may decrease the likelihood of deadlock during a -read-modify-write cycle by immediately acquiring the write lock during -the read part of the cycle so that another thread of control acquiring -a read lock for the same item, in its own read-modify-write cycle, will -not result in deadlock. -
-

Otherwise, the DBcursor->c_get function returns a non-zero error value on failure and 0 on success. -

If DBcursor->c_get fails for any reason, the state of the cursor will be -unchanged. -

Errors

-

The DBcursor->c_get function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

ENOMEM
There was insufficient memory to return the requested item. -
-

-

EINVAL
An invalid flag value or parameter was specified. -

The specified cursor was not currently initialized. -

-

The DBcursor->c_get 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 DBcursor->c_get function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBcursor->c_close, -DBcursor->c_count, -DBcursor->c_del, -DBcursor->c_dup, -DBcursor->c_get -and -DBcursor->c_put. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/dbc_put.html b/bdb/docs/api_c/dbc_put.html deleted file mode 100644 index 9a8a0e8950a..00000000000 --- a/bdb/docs/api_c/dbc_put.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - -Berkeley DB: DBcursor->c_put - - - - - - - -
-

DBcursor->c_put

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBcursor->c_put(DBC *, DBT *key, DBT *data, u_int32_t flags);
-

-

Description

-

The DBcursor->c_put function stores key/data pairs into the database. -

The flags parameter must be set to one of the following values: -

-

DB_AFTER
In the case of the Btree and Hash access methods, insert the data -element as a duplicate element of the key referenced by the cursor. -The new element appears immediately after the current cursor position. -It is an error to specify DB_AFTER if the underlying Btree or -Hash database does not support duplicate data items. The key -parameter is ignored. -

In the case of the Recno access method, it is an error to specify -DB_AFTER if the underlying Recno database was not created with -the DB_RENUMBER flag. If the DB_RENUMBER flag was -specified, a new key is created, all records after the inserted item -are automatically renumbered, and the key of the new record is returned -in the structure referenced by the parameter key. The initial -value of the key parameter is ignored. See DB->open -for more information. -

The DB_AFTER flag may not be specified to the Queue access method. -

If the current cursor record has already been deleted and the underlying -access method is Hash, DBcursor->c_put will return DB_NOTFOUND. -If the underlying access method is Btree or Recno, the operation will -succeed. -

If the cursor is not yet initialized or a duplicate sort function has been -specified, the DBcursor->c_put function will return EINVAL. -

DB_BEFORE
In the case of the Btree and Hash access methods, insert the data element -as a duplicate element of the key referenced by the cursor. The new -element appears immediately before the current cursor position. It is -an error to specify DB_BEFORE if the underlying Btree or Hash -database does not support duplicate data items. The key -parameter is ignored. -

In the case of the Recno access method, it is an error to specify -DB_BEFORE if the underlying Recno database was not created with -the DB_RENUMBER flag. If the DB_RENUMBER flag was -specified, a new key is created, the current record and all records -after it are automatically renumbered, and the key of the new record is -returned in the structure referenced by the parameter key. The -initial value of the key parameter is ignored. See -DB->open for more information. -

The DB_BEFORE flag may not be specified to the Queue access method. -

If the current cursor record has already been deleted and the underlying -access method is Hash, DBcursor->c_put will return DB_NOTFOUND. -If the underlying access method is Btree or Recno, the operation will -succeed. -

If the cursor is not yet initialized or a duplicate sort function has been -specified, DBcursor->c_put will return EINVAL. -

DB_CURRENT
Overwrite the data of the key/data pair referenced by the cursor with the -specified data item. The key parameter is ignored. -

If a duplicate sort function has been specified and the data item of the -current referenced key/data pair does not compare equally to the data -parameter, DBcursor->c_put will return EINVAL. -

If the current cursor record has already been deleted and the underlying -access method is Hash, DBcursor->c_put will return DB_NOTFOUND. -If the underlying access method is Btree, Queue or Recno, the operation -will succeed. -

If the cursor is not yet initialized, DBcursor->c_put will return EINVAL. -

DB_KEYFIRST
In the case of the Btree and Hash access methods, insert the specified -key/data pair into the database. -

If the underlying database supports duplicate data items, and if the -key already exists in the database and a duplicate sort function has -been specified, the inserted data item is added in its sorted location. -If the key already exists in the database and no duplicate sort function -has been specified, the inserted data item is added as the first of the -data items for that key. -

The DB_KEYFIRST flag may not be specified to the Queue or Recno -access methods. -

DB_KEYLAST
In the case of the Btree and Hash access methods, insert the specified -key/data pair into the database. -

If the underlying database supports duplicate data items, and if the -key already exists in the database and a duplicate sort function has -been specified, the inserted data item is added in its sorted location. -If the key already exists in the database, and no duplicate sort -function has been specified, the inserted data item is added as the last -of the data items for that key. -

The DB_KEYLAST flag may not be specified to the Queue or Recno -access methods. -

DB_NODUPDATA
In the case of the Btree and Hash access methods, insert the specified -key/data pair into the database unless it already exists in the database. -If the key/data pair already appears in the database, DB_KEYEXIST -is returned. The DB_NODUPDATA flag may only be specified if -the underlying database has been configured to support sorted duplicate -data items. -

The DB_NODUPDATA flag may not be specified to the Queue or Recno -access methods. -

-

Otherwise, the DBcursor->c_put function returns a non-zero error value on failure and 0 on success. -

If DBcursor->c_put fails for any reason, the state of the cursor will be -unchanged. If DBcursor->c_put succeeds and an item is inserted into the -database, the cursor is always positioned to reference the newly inserted -item. -

Errors

-

The DBcursor->c_put function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

EACCES
An attempt was made to modify a read-only database. -
-

-

EINVAL
An invalid flag value or parameter was specified. -

The DB_BEFORE or DB_AFTER flags were specified, and the -underlying access method is Queue. -

An attempt was made to add a record to a fixed-length database that was too -large to fit. -

-

-

EPERM
Write attempted on read-only cursor when the DB_INIT_CDB flag was -specified to DBENV->open. -
-

The DBcursor->c_put 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 DBcursor->c_put function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBcursor->c_close, -DBcursor->c_count, -DBcursor->c_del, -DBcursor->c_dup, -DBcursor->c_get -and -DBcursor->c_put. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/dbm.html b/bdb/docs/api_c/dbm.html deleted file mode 100644 index 783d59e6271..00000000000 --- a/bdb/docs/api_c/dbm.html +++ /dev/null @@ -1,220 +0,0 @@ - - - - - -Berkeley DB: dbm/ndbm - - - - - - - -
-

dbm/ndbm

-		 -APIRef -
-

- -

-#define DB_DBM_HSEARCH    1
-#include <db.h>
-

-typedef struct {
-	char *dptr;
-	int dsize;
-} datum;
-

-
Dbm Functions

-int
-dbminit(char *file);
-

-int
-dbmclose();
-

-datum
-fetch(datum key);
-

-int
-store(datum key, datum content);
-

-int
-delete(datum key);
-

-datum
-firstkey(void);
-

-datum
-nextkey(datum key);
-

-
Ndbm Functions

-DBM *
-dbm_open(char *file, int flags, int mode);
-

-void
-dbm_close(DBM *db);
-

-datum
-dbm_fetch(DBM *db, datum key);
-

-int
-dbm_store(DBM *db, datum key, datum content, int flags);
-

-int
-dbm_delete(DBM *db, datum key);
-

-datum
-dbm_firstkey(DBM *db);
-

-datum
-dbm_nextkey(DBM *db);
-

-int
-dbm_error(DBM *db);
-

-int
-dbm_clearerr(DBM *db);
-

-

Description

-

The dbm interfaces to the Berkeley DB library are intended to provide -high-performance implementations and source code compatibility for -applications written to historic interfaces. They are not recommended -for any other purpose. The historic dbm database format -is not supported, and databases previously built using the real -dbm libraries cannot be read by the Berkeley DB functions. -

To compile dbm applications, replace the application's -#include of the dbm or ndbm include file (e.g., -#include <dbm.h> or #include <ndbm.h>) -with the following two lines: -

#define DB_DBM_HSEARCH    1
-#include <db.h>
-

and recompile. If the application attempts to load against a dbm library -(e.g., -ldbm), remove the library from the load line. -

Key and content arguments are objects described by the -datum typedef. A datum specifies a string of -dsize bytes pointed to by dptr. Arbitrary binary data, -as well as normal text strings, is allowed. -

Dbm Functions

-

Before a database can be accessed, it must be opened by dbminit. -This will open and/or create the database file.db. If created, -the database file is created read/write by owner only (as described in -chmod(2) and modified by the process' umask value at the time -of creation (see umask(2)). The group ownership of created -files is based on the system and directory defaults, and is not further -specified by Berkeley DB. -

A database may be closed, and any held resources released, by calling -dbmclose. -

Once open, the data stored under a key is accessed by fetch and -data is placed under a key by store. A key (and its associated -contents) is deleted by delete. A linear pass through all keys -in a database may be made, in an (apparently) random order, by use of -firstkey and nextkey. The firstkey function will return -the first key in the database. The nextkey function will return the next -key in the database. -

The following code will traverse the data base: -

for (key = firstkey();
-    key.dptr != NULL; key = nextkey(key)) {
-	...
-}
-

Ndbm Functions

-

Before a database can be accessed, it must be opened by dbm_open. -This will open and/or create the database file file.db depending -on the flags parameter (see open(2)). If created, the database -file is created with mode mode (as described in chmod(2)) and modified by the process' umask value at the time of creation (see -umask(2)). The group ownership of created files is based on -the system and directory defaults, and is not further specified by -Berkeley DB. -

Once open, the data stored under a key is accessed by dbm_fetch -and data is placed under a key by dbm_store. The flags -field can be either DBM_INSERT or DBM_REPLACE. -DBM_INSERT will only insert new entries into the database and will -not change an existing entry with the same key. DBM_REPLACE will -replace an existing entry if it has the same key. A key (and its -associated contents) is deleted by dbm_delete. A linear pass -through all keys in a database may be made, in an (apparently) random -order, by use of dbm_firstkey and dbm_nextkey. The -dbm_firstkey function will return the first key in the database. The -dbm_nextkey function will return the next key in the database. -

The following code will traverse the data base: -

for (key = dbm_firstkey(db);
-    key.dptr != NULL; key = dbm_nextkey(db)) {
-	...
-}
-

Compatibility Notes

-

The historic dbm library created two underlying database files, -traditionally named file.dir and file.pag. The Berkeley DB -library creates a single database file named file.db. -Applications that are aware of the underlying database file names may -require additional source code modifications. -

The historic dbminit interface required that the underlying -.dir and .pag files already exist (empty databases were -created by first manually creating zero-length .dir and -.pag files). Applications that expect to create databases using -this method may require additional source code modifications. -

The historic dbm_dirfno and dbm_pagfno macros are -supported, but will return identical file descriptors as there is only a -single underlying file used by the Berkeley DB hashing access method. -Applications using both file descriptors for locking may require -additional source code modifications. -

If applications using the dbm interface exits without first -closing the database, it may lose updates because the Berkeley DB library -buffers writes to underlying databases. Such applications will require -additional source code modifications to work correctly with the Berkeley DB -library. -

Dbm Diagnostics

-

The dbminit function returns -1 on failure, setting errno, -and 0 on success. -

The fetch function sets the dptr field of the returned -datum to NULL on failure, setting errno, -and returns a non-NULL dptr on success. -

The store function returns -1 on failure, setting errno, -and 0 on success. -

The delete function returns -1 on failure, setting errno, -and 0 on success. -

The firstkey function sets the dptr field of the returned -datum to NULL on failure, setting errno, -and returns a non-NULL dptr on success. -

The nextkey function sets the dptr field of the returned -datum to NULL on failure, setting errno, -and returns a non-NULL dptr on success. -

Errors

-

The dbminit, fetch, store, delete, firstkey and nextkey functions may fail -and return a non-zero error for errors specified for other Berkeley DB and C -library or system functions. -

Ndbm Diagnostics

-

The dbm_close function returns non-zero when an error has occurred reading or -writing the database. -

The dbm_close function resets the error condition on the named database. -

The dbm_open function returns NULL on failure, setting errno, -and 0 on success. -

The dbm_fetch function sets the dptr field of the returned -datum to NULL on failure, setting errno, -and returns a non-NULL dptr on success. -

The dbm_store function returns -1 on failure, setting errno, -0 on success, and 1 if DBM_INSERT was set and the specified key already -existed in the database. -

The dbm_delete function returns -1 on failure, setting errno, -and 0 on success. -

The dbm_firstkey function sets the dptr field of the returned -datum to NULL on failure, setting errno, -and returns a non-NULL dptr on success. -

The dbm_nextkey function sets the dptr field of the returned -datum to NULL on failure, setting errno, -and returns a non-NULL dptr on success. -

The dbm_close function returns -1 on failure, setting errno, -and 0 on success. -

The dbm_close function returns -1 on failure, setting errno, -and 0 on success. -

Errors

-

The dbm_open, dbm_close, dbm_fetch, dbm_store, dbm_delete, dbm_firstkey -and dbm_nextkey functions may fail and return a non-zero error for errors -specified for other Berkeley DB and C library or system functions. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/dbt.html b/bdb/docs/api_c/dbt.html deleted file mode 100644 index a0c3e76db8d..00000000000 --- a/bdb/docs/api_c/dbt.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - -Berkeley DB: DBT - - - - - - -

Key/Data Pairs

-

Storage and retrieval for the Berkeley DB access methods are based on key/data -pairs. Both key and data items are represented by the DBT data structure. -(The name DBT is a mnemonic for data base thang, and was used -because no one could think of a reasonable name that wasn't already in -use somewhere else.) Key and data byte strings may reference strings of -zero length up to strings of essentially unlimited length. See -Database limits for more -information. -

typedef struct {
-	void *data;
-	u_int32_t size;
-	u_int32_t ulen;
-	u_int32_t dlen;
-	u_int32_t doff;
-	u_int32_t flags;
-} DBT;
-

In order to ensure compatibility with future releases of Berkeley DB, all fields -of the DBT structure that are not explicitly set should be initialized to -0 before the first time the structure is used. Do this by declaring the -structure external or static, or by calling the C library routine -bzero(3) or memset(3). -

By default, the flags structure element is expected to be 0. In -this default case, when the application is providing Berkeley DB a key or data -item to store into the database, Berkeley DB expects the data structure -element to point to a byte string of size bytes. When returning -a key/data item to the application, Berkeley DB will store into the data -structure element a pointer to a byte string of size bytes, and -the memory referenced by the pointer will be allocated and managed by Berkeley DB. -

The elements of the DBT structure are defined as follows: -

-

void *data;
A pointer to a byte string. -

u_int32_t size;
The length of data, in bytes. -

u_int32_t ulen;
The size of the user's buffer (referenced by data), in bytes. -This location is not written by the Berkeley DB functions. -

Note that applications can determine the length of a record by setting -the ulen field to 0 and checking the return value in the -size field. See the DB_DBT_USERMEM flag for more information. -

u_int32_t dlen;
The length of the partial record being read or written by the application, -in bytes. See the DB_DBT_PARTIAL flag for more information. -

u_int32_t doff;
The offset of the partial record being read or written by the application, -in bytes. See the DB_DBT_PARTIAL flag for more information. -

u_int32_t flags;
-

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_DBT_MALLOC
When this flag is set Berkeley DB will allocate memory for the returned key -or data item (using malloc(3), or the user-specified malloc -function) and return a pointer to it in the data field of the -key or data DBT structure. As any allocated memory becomes the -responsibility of the calling application, the caller must be able to -determine if memory was allocated. -

It is an error to specify more than one of DB_DBT_MALLOC, -DB_DBT_REALLOC and DB_DBT_USERMEM. -

DB_DBT_REALLOC
When this flag is set Berkeley DB will allocate memory for the returned key -or data item (using realloc(3), or the user-specified realloc -function) and return a pointer to it in the data field of the -key or data DBT structure. As any allocated memory becomes the -responsibility of the calling application, the caller must be able to -determine if memory was allocated. -

The difference between DB_DBT_MALLOC and DB_DBT_REALLOC -is that the latter will call realloc(3) instead of -malloc(3), so the allocated memory will be grown as necessary -instead of the application doing repeated free/malloc calls. -

It is an error to specify more than one of DB_DBT_MALLOC, -DB_DBT_REALLOC and DB_DBT_USERMEM. -

DB_DBT_USERMEM
The data field of the key or data structure must reference -memory that is at least ulen bytes in length. If the length of -the requested item is less than or equal to that number of bytes, the -item is copied into the memory referenced by the data field. -Otherwise, the size field is set to the length needed for the -requested item, and the error ENOMEM is returned. -

It is an error to specify more than one of DB_DBT_MALLOC, -DB_DBT_REALLOC and DB_DBT_USERMEM. -

DB_DBT_PARTIAL
Do partial retrieval or storage of an item. If the calling application -is doing a get, the dlen bytes starting doff bytes from -the beginning of the retrieved data record are returned as if they -comprised the entire record. If any or all of the specified bytes do -not exist in the record, the get is successful and the existing bytes -or nul bytes are returned. -

For example, if the data portion of a retrieved record was 100 bytes, -and a partial retrieval was done using a DBT having a dlen -field of 20 and a doff field of 85, the get call would succeed, -the data field would reference the last 15 bytes of the record, -and the size field would be set to 15. -

If the calling application is doing a put, the dlen bytes -starting doff bytes from the beginning of the specified key's -data record are replaced by the data specified by the data -and size structure elements. -If dlen is smaller than size, the record will grow, -and if dlen is larger than size, the record will shrink. -If the specified bytes do not exist, the record will be extended using -nul bytes as necessary, and the put call will succeed. -

It is an error to attempt a partial put using the DB->put function -in a database that supports duplicate records. -Partial puts in databases supporting duplicate records must be done -using a DBcursor->c_put function. -

It is an error to attempt a partial put with differing dlen and -size values in Queue or Recno databases with fixed-length records. -

For example, if the data portion of a retrieved record was 100 bytes, -and a partial put was done using a DBT having a dlen field of 20, -a doff field of 85, and a size field of 30, the resulting -record would be 115 bytes in length, where the last 30 bytes would be -those specified by the put call. -

-
- -

Retrieved key/data permanence

-

When using the non-cursor Berkeley DB calls to retrieve key/data items (e.g., -DB->get), the memory referenced by the pointer stored into the -Dbt is only valid until the next call to Berkeley DB using the Db -handle returned by DB->open. (This includes any use of -the returned Db handle, including by another thread of control -within the process. For this reason, when multiple threads are using the -returned Db handle concurrently, one of the DB_DBT_MALLOC, -DB_DBT_REALLOC or DB_DBT_USERMEM flags must be specified -with any non-cursor Dbt used for key or data retrieval.) -

When using the cursor Berkeley DB calls to retrieve key/data items (e.g., -DBcursor->c_get), the memory referenced by the pointer into the -Dbt is only valid until the next call to Berkeley DB using the -DBC handle returned by DB->cursor. - -

Data alignment

-

The Berkeley DB access methods provide no guarantees about key/data byte string -alignment, and applications are responsible for arranging any necessary -alignment. The DB_DBT_MALLOC, DB_DBT_REALLOC and -DB_DBT_USERMEM flags may be used to store returned items in memory -of arbitrary alignment. - -

Logical Record Numbers

-

In all cases for the Queue and Recno access methods, and when calling the -DB->get and DBcursor->c_get functions with the -DB_SET_RECNO flag specified, the data field of the key -must be a pointer to a memory location of type db_recno_t, as -typedef'd in the #include <db.h> include file. This type is a 32-bit -unsigned type, (which limits the number of logical records in a Queue or -Recno database, and the maximum logical record which may be directly -retrieved from a Btree database, to 4,294,967,296). The size -field of the key should be the size of that type, i.e., in the C -programming language, sizeof(db_recno_t). -

Logical record numbers are 1-based, not 0-based, i.e., the first record -in the database is record number 1. - -

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_close.html b/bdb/docs/api_c/env_close.html deleted file mode 100644 index fdb11e2e18c..00000000000 --- a/bdb/docs/api_c/env_close.html +++ /dev/null @@ -1,84 +0,0 @@ - - - - - -Berkeley DB: DBENV->close - - - - - - - -
-

DBENV->close

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->close(DB_ENV *dbenv, u_int32_t flags);
-

-

Description

-

The DBENV->close function closes the Berkeley DB environment, freeing any -allocated resources and closing any underlying subsystems. -

Calling DBENV->close does not imply closing any databases that were -opened in the environment. -

The flags parameter is currently unused, and must be set to 0. -

Where the environment was initialized with the DB_INIT_LOCK flag, -calling DBENV->close does not release any locks still held by the -closing process, providing functionality for long-lived locks. -Processes that wish to have all their locks -released can do so by issuing the appropriate lock_vec call. -

Where the environment was initialized with the DB_INIT_MPOOL -flag, calling DBENV->close implies calls to memp_fclose for -any remaining open files in the memory pool that were returned to this -process by calls to memp_fopen. It does not imply a call to -memp_fsync for those files. -

Where the environment was initialized with the DB_INIT_TXN flag, -calling DBENV->close aborts any uncommitted transactions. -(Applications are should not depend on this behavior. If the process' has -already closed a database handle which is necessary to abort an -uncommitted transaction, the Berkeley DB environment must then require that -recovery be run before further operations are done, since once a -transaction exists that cannot be committed or aborted, no future -checkpoint can ever succeed.) -

In multi-threaded applications, only a single thread may call -DBENV->close. -

Once DBENV->close has been called, regardless of its return, -the Berkeley DB environment handle may not be accessed again. -

The DBENV->close function returns a non-zero error value on failure and 0 on success. -

Errors

-

The DBENV->close 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 DBENV->close function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_create.html b/bdb/docs/api_c/env_create.html deleted file mode 100644 index 26ffb204ef2..00000000000 --- a/bdb/docs/api_c/env_create.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - -Berkeley DB: db_env_create - - - - - - - -
-

db_env_create

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_create(DB_ENV **dbenvp, u_int32_t flags);
-

-

Description

-

The db_env_create function creates a DB_ENV structure which is -the handle for a Berkeley DB environment. A pointer to this structure is -returned in the memory referenced by dbenvp. -

The flags parameter must be set to 0 or the following value: -

-

DB_CLIENT
Create a client environment to connect to a server. -

The DB_CLIENT flag indicates to the system that this environment -is remote on a server. The use of this flag causes the environment -methods to use functions that call a server instead of local functions. -Prior to making any environment or database method calls, the application -must call the DBENV->set_server function to establish the -connection to the server. -

-

The DB_ENV handle contains a special field, "app_private", which -is declared as type "void *". This field is provided for the use of -the application program. It is initialized to NULL and is not further -used by Berkeley DB in any way. -

The db_env_create function returns a non-zero error value on failure and 0 on success. -

Errors

-

The db_env_create 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_env_create function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_open.html b/bdb/docs/api_c/env_open.html deleted file mode 100644 index 677f40c1591..00000000000 --- a/bdb/docs/api_c/env_open.html +++ /dev/null @@ -1,205 +0,0 @@ - - - - - -Berkeley DB: DBENV->open - - - - - - - -
-

DBENV->open

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->open(DB_ENV *, char *db_home, u_int32_t flags, int mode);
-

-

Description

-

The DBENV->open function is the interface for opening the Berkeley DB -environment. It provides a structure for creating a consistent -environment for processes using one or more of the features of Berkeley DB. -

The db_home argument to DBENV->open (and file name -resolution in general) is described in -Berkeley DB File Naming. -

The flags argument specifies the subsystems that are initialized -and how the application's environment affects Berkeley DB file naming, among -other things. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

As there are a large number of flags that can be specified, they have been -grouped together by functionality. The first group of flags indicate -which of the Berkeley DB subsystems should be initialized: -

-

DB_JOINENV
Join an existing environment. This option allows applications to -join an existing environment without knowing which Berkeley DB subsystems -the environment supports. -

DB_INIT_CDB
Initialize locking for the Berkeley DB Concurrent Data Store -product. In this mode, Berkeley DB provides multiple reader/single writer -access. The only other subsystem that should be specified with the -DB_INIT_CDB flag is DB_INIT_MPOOL. -

Access method calls are largely unchanged when using this flag, although -any cursors through which update operations (e.g., DBcursor->c_put, -DBcursor->c_del) will be made must have the DB_WRITECURSOR value -set in the flags parameter to the cursor call that creates the cursor. -See DB->cursor for more information. -

DB_INIT_LOCK
Initialize the locking subsystem. This subsystem should be used when -multiple processes or threads are going to be reading and writing a Berkeley DB -database, so that they do not interfere with each other. If all threads -are accessing the database(s) read-only, then locking is unnecessary. -When the DB_INIT_LOCK flag is specified, it is usually necessary to run -the deadlock detector, as well. See db_deadlock and -lock_detect for more information. -

DB_INIT_LOG
Initialize the logging subsystem. This subsystem is used when recovery -from application or system failure is necessary. -

The log is stored in one or more files in the environment directory. -Each file is named using the format log.NNNNNNNNNN, where -NNNNNNNNNN is the sequence number of the file within the log. -For further information, see -Log File Limits. -

If the log region is being created and log files are already present, the -log files are reviewed and subsequent log writes are appended -to the end of the log, rather than overwriting current log entries. -

DB_INIT_MPOOL
Initialize the shared memory buffer pool subsystem. This subsystem is -used whenever the application is using any Berkeley DB access method. -

DB_INIT_TXN
Initialize the transaction subsystem. This subsystem is used when -recovery and atomicity of multiple operations and recovery are important. -The DB_INIT_TXN flag implies the DB_INIT_LOG flag. -
-

The second group of flags govern what recovery, if any, is performed when -the environment is initialized: -

-

DB_RECOVER
Run normal recovery on this environment before opening it for normal use. -If this flag is set, the DB_CREATE flag must also be set since the regions -will be removed and recreated. -

DB_RECOVER_FATAL
Run catastrophic recovery on this environment before opening it for normal -use. If this flag is set, the DB_CREATE flag must also be set since the -regions will be removed and recreated. -
-

A standard part of the recovery process is to remove the existing Berkeley DB -environment and create a new one in which to perform recovery. If the -thread of control performing recovery does not specify the correct region -initialization information (e.g., the correct memory pool cache size), -the result can be an application running in an environment with incorrect -cache and other subsystem sizes. For this reason, the thread of control -performing recovery should either specify correct configuration -information before calling the DBENV->open function, or it should remove -the environment after recovery is completed, leaving creation of the -correctly sized environment to a subsequent call to DBENV->open. -

All Berkeley DB recovery processing must be single-threaded, that is, only a -single thread of control may perform recovery or access a Berkeley DB -environment while recovery is being performed. As it is not an error to -specify DB_RECOVER for an environment for which no recovery is -required, it is reasonable programming practice for the thread of control -responsible for performing recovery and creating the environment to always -specify the DB_RECOVER flag during startup. -

The DBENV->open function returns successfully if DB_RECOVER -or DB_RECOVER_FATAL is specified and no log files exist, so it is -necessary to ensure all necessary log files are present before running -recovery. For further information, consult db_archive and -db_recover. -

The third group of flags govern file naming extensions in the environment: -

- -

DB_USE_ENVIRON
The Berkeley DB process' environment may be permitted to specify information to -be used when naming files; see Berkeley DB -File Naming. As permitting users to specify which files are used can -create security problems, environment information will be used in file -naming for all users only if the DB_USE_ENVIRON flag is set. -

DB_USE_ENVIRON_ROOT
The Berkeley DB process' environment may be permitted to specify information to -be used when naming files; see Berkeley DB -File Naming. As permitting users to specify which files are used can -create security problems, if the DB_USE_ENVIRON_ROOT flag is set, -environment information will be used for file naming only for users with -appropriate permissions (e.g., on UNIX systems, users with a user-ID of 0). -
-

Finally, there are a few additional, unrelated flags: -

-

DB_CREATE
Cause Berkeley DB subsystems to create any underlying files, as necessary. -

DB_LOCKDOWN
Lock shared Berkeley DB environment files and memory mapped databases into memory. -

DB_PRIVATE
Specify that the environment will only be accessed by a single process -(although that process may be multi-threaded). This flag has two effects -on the Berkeley DB environment. First, all underlying data structures are -allocated from per-process memory instead of from shared memory that is -potentially accessible to more than a single process. Second, mutexes -are only configured to work between threads. -

This flag should not be specified if more than a single process is -accessing the environment, as it is likely to cause database corruption -and unpredictable behavior, e.g., if both a server application and the -Berkeley DB utility db_stat will access the environment, the -DB_PRIVATE flag should not be specified. -

DB_SYSTEM_MEM
Allocate memory from system shared memory instead of from memory backed -by the filesystem. See Shared Memory -Regions for more information. -

DB_THREAD
Cause the DB_ENV handle returned by DBENV->open to be -free-threaded, that is, useable by multiple threads within a -single address space. -
-

On UNIX systems, or in IEEE/ANSI Std 1003.1 (POSIX) environments, all files created by Berkeley DB -are created with mode mode (as described in chmod(2)) and -modified by the process' umask value at the time of creation (see -umask(2)). The group ownership of created files is based on -the system and directory defaults, and is not further specified by Berkeley DB. -If mode is 0, files are created readable and writeable by both -owner and group. On Windows systems, the mode argument is ignored. -

The DBENV->open function returns a non-zero error value on failure and 0 on success. -

Environment Variables

-

-

DB_HOME
The environment variable DB_HOME may be used as the path of -the database home as described in -Berkeley DB File Naming. -
-

Errors

-

The DBENV->open function may fail and return a non-zero error for the following conditions: -

-

EAGAIN
The shared memory region was locked and (repeatedly) unavailable. -
-

-

EINVAL
An invalid flag value or parameter was specified. -

-The DB_THREAD flag was specified and spinlocks are not -implemented for this architecture. -

The DB_HOME or TMPDIR environment variables were set but empty. -

An incorrectly formatted NAME VALUE entry or line was found. -

-

-

ENOSPC
HP-UX only: a previously created Berkeley DB environment for this process still -exists. -
-

The DBENV->open 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 DBENV->open function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_remove.html b/bdb/docs/api_c/env_remove.html deleted file mode 100644 index 2d7279d79ab..00000000000 --- a/bdb/docs/api_c/env_remove.html +++ /dev/null @@ -1,125 +0,0 @@ - - - - - -Berkeley DB: DBENV->remove - - - - - - - -
-

DBENV->remove

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->remove(DB_ENV *, char *db_home, u_int32_t flags);
-

-

Description

-

The DBENV->remove function destroys a Berkeley DB environment, if it is not -currently in use. The environment regions, including any backing files, -are removed. Any log or database files and the environment directory are -not removed. -

The db_home argument to DBENV->remove is described in -Berkeley DB File Naming. -

If there are processes that have called DBENV->open without -calling DBENV->close (i.e., there are processes currently using -the environment), DBENV->remove will fail without further action, -unless the DB_FORCE flag is set, in which case -DBENV->remove will attempt to remove the environment regardless -of any processes still using it. -

The result of attempting to forcibly destroy the environment when it is -in use is unspecified. Processes using an environment often maintain open -file descriptors for shared regions within it. On UNIX systems, the -environment removal will usually succeed and processes that have already -joined the region will continue to run in that region without change, -however processes attempting to join the environment will either fail or -create new regions. On other systems (e.g., Windows/NT), where the -unlink(2) system call will fail if any process has an open -file descriptor for the file, the region removal will fail. -

Calling DBENV->remove should not be necessary for most applications, -as the Berkeley DB environment is cleaned up as part of normal database recovery -procedures, however, applications may wish to call DBENV->remove -as part of application shutdown to free up system resources. -Specifically, when the DB_SYSTEM_MEM flag was specified to -DBENV->open, it may be useful to call DBENV->remove in order -to release system shared memory segments that have been allocated. -

In the case of catastrophic or system failure, database recovery must be -performed (see db_recover), or the DB_RECOVER and -DB_RECOVER_FATAL flags to DBENV->open must be specified -when the environment is re-opened. Alternatively, if recovery is not -required because no database state is maintained across failures, and -the DB_SYSTEM_MEM flag was not specified when the environment -was created, it is possible to clean up an environment by removing all -of the files in the environment directory that begin with the string -prefix "__db", as no backing files are created in any other directory. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_FORCE
If the DB_FORCE flag is set, the environment is removed regardless -of any processes that may still using it, and, no locks are acquired -during this process. (Generally, the DB_FORCE flag is only -specified when applications were unable to shut down cleanly, and there -is a risk that an application may have died holding a Berkeley DB lock.) - -

DB_USE_ENVIRON
The Berkeley DB process' environment may be permitted to specify information to -be used when naming files; see Berkeley DB -File Naming. As permitting users to specify which files are used can -create security problems, environment information will be used in file -naming for all users only if the DB_USE_ENVIRON flag is set. -

DB_USE_ENVIRON_ROOT
The Berkeley DB process' environment may be permitted to specify information to -be used when naming files; see Berkeley DB -File Naming. As permitting users to specify which files are used can -create security problems, if the DB_USE_ENVIRON_ROOT flag is set, -environment information will be used for file naming only for users with -appropriate permissions (e.g., on UNIX systems, users with a user-ID of 0). -
-

In multi-threaded applications, only a single thread may call -DBENV->remove. -

A DB_ENV handle which has already been used to open an -environment should not be used to call the DBENV->remove function, a new -DB_ENV handle should be created for that purpose. -

Once DBENV->remove has been called, regardless of its return, -the Berkeley DB environment handle may not be accessed again. -

The DBENV->remove function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EBUSY
The shared memory region was in use and the force flag was not set. -
-

The DBENV->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 DBENV->remove function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_cachesize.html b/bdb/docs/api_c/env_set_cachesize.html deleted file mode 100644 index ba7980bb77a..00000000000 --- a/bdb/docs/api_c/env_set_cachesize.html +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - -Berkeley DB: DBENV->set_cachesize - - - - - - - -
-

DBENV->set_cachesize

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_cachesize(DB_ENV *dbenv,
-    u_int32_t gbytes, u_int32_t bytes, int ncache);
-

-

Description

-

Set the size of the database's shared memory buffer pool, i.e., the cache, -to gbytes gigabytes plus bytes. The cache should be the -size of the normal working data set of the application, with some small -amount of additional memory for unusual situations. (Note, the working -set is not the same as the number of simultaneously referenced pages, and -should be quite a bit larger!) -

The default cache size is 256KB, and may not be specified as less than -20KB. Any cache size less than 500MB is automatically increased by 25% -to account for buffer pool overhead, cache sizes larger than 500MB are -used as specified. For information on tuning the Berkeley DB cache size, see -Selecting a cache size. -

It is possible to specify caches to Berkeley DB that are large enough so that -they cannot be allocated contiguously on some architectures, e.g., some -releases of Solaris limit the amount of memory that may be allocated -contiguously by a process. If ncache is 0 or 1, the cache will -be allocated contiguously in memory. If it is greater than 1, the cache -will be broken up into ncache equally sized separate pieces of -memory. -

The DBENV->set_cachesize interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_cachesize function returns a non-zero error value on failure and 0 on success. -

The database environment's cache size may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_cachesize", one or more whitespace characters, -and the three arguments specified to this interface, separated by whitespace -characters, for example, "set_cachesize 1 500 2". Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

The specified cache size was impossibly small. -

-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_data_dir.html b/bdb/docs/api_c/env_set_data_dir.html deleted file mode 100644 index 68db6dc4725..00000000000 --- a/bdb/docs/api_c/env_set_data_dir.html +++ /dev/null @@ -1,77 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_data_dir - - - - - - - -
-

DBENV->set_data_dir

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_data_dir(DB_ENV *dbenv, const char *dir);
-

-

Description

-

Set the path of a directory to be used as the location of the access -method database files. Paths specified to the DB->open function -will be searched relative to this path. Paths set using this interface -are additive, and specifying more than one will result in each specified -directory being searched for database files. If any directories are -specified, created database files will always be created in the first path -specified. -

If no database directories are specified, database files can only exist -in the environment home directory. See Berkeley DB File Naming for more information. -

For the greatest degree of recoverability from system or application -failure, database files and log files should be located on separate -physical devices. -

The DBENV->set_data_dir interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_data_dir function returns a non-zero error value on failure and 0 on success. -

The database environment's data directory may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_data_dir", one or more whitespace characters, -and the directory name. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_errcall.html b/bdb/docs/api_c/env_set_errcall.html deleted file mode 100644 index 660943070ed..00000000000 --- a/bdb/docs/api_c/env_set_errcall.html +++ /dev/null @@ -1,73 +0,0 @@ - - - - - - -Berkeley DB: DBENV->set_errcall - - - - - - - -
-

DBENV->set_errcall

-		 -APIRef -
-

- -

-#include <db.h>
-

-void
-DBENV->set_errcall(DB_ENV *dbenv,
-    void (*db_errcall_fcn)(const char *errpfx, char *msg));
-

-

Description

-When an error occurs in the Berkeley DB library, a Berkeley DB error or an error -return value is returned by the function. In some cases, however, -the errno value may be insufficient to completely describe -the cause of the error especially during initial application debugging. -

The DBENV->set_errcall function is used to enhance the mechanism for reporting error -messages to the application. In some cases, when an error occurs, Berkeley DB -will call db_errcall_fcn with additional error information. The -function must be declared with two arguments; the first will be the prefix -string (as previously set by DB->set_errpfx or -DBENV->set_errpfx), the second will be the error message string. -It is up to the db_errcall_fcn function to display the error -message in an appropriate manner. -

Alternatively, you can use the DB->set_errfile or -DBENV->set_errfile functions to display the additional information -via a C library FILE *. -

This error logging enhancement does not slow performance or significantly -increase application size, and may be run during normal operation as well -as during application debugging. -

The DBENV->set_errcall interface may be used to configure Berkeley DB at any time -during the life of the application. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_errfile.html b/bdb/docs/api_c/env_set_errfile.html deleted file mode 100644 index ba1dd75f2cc..00000000000 --- a/bdb/docs/api_c/env_set_errfile.html +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - -Berkeley DB: DBENV->set_errfile - - - - - - - -
-

DBENV->set_errfile

-		 -APIRef -
-

- -

-#include <db.h>
-

-void
-DBENV->set_errfile(DB_ENV *dbenv, FILE *errfile);
-

-

Description

-When an error occurs in the Berkeley DB library, a Berkeley DB error or an error -return value is returned by the function. In some cases, however, -the errno value may be insufficient to completely describe -the cause of the error especially during initial application debugging. -

The DBENV->set_errfile function is used to enhance the mechanism for reporting error -messages to the application by setting a C library FILE * to be used for -displaying additional Berkeley DB error messages. In some cases, when an error -occurs, Berkeley DB will output an additional error message to the specified -file reference. -

The error message will consist of the prefix string and a colon -(":") (if a prefix string was previously specified using -DB->set_errpfx or DBENV->set_errpfx), an error string, and -a trailing <newline> character. -

This error logging enhancement does not slow performance or significantly -increase application size, and may be run during normal operation as well -as during application debugging. -

The DBENV->set_errfile interface may be used to configure Berkeley DB at any time -during the life of the application. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_errpfx.html b/bdb/docs/api_c/env_set_errpfx.html deleted file mode 100644 index be803070cce..00000000000 --- a/bdb/docs/api_c/env_set_errpfx.html +++ /dev/null @@ -1,59 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_errpfx - - - - - - - -
-

DBENV->set_errpfx

-		 -APIRef -
-

- -

-#include <db.h>
-

-void
-DBENV->set_errpfx(DB_ENV *dbenv, const char *errpfx);
-

-

Description

-

Set the prefix string that appears before error messages issued by Berkeley DB. -

The DBENV->set_errpfx function does not copy the memory referenced by the -errpfx argument, rather, it maintains a reference to it. This -allows applications to modify the error message prefix at any time, -without repeatedly calling DBENV->set_errpfx, but means that the -memory must be maintained until the handle is closed. -

The DBENV->set_errpfx interface may be used to configure Berkeley DB at any time -during the life of the application. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_feedback.html b/bdb/docs/api_c/env_set_feedback.html deleted file mode 100644 index 743f7772ff9..00000000000 --- a/bdb/docs/api_c/env_set_feedback.html +++ /dev/null @@ -1,69 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_feedback - - - - - - - -
-

DBENV->set_feedback

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_feedback(DB_ENV *,
-    void (*db_feedback_fcn)(DB_ENV *, int opcode, int pct));
-

-

Description

-

Some operations performed by the Berkeley DB library can take non-trivial -amounts of time. The DBENV->set_feedback function can be used by -applications to monitor progress within these operations. -

When an operation is likely to take a long time, Berkeley DB will call the -specified callback function. This function must be declared with -three arguments: the first will be a reference to the enclosing -environment, the second a flag value, and the third the percent of the -operation that has been completed, specified as an integer value between -0 and 100. It is up to the callback function to display this -information in an appropriate manner. -

The opcode argument may take on any of the following values: -

-

DB_RECOVER
The environment is being recovered. -
-

The DBENV->set_feedback interface may be used to configure Berkeley DB at any time -during the life of the application. -

The DBENV->set_feedback function returns a non-zero error value on failure and 0 on success. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_flags.html b/bdb/docs/api_c/env_set_flags.html deleted file mode 100644 index 6dfc0950819..00000000000 --- a/bdb/docs/api_c/env_set_flags.html +++ /dev/null @@ -1,84 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_flags - - - - - - - -
-

DBENV->set_flags

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_flags(DB_ENV *dbenv, u_int32_t flags, int onoff);
-

-

Description

-

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -If onoff is zero, the specified flags are cleared, otherwise they -are set. -

-

DB_CDB_ALLDB
For Berkeley DB Concurrent Data Store applications, perform locking on an environment-wide basis -rather than per-database. This flag may only be used to configure Berkeley DB -before the DBENV->open interface is called. -

DB_NOMMAP
Copy read-only database files in this environment into the local cache -instead of potentially mapping them into process memory (see the -description of the DBENV->set_mp_mmapsize function for further information). -

DB_TXN_NOSYNC
Do not synchronously flush the log on transaction commit or prepare. -This means that transactions exhibit the ACI (atomicity, consistency and -isolation) properties, but not D (durability), i.e., database integrity -will be maintained but it is possible that some number of the most -recently committed transactions may be undone during recovery instead of -being redone. -

The number of transactions that are potentially at risk is governed by -how often the log is checkpointed (see db_checkpoint for more -information) and how many log updates can fit on a single log page. -

-

The DBENV->set_flags function returns a non-zero error value on failure and 0 on success. -

The database environment's flag values may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_flags", one or more whitespace characters, -and the interface flag argument as a string, for example, "set_flags -DB_TXN_NOSYNC". Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_lg_bsize.html b/bdb/docs/api_c/env_set_lg_bsize.html deleted file mode 100644 index 85e6dc12118..00000000000 --- a/bdb/docs/api_c/env_set_lg_bsize.html +++ /dev/null @@ -1,68 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_lg_bsize - - - - - - - -
-

DBENV->set_lg_bsize

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_lg_bsize(DB_ENV *dbenv, u_int32_t lg_bsize);
-

-

Description

-

Set the size of the in-memory log buffer, in bytes. By default, or if -the value is set to 0, a size of 32K is used. -

Log information is stored in-memory until the storage space fills up -or transaction commit forces the information to be flushed to stable -storage. In the presence of long-running transactions or transactions -producing large amounts of data, larger buffer sizes can increase -throughput. -

The DBENV->set_lg_bsize interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_lg_bsize function returns a non-zero error value on failure and 0 on success. -

The database environment's log buffer size may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_lg_bsize", one or more whitespace characters, -and the size in bytes. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_lg_dir.html b/bdb/docs/api_c/env_set_lg_dir.html deleted file mode 100644 index a8d5c861421..00000000000 --- a/bdb/docs/api_c/env_set_lg_dir.html +++ /dev/null @@ -1,73 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_lg_dir - - - - - - - -
-

DBENV->set_lg_dir

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_lg_dir(DB_ENV *dbenv, const char *dir);
-

-

Description

-

The path of a directory to be used as the location of logging files. -Log files created by the Log Manager subsystem will be created in this -directory. -

If no logging directory is specified, log files are created in the -environment home directory. See Berkeley DB File Naming for more information. -

For the greatest degree of recoverability from system or application -failure, database files and log files should be located on separate -physical devices. -

The DBENV->set_lg_dir interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_lg_dir function returns a non-zero error value on failure and 0 on success. -

The database environment's logging directory may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_lg_dir", one or more whitespace characters, -and the directory name. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_lg_max.html b/bdb/docs/api_c/env_set_lg_max.html deleted file mode 100644 index 4625db4346b..00000000000 --- a/bdb/docs/api_c/env_set_lg_max.html +++ /dev/null @@ -1,68 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_lg_max - - - - - - - -
-

DBENV->set_lg_max

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_lg_max(DB_ENV *dbenv, u_int32_t lg_max);
-

-

Description

-

Set the maximum size of a single file in the log, in bytes. Because -DB_LSN file offsets are unsigned 4-byte values, the set value may -not be larger than the maximum unsigned 4-byte value. By default, or if -the value is set to 0, a size of 10MB is used. -

See Log File Limits -for more information. -

The DBENV->set_lg_max interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_lg_max function returns a non-zero error value on failure and 0 on success. -

The database environment's log file size may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_lg_max", one or more whitespace characters, -and the size in bytes. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

The specified log file size was too large. -

-

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_lk_conflicts.html b/bdb/docs/api_c/env_set_lk_conflicts.html deleted file mode 100644 index 689464736ef..00000000000 --- a/bdb/docs/api_c/env_set_lk_conflicts.html +++ /dev/null @@ -1,69 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_lk_conflicts - - - - - - - -
-

DBENV->set_lk_conflicts

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_lk_conflicts(DB_ENV *dbenv,
-    u_int8_t *conflicts, int nmodes);
-

-

Description

-

Set the locking conflicts matrix. -The conflicts argument -is an nmodes by nmodes array. -A non-0 value for the array element: -

conflicts[requested_mode][held_mode]
-

indicates that requested_mode and held_mode conflict. The -not-granted mode must be represented by 0. -

If no conflicts value is specified, the conflicts array -db_rw_conflicts is used; see Standard Lock Modes for a description of that array. -

The DBENV->set_lk_conflicts interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_lk_conflicts function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

-

ENOMEM
No memory was available to copy the conflicts array. -
-

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_lk_detect.html b/bdb/docs/api_c/env_set_lk_detect.html deleted file mode 100644 index 460651a0dab..00000000000 --- a/bdb/docs/api_c/env_set_lk_detect.html +++ /dev/null @@ -1,72 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_lk_detect - - - - - - - -
-

DBENV->set_lk_detect

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_lk_detect(DB_ENV *dbenv, u_int32_t detect);
-

-

Description

-

Set if the deadlock detector is to be run whenever a lock conflict occurs, -and specify which transaction should be aborted in the case of a deadlock. -The specified value must be one of the following list: -

-

DB_LOCK_DEFAULT
Use the default policy as specified by db_deadlock. -
DB_LOCK_OLDEST
Abort the oldest transaction. -
DB_LOCK_RANDOM
Abort a random transaction involved in the deadlock. -
DB_LOCK_YOUNGEST
Abort the youngest transaction. -
-

The DBENV->set_lk_detect interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_lk_detect function returns a non-zero error value on failure and 0 on success. -

The database environment's deadlock detector configuration may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_lk_detect", one or more whitespace characters, -and the interface detect argument as a string, for example, -"set_lk_detect DB_LOCK_OLDEST". Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_lk_max.html b/bdb/docs/api_c/env_set_lk_max.html deleted file mode 100644 index 1e9832b59d9..00000000000 --- a/bdb/docs/api_c/env_set_lk_max.html +++ /dev/null @@ -1,72 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_lk_max - - - - - - - -
-

DBENV->set_lk_max

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_lk_max(DB_ENV *dbenv, u_int32_t max);
-

-

Description

-

The DBENV->set_lk_max function interface has been deprecated in favor of -the DBENV->set_lk_max_locks, DBENV->set_lk_max_lockers, -and DBENV->set_lk_max_objects functions. Please update your applications. -

Set each of the maximum number of locks, lockers and lock objects -supported by the Berkeley DB lock subsystem to max. This value is -used by DBENV->open to estimate how much space to allocate for -various lock-table data structures. For specific information on -configuring the size of the lock subsystem, see -Configuring locking: sizing the -system. -

The DBENV->set_lk_max interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_lk_max function returns a non-zero error value on failure and 0 on success. -

The database environment's maximum number of locks may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_lk_max", one or more whitespace characters, -and the number of locks. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_lk_max_lockers.html b/bdb/docs/api_c/env_set_lk_max_lockers.html deleted file mode 100644 index e41a943fd56..00000000000 --- a/bdb/docs/api_c/env_set_lk_max_lockers.html +++ /dev/null @@ -1,68 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_lk_max_lockers - - - - - - - -
-

DBENV->set_lk_max_lockers

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_lk_max_lockers(DB_ENV *dbenv, u_int32_t max);
-

-

Description

-

Set the maximum number of simultaneous locking entities supported by -the Berkeley DB lock subsystem. This value is used by DBENV->open to -estimate how much space to allocate for various lock-table data -structures. For specific information on configuring the size of the -lock subsystem, see -Configuring locking: sizing the system. -

The DBENV->set_lk_max_lockers interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_lk_max_lockers function returns a non-zero error value on failure and 0 on success. -

The database environment's maximum number of lockers may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_lk_max_lockers", one or more whitespace characters, -and the number of lockers. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_lk_max_locks.html b/bdb/docs/api_c/env_set_lk_max_locks.html deleted file mode 100644 index a908b288f97..00000000000 --- a/bdb/docs/api_c/env_set_lk_max_locks.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_lk_max_locks - - - - - - - -
-

DBENV->set_lk_max_locks

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_lk_max_locks(DB_ENV *dbenv, u_int32_t max);
-

-

Description

-

Set the maximum number of locks supported by the Berkeley DB lock subsystem. -This value is used by DBENV->open to estimate how much space to -allocate for various lock-table data structures. For specific -information on configuring the size of the lock subsystem, see -Configuring locking: sizing the system. -

The DBENV->set_lk_max_locks interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_lk_max_locks function returns a non-zero error value on failure and 0 on success. -

The database environment's maximum number of locks may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_lk_max_locks", one or more whitespace characters, -and the number of locks. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_lk_max_objects.html b/bdb/docs/api_c/env_set_lk_max_objects.html deleted file mode 100644 index 8fba15876cf..00000000000 --- a/bdb/docs/api_c/env_set_lk_max_objects.html +++ /dev/null @@ -1,68 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_lk_max_objects - - - - - - - -
-

DBENV->set_lk_max_objects

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_lk_max_objects(DB_ENV *dbenv, u_int32_t max);
-

-

Description

-

Set the maximum number of simultaneously locked objects supported by -the Berkeley DB lock subsystem. This value is used by DBENV->open to -estimate how much space to allocate for various lock-table data -structures. For specific information on configuring the size of the -lock subsystem, see -Configuring locking: sizing the system. -

The DBENV->set_lk_max_objects interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_lk_max_objects function returns a non-zero error value on failure and 0 on success. -

The database environment's maximum number of objects may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_lk_max_objects", one or more whitespace characters, -and the number of objects. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_mp_mmapsize.html b/bdb/docs/api_c/env_set_mp_mmapsize.html deleted file mode 100644 index 3f87a140a15..00000000000 --- a/bdb/docs/api_c/env_set_mp_mmapsize.html +++ /dev/null @@ -1,71 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_mp_mmapsize - - - - - - - -
-

DBENV->set_mp_mmapsize

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_mp_mmapsize(DB_ENV *dbenv, size_t mp_mmapsize);
-

-

Description

-

Files that are opened read-only in the pool (and that satisfy a few other -criteria) are, by default, mapped into the process address space instead -of being copied into the local cache. This can result in better-than-usual -performance, as available virtual memory is normally much larger than the -local cache, and page faults are faster than page copying on many systems. -However, in the presence of limited virtual memory it can cause resource -starvation, and in the presence of large databases, it can result in immense -process sizes. -

Set the maximum file size, in bytes, for a file to be mapped into the -process address space. If no value is specified, it defaults to 10MB. -

The DBENV->set_mp_mmapsize interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_mp_mmapsize function returns a non-zero error value on failure and 0 on success. -

The database environment's maximum mapped file size may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_mp_mmapsize", one or more whitespace characters, -and the size in bytes. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_mutexlocks.html b/bdb/docs/api_c/env_set_mutexlocks.html deleted file mode 100644 index a5fa2aa34c6..00000000000 --- a/bdb/docs/api_c/env_set_mutexlocks.html +++ /dev/null @@ -1,59 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_mutexlocks - - - - - - - -
-

DBENV->set_mutexlocks

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_mutexlocks(DB_ENV *dbenv, int do_lock);
-

-

Description

-

Toggle mutex locks. Setting do_lock to a zero value causes -Berkeley DB to grant all requested mutual exclusion mutexes without regard -for their availability. -

This functionality should never be used for any other purpose than -debugging. -

The DBENV->set_mutexlocks interface may be used to configure Berkeley DB at any time -during the life of the application. -

The DBENV->set_mutexlocks function returns a non-zero error value on failure and 0 on success. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_pageyield.html b/bdb/docs/api_c/env_set_pageyield.html deleted file mode 100644 index 95372408525..00000000000 --- a/bdb/docs/api_c/env_set_pageyield.html +++ /dev/null @@ -1,68 +0,0 @@ - - - - - -Berkeley DB: db_env_set_pageyield - - - - - - - -
-

db_env_set_pageyield

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_pageyield(int pageyield);
-

-

Description

-

Yield the processor whenever requesting a page from the cache. Setting -pageyield to a non-zero value causes Berkeley DB to yield the processor -any time a thread requests a page from the cache. -

The db_env_set_pageyield interface affects the entire application, not a single -database or database environment. -

While the db_env_set_pageyield interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

This functionality should never be used for any other purpose than stress -testing. -

The db_env_set_pageyield interface may be used to configure Berkeley DB at any time -during the life of the application. -

The db_env_set_pageyield function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_paniccall.html b/bdb/docs/api_c/env_set_paniccall.html deleted file mode 100644 index a9d58a80b83..00000000000 --- a/bdb/docs/api_c/env_set_paniccall.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - - - -Berkeley DB: DBENV->set_paniccall - - - - - - - -
-

DBENV->set_paniccall

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_paniccall(DB_ENV *dbenv,
-    void (*paniccall)(DB_ENV *, int errval));
-

-

Description

-

Errors can occur in the Berkeley DB library where the only solution is to shut -down the application and run recovery. (For example, if Berkeley DB is unable -to write log records to disk because there is insufficient disk space.) -In these cases, the value DB_RUNRECOVERY is returned by Berkeley DB. -

In these cases, it is also often simpler to shut down the application when -such errors occur rather than attempting to gracefully return up the stack. -The DBENV->set_paniccall function is used to specify a function to be called when -DB_RUNRECOVERY is about to be returned from a Berkeley DB method. When -called, the dbenv argument will be a reference to the current -environment, and the errval argument is the error value that would -have been returned to the calling function. -

The DBENV->set_paniccall interface may be used to configure Berkeley DB at any time -during the life of the application. -

The DBENV->set_paniccall function returns a non-zero error value on failure and 0 on success. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_panicstate.html b/bdb/docs/api_c/env_set_panicstate.html deleted file mode 100644 index 6168ad9af7e..00000000000 --- a/bdb/docs/api_c/env_set_panicstate.html +++ /dev/null @@ -1,64 +0,0 @@ - - - - - -Berkeley DB: db_env_set_panicstate - - - - - - - -
-

db_env_set_panicstate

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_panicstate(int panic);
-

-

Description

-

Toggle the Berkeley DB panic state. Setting panic to a non-zero value -causes Berkeley DB to refuse attempts to call Berkeley DB functions with the -DB_RUNRECOVERY error return. -

The db_env_set_panicstate interface affects the entire application, not a single -database or database environment. -

While the db_env_set_panicstate interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_panicstate function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_rec_init.html b/bdb/docs/api_c/env_set_rec_init.html deleted file mode 100644 index 056ec9b717c..00000000000 --- a/bdb/docs/api_c/env_set_rec_init.html +++ /dev/null @@ -1,71 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_recovery_init - - - - - - - -
-

DBENV->set_recovery_init

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_recovery_init(DB_ENV *,
-    int (*db_recovery_init_fcn)(DB_ENV *));
-

-

Description

-

Applications installing application-specific recovery functions need -to be called before Berkeley DB performs recovery so they may add their recovery -functions to Berkeley DB's. -

The DBENV->set_recovery_init function supports this functionality. The -db_recovery_init_fcn function must be declared with one -argument, a reference to the enclosing Berkeley DB environment. This -function will be called after the DBENV->open has been called, -but before recovery is started. -

If the db_recovery_init_fcn function returns a non-zero value, -no recovery will be performed and DBENV->open will return the same -value to its caller. -

The DBENV->set_recovery_init interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_recovery_init function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_region_init.html b/bdb/docs/api_c/env_set_region_init.html deleted file mode 100644 index 3c83680ada9..00000000000 --- a/bdb/docs/api_c/env_set_region_init.html +++ /dev/null @@ -1,77 +0,0 @@ - - - - - -Berkeley DB: db_env_set_region_init - - - - - - - -
-

db_env_set_region_init

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_region_init(int region_init);
-

-

Description

-

Page-fault shared regions into memory when initially creating or joining -a Berkeley DB environment. In some applications, the expense of page-faulting -the shared memory regions can affect performance, e.g., when the -page-fault occurs while holding a lock, other lock requests can convoy -and overall throughput may decrease. Setting region_init to a -non-zero value specifies that shared regions be read or written, as -appropriate, when the region is joined by the application. This forces -the underlying virtual memory and file systems to instantiate both the -necessary memory and the necessary disk space. This can also avoid -out-of-disk space failures later on. -

The db_env_set_region_init interface affects the entire application, not a single -database or database environment. -

While the db_env_set_region_init interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_region_init function returns a non-zero error value on failure and 0 on success. -

The database environment's initial behavior with respect to shared memory regions may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_region_init", one or more whitespace characters, -and the string "1". Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_server.html b/bdb/docs/api_c/env_set_server.html deleted file mode 100644 index 586887bfc96..00000000000 --- a/bdb/docs/api_c/env_set_server.html +++ /dev/null @@ -1,77 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_server - - - - - - - -
-

DBENV->set_server

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_server(DB_ENV *dbenv, char *host,
-    long cl_timeout, long sv_timeout, u_int32_t flags);
-

-

Description

-

Connects to the DB server on the indicated hostname and sets up a channel -for communication. -

The cl_timeout argument specifies the number of seconds the client -should wait for results to come back from the server. Once the timeout -has expired on any communication with the server, DB_NOSERVER will -be returned. If this value is zero, a default timeout is used. -

The sv_timeout argument specifies the number of seconds the server -should allow a client connection to remain idle before assuming that -client is gone. Once that timeout has been reached, the server releases -all resources associated with that client connection. Subsequent attempts -by that client to communicate with the server result in -DB_NOSERVER_ID indicating that an invalid identifier has been -given to the server. This value can be considered a hint to the server. -The server may alter this value based on its own policies or allowed -values. If this value is zero, a default timeout is used. -

The flags parameter is currently unused, and must be set to 0. -

When the DBENV->set_server function has been called, any subsequent calls -to Berkeley DB library interfaces may return either DB_NOSERVER or -DB_NOSERVER_ID. -

The DBENV->set_server function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

dbenv_set_server -

-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_shm_key.html b/bdb/docs/api_c/env_set_shm_key.html deleted file mode 100644 index 8de32ed842a..00000000000 --- a/bdb/docs/api_c/env_set_shm_key.html +++ /dev/null @@ -1,87 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_shm_key - - - - - - - -
-

DBENV->set_shm_key

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_shm_key(DB_ENV *dbenv, long shm_key);
-

-

Description

-

Specify a base segment ID for Berkeley DB environment shared memory regions -created in system memory on VxWorks or systems supporting X/Open-style -shared memory interfaces, e.g., UNIX systems supporting -shmget(2) and related System V IPC interfaces. -

This base segment ID will be used when Berkeley DB shared memory regions are -first created. It will be incremented a small integer value each time -a new shared memory region is created, that is, if the base ID is 35, -the first shared memory region created will have a segment ID of 35 and -the next one a segment ID between 36 and 40 or so. A Berkeley DB environment -always creates a master shared memory region, plus an additional shared -memory region for each of the subsystems supported by the environment -(locking, logging, memory pool and transaction), plus an additional -shared memory region for each additional memory pool cache that is -supported. Already existing regions with the same segment IDs will be -removed. See Shared Memory Regions -for more information. -

The intent behind this interface is two-fold: without it, applications -have no way to ensure that two Berkeley DB applications don't attempt to use -the same segment IDs when creating different Berkeley DB environments. In -addition, by using the same segment IDs each time the environment is -created, previously created segments will be removed, and the set of -segments on the system will not grow without bound. -

The DBENV->set_shm_key interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_shm_key function returns a non-zero error value on failure and 0 on success. -

The database environment's base segment ID may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_shm_key", one or more whitespace characters, -and the ID. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_tas_spins.html b/bdb/docs/api_c/env_set_tas_spins.html deleted file mode 100644 index 633dcda077e..00000000000 --- a/bdb/docs/api_c/env_set_tas_spins.html +++ /dev/null @@ -1,70 +0,0 @@ - - - - - -Berkeley DB: db_env_set_tas_spins - - - - - - - -
-

db_env_set_tas_spins

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_tas_spins(u_int32_t tas_spins);
-

-

Description

-

Specify that test-and-set mutexes should spin tas_spins times -without blocking. The value defaults to 1 on uniprocessor systems and -to 50 times the number of processors on multiprocessor systems. -

The db_env_set_tas_spins interface affects the entire application, not a single -database or database environment. -

While the db_env_set_tas_spins interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_tas_spins function returns a non-zero error value on failure and 0 on success. -

The database environment's test-and-set spin count may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_tas_spins", one or more whitespace characters, -and the number of spins. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_tmp_dir.html b/bdb/docs/api_c/env_set_tmp_dir.html deleted file mode 100644 index 05f3bed5da0..00000000000 --- a/bdb/docs/api_c/env_set_tmp_dir.html +++ /dev/null @@ -1,89 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_tmp_dir - - - - - - - -
-

DBENV->set_tmp_dir

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_tmp_dir(DB_ENV *dbenv, const char *dir);
-

-

Description

-

The path of a directory to be used as the location of temporary files. -The files created to back in-memory access method databases will be -created relative to this path. These temporary files can be quite large, -depending on the size of the database. -

If no directories are specified, the following alternatives are checked -in the specified order. The first existing directory path is used for -all temporary files. -

    -

  1. The value of the environment variable TMPDIR. -
  2. The value of the environment variable TEMP. -
  3. The value of the environment variable TMP. -
  4. The value of the environment variable TempFolder. -
  5. The value returned by the GetTempPath interface. -
  6. The directory /var/tmp. -
  7. The directory /usr/tmp. -
  8. The directory /temp. -
  9. The directory /tmp. -
  10. The directory C:/temp. -
  11. The directory C:/tmp. -
-

Note: environment variables are only checked if one of the -DB_USE_ENVIRON or DB_USE_ENVIRON_ROOT flags were -specified. -

Note: the GetTempPath interface is only checked on Win/32 platforms. -

The DBENV->set_tmp_dir interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_tmp_dir function returns a non-zero error value on failure and 0 on success. -

The database environment's temporary file directory may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_tmp_dir", one or more whitespace characters, -and the directory name. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_tx_max.html b/bdb/docs/api_c/env_set_tx_max.html deleted file mode 100644 index 82328955237..00000000000 --- a/bdb/docs/api_c/env_set_tx_max.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_tx_max - - - - - - - -
-

DBENV->set_tx_max

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_tx_max(DB_ENV *dbenv, u_int32_t tx_max);
-

-

Description

-

Set the maximum number of active transactions that are supported by the -environment. This value bounds the size of backing shared memory regions. -Note that child transactions must be counted as active until their -ultimate parent commits or aborts. -

When there are more than the specified number of concurrent transactions, -calls to txn_begin will fail (until some active transactions -complete). If no value is specified, a default value of 20 is used. -

The DBENV->set_tx_max interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_tx_max function returns a non-zero error value on failure and 0 on success. -

The database environment's maximum number of active transactions may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_tx_max", one or more whitespace characters, -and the number of transactions. Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_tx_recover.html b/bdb/docs/api_c/env_set_tx_recover.html deleted file mode 100644 index 9295537b5f5..00000000000 --- a/bdb/docs/api_c/env_set_tx_recover.html +++ /dev/null @@ -1,75 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_tx_recover - - - - - - - -
-

DBENV->set_tx_recover

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_tx_recover(DB_ENV *dbenv,
-    int (*tx_recover)(DB_ENV *dbenv,
-    DBT *log_rec, DB_LSN *lsn, db_recops op));
-

-

Description

-

Set the application's function to be called during transaction abort -and recovery. This function must return 0 on success and either -errno or a value outside of the Berkeley DB error name space on -failure. It takes four arguments: -

-

dbenv
A Berkeley DB environment. -

log_rec
A log record. -

lsn
A log sequence number. -

op
One of the following values: -

-

DB_TXN_BACKWARD_ROLL
The log is being read backward to determine which transactions have been -committed and to abort those operations that were not, undo the operation -described by the log record. -

DB_TXN_FORWARD_ROLL
The log is being played forward, redo the operation described by the log -record. -

DB_TXN_ABORT
The log is being read backwards during a transaction abort, undo the -operation described by the log record. -
-
-

The DBENV->set_tx_recover interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_tx_recover function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

Called after DBENV->open was called. -

-

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_tx_timestamp.html b/bdb/docs/api_c/env_set_tx_timestamp.html deleted file mode 100644 index 68cd0d15723..00000000000 --- a/bdb/docs/api_c/env_set_tx_timestamp.html +++ /dev/null @@ -1,63 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_tx_timestamp - - - - - - - -
-

DBENV->set_tx_timestamp

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_tx_timestamp(DB_ENV *dbenv, time_t *timestamp);
-

-

Description

-

Recover to the time specified by timestamp rather than to the most -current possible date. -The timestamp argument should be the number of seconds since 0 -hours, 0 minutes, 0 seconds, January 1, 1970, Coordinated Universal Time, -i.e., the Epoch. -

Once a database environment has been upgraded to a new version of Berkeley DB -involving a log format change (see Upgrading Berkeley DB installations, it is no longer possible to recover -to a specific time before that upgrade. -

The DBENV->set_tx_timestamp interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The DBENV->set_tx_timestamp function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -

It is not possible to recover to the specified time using the -log files currently present in the environment. -

-

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_set_verbose.html b/bdb/docs/api_c/env_set_verbose.html deleted file mode 100644 index 605fd577cca..00000000000 --- a/bdb/docs/api_c/env_set_verbose.html +++ /dev/null @@ -1,78 +0,0 @@ - - - - - -Berkeley DB: DBENV->set_verbose - - - - - - - -
-

DBENV->set_verbose

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-DBENV->set_verbose(DB_ENV *dbenv, u_int32_t which, int onoff);
-

-

Description

-

The DBENV->set_verbose function turns additional informational and -debugging messages in the Berkeley DB message output on and off. If -onoff is set to -non-zero, -the additional messages are output. -

The which parameter must be set to one of the following values: -

-

DB_VERB_CHKPOINT
Display checkpoint location information when searching the log for -checkpoints. -

DB_VERB_DEADLOCK
Display additional information when doing deadlock detection. -

DB_VERB_RECOVERY
Display additional information when performing recovery. -

DB_VERB_WAITSFOR
Display the waits-for table when doing deadlock detection. -
-

The DBENV->set_verbose interface may be used to configure Berkeley DB at any time -during the life of the application. -

The DBENV->set_verbose function returns a non-zero error value on failure and 0 on success. -

The database environment's verbosity may also be set using the environment's -DB_CONFIG file. The syntax of the entry in that file is a -single line with the string "set_verbose", one or more whitespace characters, -and the interface which argument as a string, for example, -"set_verbose DB_VERB_CHKPOINT". Because the DB_CONFIG file is read when the database -environment is opened, it will silently overrule configuration done -before that time. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_strerror.html b/bdb/docs/api_c/env_strerror.html deleted file mode 100644 index e6bd190a2ea..00000000000 --- a/bdb/docs/api_c/env_strerror.html +++ /dev/null @@ -1,60 +0,0 @@ - - - - - -Berkeley DB: db_strerror - - - - - - - -
-

db_strerror

-		 -APIRef -
-

- -

-#include <db.h>
-

-char *
-db_strerror(int error);
-

-

Description

-

The db_strerror function returns an error message string corresponding -to the error number error. This interface is a superset of the -ANSI C X3.159-1989 (ANSI C) strerror(3) interface. If the error number -error is greater than or equal to 0, then the string returned by -the system interface strerror(3) is returned. If the error -number is less than 0, an error string appropriate to the corresponding -Berkeley DB library error is returned. See -Error returns to applications -for more information. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/env_version.html b/bdb/docs/api_c/env_version.html deleted file mode 100644 index fa7704aaea2..00000000000 --- a/bdb/docs/api_c/env_version.html +++ /dev/null @@ -1,57 +0,0 @@ - - - - - -Berkeley DB: db_version - - - - - - - -
-

db_version

-		 -APIRef -
-

- -

-#include <db.h>
-

-char *
-db_version(int *major, int *minor, int *patch);
-

-

Description

-

The db_version function returns a pointer to a string containing Berkeley DB -version information. If major is non-NULL, the major version -of the Berkeley DB release is stored in the memory it references. If -minor is non-NULL, the minor version of the Berkeley DB release is -stored in the memory it references. If patch is non-NULL, the -patch version of the Berkeley DB release is stored in the memory it references. -

See Also

-DBENV->close, -db_env_create, -DBENV->open, -DBENV->remove, -DBENV->err, -db_strerror, -db_version, -DBENV->set_cachesize, -DBENV->set_errcall, -DBENV->set_errfile, -DBENV->set_errpfx, -DBENV->set_flags, -DBENV->set_mutexlocks, -DBENV->set_paniccall, -and -DBENV->set_verbose. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/hsearch.html b/bdb/docs/api_c/hsearch.html deleted file mode 100644 index 0d6d6ce51ed..00000000000 --- a/bdb/docs/api_c/hsearch.html +++ /dev/null @@ -1,107 +0,0 @@ - - - - - -Berkeley DB: hsearch - - - - - - - -
-

hsearch

-		 -APIRef -
-

- -

-#define DB_DBM_HSEARCH    1
-#include <db.h>
-

-typedef enum {
-        FIND, ENTER
-} ACTION;
-

-typedef struct entry {
-        char *key;
-        void *data;
-} ENTRY;
-

-ENTRY *
-hsearch(ENTRY item, ACTION action);
-

-int
-hcreate(size_t nelem);
-

-void
-hdestroy(void);
-

-

Description

-

The hsearch interface to the Berkeley DB library is intended to -provide a high-performance implementation and source code compatibility -for applications written to the historic hsearch interface. -It is not recommended for any other purpose. -

To compile hsearch applications, replace the application's -#include of the hsearch include -file (e.g., #include <search.h>) -with the following two lines: -

-#define DB_DBM_HSEARCH    1
-#include <db.h>
-

and recompile. -

The hcreate function creates an in-memory database. The -nelem argument is an estimation of the maximum number of key/data -pairs that will be stored in the database. -

The hdestroy function discards the database. -

Database elements are structures of type ENTRY, which contain at -least two fields: key and data. The field key is -declared to be of type char * and is the key used for storage -and retrieval. The field data is declared to be of type -void * and is its associated data. -

The hsearch function retrieves key/data pairs from, and stores -key/data pairs into the database. -

The action argument must be set to one of two values: -

-

ENTER
If the key does not already appear in the database, -insert the key/data pair into the database. -If the key already appears in the database, -return a reference to an ENTRY -structure referencing the existing key and its associated data element. -

FIND
Retrieve the specified key/data pair from the database. -
-

Compatibility Notes

-

Historically, hsearch required applications to maintain the keys -and data in the application's memory for as long as the hsearch -database existed. As Berkeley DB handles key and data management internally, -there is no requirement that applications maintain local copies of key -and data items, although the only effect of doing so should be the -allocation of additional memory. -

Hsearch Diagnostics

-

The hcreate function returns 0 on failure, setting errno -and non-zero on success. -

The hsearch function returns a pointer to an ENTRY structure on -success, and NULL, setting errno, if the action -specified was FIND and the item did not appear in the database. -

Errors

-

The hcreate 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 hcreate function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

The hsearch 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 hsearch function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

In addition, the hsearch function will fail, setting errno -to 0, if the action specified was FIND and the item did not appear in -the database. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/lock_detect.html b/bdb/docs/api_c/lock_detect.html deleted file mode 100644 index 7b95e98e9d0..00000000000 --- a/bdb/docs/api_c/lock_detect.html +++ /dev/null @@ -1,73 +0,0 @@ - - - - - -Berkeley DB: lock_detect - - - - - - - -
-

lock_detect

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-lock_detect(DB_ENV *env,
-	u_int32_t flags, u_int32_t atype, int *aborted);
-

-

Description

-

The lock_detect function runs one iteration of the deadlock detector. -The deadlock detector traverses the lock table, and for each deadlock -it finds, marks one of the participating transactions for abort. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_LOCK_CONFLICT
Only run the deadlock detector if a lock conflict has occurred since -the last time that the deadlock detector was run. -
-

The atype parameter specifies which transaction to abort in the -case of deadlock. It must be set to one of possible arguments listed for -the DBENV->set_lk_detect interface. -

If the aborted parameter is non-NULL, the memory location it -references will be set to the number of transactions aborted by the -lock_detect function. -

The lock_detect function is the underlying function used by the db_deadlock utility. -See the db_deadlock utility source code for an example of using lock_detect -in a IEEE/ANSI Std 1003.1 (POSIX) environment. -

The lock_detect function returns a non-zero error value on failure and 0 on success. -

Errors

-

The lock_detect 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 lock_detect function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/lock_get.html b/bdb/docs/api_c/lock_get.html deleted file mode 100644 index 8d68ba54cb9..00000000000 --- a/bdb/docs/api_c/lock_get.html +++ /dev/null @@ -1,91 +0,0 @@ - - - - - -Berkeley DB: lock_get - - - - - - - -
-

lock_get

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-lock_get(DB_ENV *env, u_int32_t locker,
-    u_int32_t flags, const DBT *obj,
-    const db_lockmode_t lock_mode, DB_LOCK *lock);
-

-

Description

-

The lock_get function acquires a lock from the lock table, returning -information about it in -the lock argument. -

The locker argument specified to lock_get is an unsigned -32-bit integer quantity. It represents the entity requesting or releasing -the lock. -

The flags value must be set to 0 or the following value: -

-

DB_LOCK_NOWAIT
If a lock cannot be granted because the requested lock conflicts with an -existing lock, return immediately instead of waiting for the lock to -become available. -
-

The obj argument is an untyped byte string that specifies the -object to be locked or released. -

The mode argument is an index into the environment's lock conflict -array. See DBENV->set_lk_conflicts and -Standard Lock Modes -for a description of that array. -

The lock_get function may -return -one of the following values: -

-

DB_LOCK_NOTGRANTED
A lock was requested that could not be immediately granted and the -flags parameter was set to DB_LOCK_NOWAIT. -
-

Otherwise, the lock_get function returns a non-zero error value on failure and 0 on success. -

Errors

-

The lock_get function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

EINVAL
An invalid flag value or parameter was specified. -
-

-

ENOMEM
The maximum number of locks has been reached. -
-

The lock_get 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 lock_get function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/lock_id.html b/bdb/docs/api_c/lock_id.html deleted file mode 100644 index bd720cdb00e..00000000000 --- a/bdb/docs/api_c/lock_id.html +++ /dev/null @@ -1,57 +0,0 @@ - - - - - -Berkeley DB: lock_id - - - - - - - -
-

lock_id

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-lock_id(DB_ENV *env, u_int32_t *idp);
-

-

Description

-

The lock_id function -copies a locker ID, which is guaranteed to be unique in the specified lock -table, into the memory location referenced by idp. -

The lock_id function returns a non-zero error value on failure and 0 on success. -

Errors

-

The lock_id 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 lock_id function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/lock_put.html b/bdb/docs/api_c/lock_put.html deleted file mode 100644 index 777f4bdd09b..00000000000 --- a/bdb/docs/api_c/lock_put.html +++ /dev/null @@ -1,59 +0,0 @@ - - - - - -Berkeley DB: lock_put - - - - - - - -
-

lock_put

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-lock_put(DB_ENV *env, DB_LOCK *lock);
-

-

Description

-

The lock_put function releases lock from the lock table. -

The lock_put function returns a non-zero error value on failure and 0 on success. -

Errors

-

The lock_put function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The lock_put 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 lock_put function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/lock_stat.html b/bdb/docs/api_c/lock_stat.html deleted file mode 100644 index c86024de7f9..00000000000 --- a/bdb/docs/api_c/lock_stat.html +++ /dev/null @@ -1,92 +0,0 @@ - - - - - -Berkeley DB: lock_stat - - - - - - - -
-

lock_stat

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-lock_stat(DB_ENV *env,
-    DB_LOCK_STAT **statp, void *(*db_malloc)(size_t));
-

-

Description

-

The lock_stat function -creates a statistical structure and copies a pointer to it into a -user-specified memory location. -

Statistical structures are created in allocated memory. If db_malloc is non-NULL, it -is called to allocate the memory, otherwise, the library function -malloc(3) is used. The function db_malloc must match -the calling conventions of the malloc(3) library routine. -Regardless, the caller is responsible for deallocating the returned -memory. To deallocate returned memory, free the returned memory -reference, references inside the returned memory do not need to be -individually freed. -

The lock region statistics are stored in a structure of type -DB_LOCK_STAT. The following DB_LOCK_STAT fields will be filled in: -

-
u_int32_t st_lastid;
The last allocated lock ID. -
u_int32_t st_nmodes;
The number of lock modes. -
u_int32_t st_maxlocks;
The maximum number of locks possible. -
u_int32_t st_maxlockers;
The maximum number of lockers possible. -
u_int32_t st_maxobjects;
The maximum number of objects possible. -
u_int32_t st_nlocks;
The number of current locks. -
u_int32_t st_maxnlocks;
The maximum number of locks at any one time. -
u_int32_t st_nlockers;
The number of current lockers. -
u_int32_t st_maxnlockers;
The maximum number of lockers at any one time. -
u_int32_t st_nobjects;
The number of current objects. -
u_int32_t st_maxnobjects;
The maximum number of objects at any one time. -
u_int32_t st_nrequests;
The total number of locks requested. -
u_int32_t st_nreleases;
The total number of locks released. -
u_int32_t st_nnowaits;
The total number of lock requests that failed because -DB_LOCK_NOWAIT was set. -
u_int32_t st_nconflicts;
The total number of locks not immediately available due to conflicts. -
u_int32_t st_ndeadlocks;
The number of deadlocks detected. -
u_int32_t st_regsize;
The size of the region. -
u_int32_t st_region_wait;
The number of times that a thread of control was forced to wait before -obtaining the region lock. -
u_int32_t st_region_nowait;
The number of times that a thread of control was able to obtain -the region lock without waiting. -
-

The lock_stat function returns a non-zero error value on failure and 0 on success. -

Errors

-

The lock_stat 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 lock_stat function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/lock_vec.html b/bdb/docs/api_c/lock_vec.html deleted file mode 100644 index 56d3fa96a98..00000000000 --- a/bdb/docs/api_c/lock_vec.html +++ /dev/null @@ -1,123 +0,0 @@ - - - - - -Berkeley DB: lock_vec - - - - - - - -
-

lock_vec

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-lock_vec(DB_ENV *env, u_int32_t locker, u_int32_t flags,
-    DB_LOCKREQ list[], int nlist, DB_LOCKREQ **elistp);
-

-

Description

-

The lock_vec function atomically obtains and releases one or more locks -from the lock table. The lock_vec function is intended to support -acquisition or trading of multiple locks under one lock table semaphore, -as is needed for lock coupling or in multigranularity locking for lock -escalation. -

The locker argument specified to lock_vec is an unsigned -32-bit integer quantity. It represents the entity requesting or releasing -the lock. -

The flags value must be set to 0 or the following value: -

-

DB_LOCK_NOWAIT
If a lock cannot be immediately granted because the requested lock -conflicts with an existing lock, return instead of waiting for the lock -to become available. -
-

The list array provided to lock_vec is typedef'd as -DB_LOCKREQ. A DB_LOCKREQ structure has at least the following fields, -which must be initialized before calling lock_vec: -

-

lockop_t op;
The operation to be performed, which must be set to one of the -following values: -

-

DB_LOCK_GET
Get a lock, as defined by the values of locker, obj, -and mode. Upon return from lock_vec, if the -lock field is non-NULL, a reference to the acquired lock is -stored there. (This reference is invalidated by any call to -lock_vec or lock_put that releases the lock.) -

DB_LOCK_PUT
The lock referenced by the contents of the lock field is released. -

DB_LOCK_PUT_ALL
All locks held by the locker are released. (Any locks acquired -as a part of the current call to lock_vec that appear after the -DB_LOCK_PUT_ALL entry are not considered for this -operation). -

DB_LOCK_PUT_OBJ
All locks held on the object obj are released. The mode -and locker parameters are ignored. Note that any locks acquired -as a part of the current call to lock_vec that occur before the -DB_LOCK_PUT_OBJ will also be released; those acquired afterwards -will not be released. -
-

const DBT obj;
An untyped byte string that specifies the object to be locked or released. -

const lockmode_t mode;
The lock mode, used as an index into the environment's lock conflict array. -See DBENV->set_lk_conflicts and Standard Lock Modes for a description of that array. -

DB_LOCK lock;
A lock reference. -
-

The nlist argument specifies the number of elements in the -list array. -

If any of the requested locks cannot be acquired, or any of the locks to -be released cannot be released, the operations before the failing -operation are guaranteed to have completed successfully, and -lock_vec returns a non-zero value. In addition, if elistp -is not NULL, it is set to point to the DB_LOCKREQ entry that was being -processed when the error occurred. -

The lock_vec function may -return -one of the following values: -

-

DB_LOCK_NOTGRANTED
A lock was requested that could not be immediately granted and the -flag parameter was set to DB_LOCK_NOWAIT. In this case, if -non-NULL, elistp identifies the request that was not granted. -
-

Otherwise, the lock_vec function returns a non-zero error value on failure and 0 on success. -

Errors

-

The lock_vec function may fail and return a non-zero error for the following conditions: -

-

DB_LOCK_DEADLOCK
The operation was selected to resolve a deadlock. -
-

-

EINVAL
An invalid flag value or parameter was specified. -
-

-

ENOMEM
The maximum number of locks has been reached. -
-

The lock_vec 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 lock_vec function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lk_conflicts, -DBENV->set_lk_detect, -DBENV->set_lk_max_locks, -DBENV->set_lk_max_lockers, -DBENV->set_lk_max_objects, -DBENV->set_lk_max, -lock_detect, -lock_get, -lock_id, -lock_put, -lock_stat -and -lock_vec. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/log_archive.html b/bdb/docs/api_c/log_archive.html deleted file mode 100644 index 6c9aea26b8d..00000000000 --- a/bdb/docs/api_c/log_archive.html +++ /dev/null @@ -1,102 +0,0 @@ - - - - - -Berkeley DB: log_archive - - - - - - - -
-

log_archive

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-log_archive(DB_ENV *env, char *(*listp)[],
-    u_int32_t flags, void *(*db_malloc)(size_t));
-

-

Description

-

The log_archive function -creates a NULL-terminated array of log or database file names and copies -a pointer to them into the user-specified memory location listp. -

By default, log_archive returns the names of all of the log files -that are no longer in use (e.g., no longer involved in active transactions), -and that may safely be archived for catastrophic recovery and then removed -from the system. If there were no file names to return, the memory location -referenced by listp will be set to NULL. -

Arrays of log file names are created in allocated memory. If db_malloc is non-NULL, it -is called to allocate the memory, otherwise, the library function -malloc(3) is used. The function db_malloc must match -the calling conventions of the malloc(3) library routine. -Regardless, the caller is responsible for deallocating the returned -memory. To deallocate returned memory, free the returned memory -reference, references inside the returned memory do not need to be -individually freed. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_ARCH_ABS
All pathnames are returned as absolute pathnames, -instead of relative to the database home directory. -

DB_ARCH_DATA
Return the database files that need to be archived in order to recover -the database from catastrophic failure. If any of the database files -have not been accessed during the lifetime of the current log files, -log_archive will not include them in this list. It is also -possible that some of the files referenced in the log have since been -deleted from the system. -

DB_ARCH_LOG
Return all the log file names regardless of whether or not they are in -use. -
-

The DB_ARCH_DATA and DB_ARCH_LOG flags are mutually -exclusive. -

See the db_archive manual page for more information on database -archival procedures. -

The log_archive function is the underlying function used by the db_archive utility. -See the db_archive utility source code for an example of using log_archive -in a IEEE/ANSI Std 1003.1 (POSIX) environment. -

The log_archive function returns a non-zero error value on failure and 0 on success. -

Bugs

-

In a threaded application (i.e., one where the environment was created -with the DB_THREAD flag specified), calling log_archive with the -DB_ARCH_DATA flag will fail, returning EINVAL. To work around this -problem, re-open the log explicitly without specifying DB_THREAD. This -restriction is expected to be removed in a future version of Berkeley DB. -

Errors

-

The log_archive function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -

The log was corrupted. -

-

The log_archive 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 log_archive function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/log_compare.html b/bdb/docs/api_c/log_compare.html deleted file mode 100644 index c6e7743beb1..00000000000 --- a/bdb/docs/api_c/log_compare.html +++ /dev/null @@ -1,51 +0,0 @@ - - - - - -Berkeley DB: log_compare - - - - - - - -
-

log_compare

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-log_compare(const DB_LSN *lsn0, const DB_LSN *lsn1);
-

-

Description

-

The log_compare function allows the caller to compare two -DB_LSN structures, -returning 0 if they are equal, 1 if lsn0 is greater than -lsn1, and -1 if lsn0 is less than lsn1. -

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/log_file.html b/bdb/docs/api_c/log_file.html deleted file mode 100644 index 434380cccb0..00000000000 --- a/bdb/docs/api_c/log_file.html +++ /dev/null @@ -1,76 +0,0 @@ - - - - - -Berkeley DB: log_file - - - - - - - -
-

log_file

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-log_file(DB_ENV *env,
-    const DB_LSN *lsn, char *namep, size_t len);
-

-

Description

-

The log_file function maps -DB_LSN structures -to file names, -copying the name of the file containing the record named by lsn -into the memory location referenced by namep. -

The len argument is the length of the namep buffer in bytes. -If namep is too short to hold the file name, log_file will -return ENOMEM. -(Log file names are normally quite short, on the order of 10 characters.) -

This mapping of -DB_LSN structures -to files is needed for database administration. For example, a -transaction manager typically records the earliest -DB_LSN -needed for restart, and the database administrator may want to archive -log files to tape when they contain only -DB_LSN -entries before the earliest one needed for restart. -

The log_file function returns a non-zero error value on failure and 0 on success. -

Errors

-

The log_file function may fail and return a non-zero error for the following conditions: -

-

ENOMEM
The supplied buffer was too small to hold the log file name. -
-

The log_file 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 log_file function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/log_flush.html b/bdb/docs/api_c/log_flush.html deleted file mode 100644 index 1315fc10670..00000000000 --- a/bdb/docs/api_c/log_flush.html +++ /dev/null @@ -1,62 +0,0 @@ - - - - - -Berkeley DB: log_flush - - - - - - - -
-

log_flush

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-log_flush(DB_ENV *env, const DB_LSN *lsn);
-

-

Description

-

The log_flush function guarantees that all log records whose -DB_LSN values -are less than or equal to the lsn argument have been -written to disk. If lsn is NULL, all records in the -log are flushed. -

The log_flush function returns a non-zero error value on failure and 0 on success. -

Errors

-

The log_flush function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The log_flush 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 log_flush function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/log_get.html b/bdb/docs/api_c/log_get.html deleted file mode 100644 index 05761e1ea30..00000000000 --- a/bdb/docs/api_c/log_get.html +++ /dev/null @@ -1,114 +0,0 @@ - - - - - -Berkeley DB: log_get - - - - - - - -
-

log_get

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-log_get(DB_ENV *env, DB_LSN *lsn, DBT *data, u_int32_t flags);
-

-

Description

-

The log_get function implements a cursor inside of the log, -retrieving records from the log according to the lsn and -flags arguments. -

The data field of the data structure is set to the record -retrieved and the size field indicates the number of bytes in the record. -See DBT for a description of other fields in the data -structure. When multiple threads are using the returned log handle -concurrently, one of the DB_DBT_MALLOC, DB_DBT_REALLOC or -DB_DBT_USERMEM flags must be specified for any DBT used -for data retrieval. -

The flags argument must be set to exactly one of the following values: -

-

DB_CHECKPOINT
The last record written with the DB_CHECKPOINT flag specified to the -log_put function is returned in the data argument. The -lsn argument is overwritten with the DB_LSN of the record -returned. If no record has been previously written with the DB_CHECKPOINT -flag specified, the first record in the log is returned. -

If the log is empty, the log_get function will return DB_NOTFOUND. -

DB_FIRST
The first record from any of the log files found in the log directory -is returned in the data argument. -The lsn argument is overwritten with the DB_LSN of the -record returned. -

If the log is empty, the log_get function will return DB_NOTFOUND. -

DB_LAST
The last record in the log is returned in the data argument. -The lsn argument is overwritten with the DB_LSN of the -record returned. -

If the log is empty, the log_get function will return DB_NOTFOUND. -

DB_NEXT
The current log position is advanced to the next record in the log and that -record is returned in the data argument. -The lsn argument is overwritten with the DB_LSN of the -record returned. -

If the pointer has not been initialized via DB_FIRST, DB_LAST, DB_SET, -DB_NEXT, or DB_PREV, log_get will return the first record in the log. -If the last log record has already been returned or the log is empty, the -log_get function will return DB_NOTFOUND. -

If the log was opened with the DB_THREAD flag set, calls to -log_get with the DB_NEXT flag set will return EINVAL. -

DB_PREV
The current log position is moved to the previous record in the log and that -record is returned in the data argument. -The lsn argument is overwritten with the DB_LSN of the -record returned. -

If the pointer has not been initialized via DB_FIRST, DB_LAST, DB_SET, -DB_NEXT, or DB_PREV, -log_get will return the last record in the log. -If the first log record has already been returned or the log is empty, the -log_get function will return DB_NOTFOUND. -

If the log was opened with the DB_THREAD flag set, calls to -log_get with the DB_PREV flag set will return EINVAL. -

DB_CURRENT
Return the log record currently referenced by the log. -

If the log pointer has not been initialized via DB_FIRST, DB_LAST, DB_SET, -DB_NEXT, or DB_PREV, or if the log was opened with the DB_THREAD flag set, -log_get will return EINVAL. -

DB_SET
Retrieve the record specified by the lsn argument. If the -specified DB_LSN is invalid (e.g., does not appear in the log) -log_get will return EINVAL. -
-

Otherwise, the log_get function returns a non-zero error value on failure and 0 on success. -

Errors

-

The log_get function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -

The DB_FIRST flag was specified and no log files were found. -

-

The log_get 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 log_get function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/log_put.html b/bdb/docs/api_c/log_put.html deleted file mode 100644 index 9455296986e..00000000000 --- a/bdb/docs/api_c/log_put.html +++ /dev/null @@ -1,81 +0,0 @@ - - - - - -Berkeley DB: log_put - - - - - - - -
-

log_put

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-log_put(DB_ENV *env,
-    DB_LSN *lsn, const DBT *data, u_int32_t flags);
-

-

Description

-

The log_put function appends records to the log. The DB_LSN of -the put record is returned in the lsn argument. The flags -argument may be set to one of the following values: -

-

DB_CHECKPOINT
The log should write a checkpoint record, recording any information -necessary to make the log structures recoverable after a crash. -

DB_CURLSN
The DB_LSN of the next record to be put is returned in the -lsn argument. -

DB_FLUSH
The log is forced to disk after this record is written, guaranteeing -that all records with DB_LSN values less than or equal to the -one being put are on disk before this function returns (this function -is most often used for a transaction commit, see txn_commit for -more information). -

The caller is responsible for providing any necessary structure to -data. (For example, in a write-ahead logging protocol, the -application must understand what part of data is an operation -code, what part is redo information, and what part is undo information. -In addition, most transaction managers will store in data the -DB_LSN of the previous log record for the same transaction, to -support chaining back through the transaction's log records during -undo.) -

-

The log_put function returns a non-zero error value on failure and 0 on success. -

Errors

-

The log_flush function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -

The record to be logged is larger than the maximum log record. -

-

The log_put 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 log_put function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/log_register.html b/bdb/docs/api_c/log_register.html deleted file mode 100644 index e993feabed2..00000000000 --- a/bdb/docs/api_c/log_register.html +++ /dev/null @@ -1,64 +0,0 @@ - - - - - -Berkeley DB: log_register - - - - - - - -
-

log_register

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-log_register(DB_ENV *env, DB *dbp, const char *name);
-

-

Description

-

The log_register function registers a file name with the specified Berkeley DB -environment's log manager. The log manager records all file name mappings -at each checkpoint so that a recovery process can identify the file to -which a record in the log refers. -

The dbp argument should be a reference to the DB structure being -registered. The name argument should be a file name appropriate -for opening the file in the environment, during recovery. -

The log_register function returns a non-zero error value on failure and 0 on success. -

Errors

-

The log_register function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The log_register 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 log_register function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/log_stat.html b/bdb/docs/api_c/log_stat.html deleted file mode 100644 index 819c603d318..00000000000 --- a/bdb/docs/api_c/log_stat.html +++ /dev/null @@ -1,90 +0,0 @@ - - - - - -Berkeley DB: log_stat - - - - - - - -
-

log_stat

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-log_stat(DB_ENV *env,
-    DB_LOG_STAT **spp, void *(*db_malloc)(size_t));
-

-

Description

-

The log_stat function -creates a statistical structure and copies a pointer to it into a -user-specified memory location. -

Statistical structures are created in allocated memory. If db_malloc is non-NULL, it -is called to allocate the memory, otherwise, the library function -malloc(3) is used. The function db_malloc must match -the calling conventions of the malloc(3) library routine. -Regardless, the caller is responsible for deallocating the returned -memory. To deallocate returned memory, free the returned memory -reference, references inside the returned memory do not need to be -individually freed. -

The log region statistics are stored in a structure of type DB_LOG_STAT. -The following DB_LOG_STAT fields will be filled in: -

-
u_int32_t st_magic;
The magic number that identifies a file as a log file. -
u_int32_t st_version;
The version of the log file type. -
u_int32_t st_regsize;
The size of the region. -
int st_mode;
The mode of any created log files. -
u_int32_t st_lg_bsize;
The in-memory log record cache size. -
u_int32_t st_lg_max;
The maximum size of any individual file comprising the log. -
u_int32_t st_w_mbytes;
The number of megabytes written to this log. -
u_int32_t st_w_bytes;
The number of bytes over and above st_w_mbytes written to this log. -
u_int32_t st_wc_mbytes;
The number of megabytes written to this log since the last checkpoint. -
u_int32_t st_wc_bytes;
The number of bytes over and above st_wc_mbytes written to this log -since the last checkpoint. -
u_int32_t st_wcount;
The number of times the log has been written to disk. -
u_int32_t st_wcount_fill;
The number of times the log has been written to disk because the -in-memory log record cache filled up. -
u_int32_t st_scount;
The number of times the log has been flushed to disk. -
u_int32_t st_cur_file;
The current log file number. -
u_int32_t st_cur_offset;
The byte offset in the current log file. -
u_int32_t st_region_wait;
The number of times that a thread of control was forced to wait before -obtaining the region lock. -
u_int32_t st_region_nowait;
The number of times that a thread of control was able to obtain -the region lock without waiting. -
-

The log_stat function returns a non-zero error value on failure and 0 on success. -

Errors

-

The log_stat 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 log_stat function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/log_unregister.html b/bdb/docs/api_c/log_unregister.html deleted file mode 100644 index cfc1e6f2e5d..00000000000 --- a/bdb/docs/api_c/log_unregister.html +++ /dev/null @@ -1,59 +0,0 @@ - - - - - -Berkeley DB: log_unregister - - - - - - - -
-

log_unregister

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-log_unregister(DB_ENV *env, DB *dbp);
-

-

Description

-

The log_unregister function function unregisters the file represented by -the dbp parameter from the Berkeley DB environment's log manager. -

The log_unregister function returns a non-zero error value on failure and 0 on success. -

Errors

-

The log_unregister function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The log_unregister 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 log_unregister function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_lg_bsize, -DBENV->set_lg_max, -log_archive, -log_compare, -log_file, -log_flush, -log_get, -log_put, -log_register, -log_stat -and -log_unregister. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_fclose.html b/bdb/docs/api_c/memp_fclose.html deleted file mode 100644 index ae8ce3c5647..00000000000 --- a/bdb/docs/api_c/memp_fclose.html +++ /dev/null @@ -1,61 +0,0 @@ - - - - - -Berkeley DB: memp_fclose - - - - - - - -
-

memp_fclose

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_fclose(DB_MPOOLFILE *mpf);
-

-

Description

-

The memp_fclose function closes the source file indicated by the -DB_MPOOLFILE structure. Calling memp_fclose does not imply -a call to memp_fsync, i.e. no pages are written to the source -file as as a result of calling memp_fclose. -

In addition, if the file argument to memp_fopen was NULL, -any underlying files created for this DB_MPOOLFILE will be removed. -

Once memp_fclose has been called, regardless of its return, the -DB_MPOOLFILE handle may not be accessed again. -

The memp_fclose function returns a non-zero error value on failure and 0 on success. -

Errors

-

The memp_fclose 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 memp_fclose function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_fget.html b/bdb/docs/api_c/memp_fget.html deleted file mode 100644 index 84b39e53ee1..00000000000 --- a/bdb/docs/api_c/memp_fget.html +++ /dev/null @@ -1,98 +0,0 @@ - - - - - -Berkeley DB: memp_fget - - - - - - - -
-

memp_fget

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_fget(DB_MPOOLFILE *mpf,
-    db_pgno_t *pgnoaddr, u_int32_t flags, void **pagep);
-

-

Description

-

The memp_fget function copies a pointer to the page with the page -number specified by pgnoaddr, from the source file in the -DB_MPOOLFILE, into the memory location referenced by pagep. -If the page does not exist or cannot be retrieved, memp_fget will -fail. -

Page numbers begin at 0, i.e., the first page in the file is page number -0, not page number 1. -

The returned page is size_t type aligned. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_MPOOL_CREATE
If the specified page does not exist, create it. In this case, the -pgin function, if specified, is -called. -

DB_MPOOL_LAST
Return the last page of the source file and copy its page number -to the location referenced by pgnoaddr. -

DB_MPOOL_NEW
Create a new page in the file and copy its page number to the location -referenced by pgnoaddr. In this case, the -pgin function, if specified, is -not called. -
-

The DB_MPOOL_CREATE, DB_MPOOL_LAST and -DB_MPOOL_NEW flags are mutually exclusive. -

Created pages have all their bytes set to 0, unless otherwise specified -when the file was opened. -

All pages returned by memp_fget will be retained (i.e. -pinned), in the pool until a subsequent call to -memp_fput. -

The memp_fget function returns a non-zero error value on failure and 0 on success. -

Errors

-

The memp_fget function may fail and return a non-zero error for the following conditions: -

-

EAGAIN
The page reference count has overflowed. (This should never happen unless -there's a bug in the application.) -
-

-

EINVAL
An invalid flag value or parameter was specified. -

The DB_MPOOL_NEW flag was set and the source file was not opened for writing. -

More than one of DB_MPOOL_CREATE, DB_MPOOL_LAST and DB_MPOOL_NEW was set. -

-

-

EIO
The requested page does not exist and DB_MPOOL_CREATE was not set. -
-

-

ENOMEM
The cache is full and no more pages will fit in the pool. -
-

The memp_fget 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 memp_fget function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_fopen.html b/bdb/docs/api_c/memp_fopen.html deleted file mode 100644 index ea0250246cb..00000000000 --- a/bdb/docs/api_c/memp_fopen.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - -Berkeley DB: memp_fopen - - - - - - - -
-

memp_fopen

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_fopen(DB_ENV *env, char *file, u_int32_t flags,
-    int mode, size_t pagesize, DB_MPOOL_FINFO *finfop,
-    DB_MPOOLFILE **mpf);
-

-

Description

-

The memp_fopen function opens a file in the pool specified by the -DB_ENV env, copying the DB_MPOOLFILE pointer -representing it into the memory location referenced by mpf. -

The file argument is the name of the file to be opened. -If file is NULL, a private file is created that cannot be -shared with any other process (although it may be shared with -other threads). -

The flags and mode arguments specify how files will be opened -and/or created if they do not already exist. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_CREATE
Create any underlying files, as necessary. If the files do not already -exist and the DB_CREATE flag is not specified, the call will fail. -

DB_NOMMAP
Always copy this file into the local cache instead of potentially mapping -it into process memory (see the description of the -DBENV->set_mp_mmapsize function for further information). -

DB_RDONLY
Open any underlying files for reading only. Any attempt to write the file -using the pool functions will fail, regardless of the actual permissions -of the file. -
-

On UNIX systems, or in IEEE/ANSI Std 1003.1 (POSIX) environments, all files created by function memp_fopen -are created with mode mode (as described in chmod(2)) and -modified by the process' umask value at the time of creation (see -umask(2)). The group ownership of created files is based on -the system and directory defaults, and is not further specified by Berkeley DB. -If mode is 0, files are created readable and writeable by both -owner and group. On Windows systems, the mode argument is ignored. -

The pagesize argument is the size, in bytes, of the unit of transfer -between the application and the pool, although it is not necessarily the -unit of transfer between the pool and the source file. -

Files opened in the pool may be further configured based on the -finfop argument to memp_fopen (which is a pointer to a -structure of type DB_MPOOL_FINFO). No references to the finfop -structure are maintained by Berkeley DB, so it may be discarded when the -memp_fopen function returns. In order to ensure compatibility -with future releases of Berkeley DB, all fields of the DB_MPOOL_FINFO structure -that are not explicitly set should be initialized to 0 before the first -time the structure is used. Do this by declaring the structure external -or static, or by calling the C library routine bzero(3) or -memset(3). -

The fields of the DB_MPOOL_FINFO structure used by memp_fopen are -described below. If finfop is NULL or any of its fields are -set to their default value, defaults appropriate for the system are used. -

-

int ftype;
The ftype field should be the same as a ftype argument -previously specified to the memp_register function, unless no -input or output processing of the file's pages are necessary, in which -case it should be 0. (See the description of the memp_register -function for more information.) -

DBT *pgcookie;
The pgcookie field contains the byte string that is passed to the -pgin and pgout functions for this file, if any. If no -pgin or pgout functions are specified, the -pgcookie field should be NULL. (See the description of the -memp_register function for more information.) -

u_int8_t *fileid;
The fileid field is a unique identifier for the file. If the -fileid field is non-NULL, it must reference a DB_FILE_ID_LEN -length array of bytes that will be used to uniquely identify the file. -

The mpool functions must be able to uniquely identify files in order that -multiple processes wanting to share a file will correctly identify it in -the pool. -

On most UNIX/POSIX systems, the fileid field will not need to be -set and the mpool functions will simply use the file's device and inode -numbers for this purpose. On Windows systems, the mpool functions use -the values returned by GetFileInformationByHandle() by default -- these -values are known to be constant between processes and over reboot in the -case of NTFS (where they are the NTFS MFT indexes). -

On other filesystems, (e.g., FAT or NFS) these default values are not -necessarily unique between processes or across system reboots. -Applications wanting to maintain a shared memory buffer pool -between processes or across system reboots, where the pool contains pages -from files stored on such filesystems, must specify a unique file -identifier to the memp_fopen call and each process opening or -registering the file must provide the same unique identifier. -

This should not be necessary for most applications. Specifically, it is -not necessary if the memory pool is not shared between processes and is -re-instantiated after each system reboot, or the application is using the -Berkeley DB access methods instead of calling the pool functions explicitly, or -the files in the memory pool are stored on filesystems where the default -values as described above are invariant between process and across system -reboots. -

int32_t lsn_offset;
The lsn_offset field is the zero-based byte offset in the page of -the page's log sequence number (LSN), or -1 if no LSN offset is specified. -(See the description of the memp_sync function for more -information.) -

u_int32_t clear_len;
The clear_len field is the number of initial bytes in a page -that should be set to zero when the page is created as a result of the -DB_MPOOL_CREATE or DB_MPOOL_NEW flags being specified to memp_fget. -If finfop is NULL or clear_len is 0, the entire page is -cleared. -
-

The memp_fopen function returns a non-zero error value on failure and 0 on success. -

Errors

-

The memp_fopen function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -

The file has already been entered into the pool, and the pagesize -value is not the same as when the file was entered into the pool, or the -length of the file is not zero or a multiple of the pagesize. -

The DB_RDONLY flag was specified for an in-memory pool. -

-

-

ENOMEM
The maximum number of open files has been reached. -
-

The memp_fopen 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 memp_fopen function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_fput.html b/bdb/docs/api_c/memp_fput.html deleted file mode 100644 index ce382b4d034..00000000000 --- a/bdb/docs/api_c/memp_fput.html +++ /dev/null @@ -1,79 +0,0 @@ - - - - - -Berkeley DB: memp_fput - - - - - - - -
-

memp_fput

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_fput(DB_MPOOLFILE *mpf, void *pgaddr, u_int32_t flags);
-

-

Description

-

The memp_fput function indicates that the page referenced by -pgaddr can be evicted from the pool. The pgaddr -argument must be an address previously returned by memp_fget. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_MPOOL_CLEAN
Clear any previously set modification information (i.e., don't bother -writing the page back to the source file). -

DB_MPOOL_DIRTY
The page has been modified and must be written to the source file -before being evicted from the pool. -

DB_MPOOL_DISCARD
The page is unlikely to be useful in the near future, -and should be discarded before other pages in the pool. -
-

The DB_MPOOL_CLEAN and DB_MPOOL_DIRTY flags are -mutually exclusive. -

The memp_fput function returns a non-zero error value on failure and 0 on success. -

Errors

-

The memp_fput function may fail and return a non-zero error for the following conditions: -

-

EACCES
The DB_MPOOL_DIRTY flag was set and the source file was not opened for -writing. -
-

-

EINVAL
An invalid flag value or parameter was specified. -

The pgaddr parameter does not reference a page returned by -memp_fget. -

More than one of DB_MPOOL_CLEAN and DB_MPOOL_DIRTY flags was set. -

-

The memp_fput 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 memp_fput function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_fset.html b/bdb/docs/api_c/memp_fset.html deleted file mode 100644 index 73acd322c4e..00000000000 --- a/bdb/docs/api_c/memp_fset.html +++ /dev/null @@ -1,72 +0,0 @@ - - - - - -Berkeley DB: memp_fset - - - - - - - -
-

memp_fset

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_fset(DB_MPOOLFILE *mpf, void *pgaddr, u_int32_t flags);
-

-

Description

-

The memp_fset function sets the flags associated with the page referenced -by pgaddr without unpinning it from the pool. The pgaddr -argument must be an address previously returned by memp_fget. -

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more -of the following values. -

-

DB_MPOOL_CLEAN
Clear any previously set modification information (i.e., don't bother -writing the page back to the source file). -

DB_MPOOL_DIRTY
The page has been modified and must be written to the source file -before being evicted from the pool. -

DB_MPOOL_DISCARD
The page is unlikely to be useful in the near future, -and should be discarded before other pages in the pool. -
-

The DB_MPOOL_CLEAN and DB_MPOOL_DIRTY flags are -mutually exclusive. -

The memp_fset function returns a non-zero error value on failure and 0 on success. -

Errors

-

The memp_fset function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The memp_fset 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 memp_fset function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_fsync.html b/bdb/docs/api_c/memp_fsync.html deleted file mode 100644 index ad429ccf390..00000000000 --- a/bdb/docs/api_c/memp_fsync.html +++ /dev/null @@ -1,59 +0,0 @@ - - - - - -Berkeley DB: memp_fsync - - - - - - - -
-

memp_fsync

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_fsync(DB_MPOOLFILE *mpf);
-

-

Description

-

The memp_fsync function writes all pages associated with the -DB_MPOOLFILE, that were marked as modified using memp_fput -or memp_fset, back to the source file. If any of the modified -pages are also pinned (i.e., currently referenced by this or -another process) memp_fsync will ignore them. -

The memp_fsync function returns a non-zero error value on failure, 0 on success, and returns DB_INCOMPLETE if there were pages which were -modified but which memp_fsync was unable to write immediately. -

Errors

-

The memp_fsync 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 memp_fsync function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_register.html b/bdb/docs/api_c/memp_register.html deleted file mode 100644 index 7c50a89ed2b..00000000000 --- a/bdb/docs/api_c/memp_register.html +++ /dev/null @@ -1,93 +0,0 @@ - - - - - -Berkeley DB: memp_register - - - - - - - -
-

memp_register

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_register(DB_ENV *env, int ftype,
-    int (*pgin_fcn)(DB_ENV *, db_pgno_t pgno, void *pgaddr, DBT *pgcookie),
-    int (*pgout_fcn)(DB_ENV *, db_pgno_t pgno, void *pgaddr, DBT *pgcookie));
-

-

Description

-

The memp_register function registers page-in and page-out -functions for files of type ftype in the specified pool. -

If the pgin_fcn function is non-NULL, it is called each time -a page is read into the memory pool from a file of type ftype, or -a page is created for a file of type ftype (see the -DB_MPOOL_CREATE flag for the memp_fget function). -

If the pgout_fcn function is non-NULL, it is called each time -a page is written to a file of type ftype. -

Both the pgin_fcn and pgout_fcn functions are called with -a reference to the current environment, the page number, a pointer to the -page being read or written, and any argument pgcookie that was -specified to the memp_fopen function when the file was opened. -The pgin_fcn and pgout_fcn functions should return 0 on -success, and an applicable non-zero errno value on failure, in -which case the shared memory pool interface routine (and, by extension, -any Berkeley DB library function) calling it will also fail, returning that -errno value. -

The purpose of the memp_register function is to support processing -when pages are entered into, or flushed from, the pool. A file type must -be specified to make it possible for unrelated threads or processes, that -are sharing a pool, to evict each other's pages from the pool. -Applications should call memp_register, during initialization, -for each type of file requiring input or output processing that will be -sharing the underlying pool. (No registry is necessary for the standard -Berkeley DB access method types, as DB->open registers them -separately.) -

If a thread or process does not call memp_register for a file -type, it is impossible for it to evict pages for any file requiring input -or output processing from the pool. For this reason, -memp_register should always be called by each application sharing -a pool for each type of file included in the pool, regardless of whether -or not the application itself uses files of that type. -

There are no standard values for ftype, pgin_fcn, -pgout_fcn and pgcookie, except that the ftype -value for a file must be a non-zero positive number, as negative numbers -are reserved for internal use by the Berkeley DB library. For this reason, -applications sharing a pool must coordinate their values amongst -themselves. -

The memp_register function returns a non-zero error value on failure and 0 on success. -

Errors

-

The memp_register 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 memp_register function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_stat.html b/bdb/docs/api_c/memp_stat.html deleted file mode 100644 index 8e9d136a90b..00000000000 --- a/bdb/docs/api_c/memp_stat.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - -Berkeley DB: memp_stat - - - - - - - -
-

memp_stat

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_stat(DB_ENV *env, DB_MPOOL_STAT **gsp,
-    DB_MPOOL_FSTAT *(*fsp)[], void *(*db_malloc)(size_t));
-

-

Description

-

The memp_stat function method creates statistical structures and copies -pointers to them into user-specified memory locations. The statistics -include the number of files participating in the pool, the active pages -in the pool, and information as to how effective the cache has been. -

Statistical structures are created in allocated memory. If db_malloc is non-NULL, it -is called to allocate the memory, otherwise, the library function -malloc(3) is used. The function db_malloc must match -the calling conventions of the malloc(3) library routine. -Regardless, the caller is responsible for deallocating the returned -memory. To deallocate returned memory, free the returned memory -reference, references inside the returned memory do not need to be -individually freed. -

If gsp is non-NULL, the global statistics for the memory pool -mp are copied into the memory location it references. The -global statistics are stored in a structure of type DB_MPOOL_STAT. -

The following DB_MPOOL_STAT fields will be filled in: -

-
size_t st_gbytes;
Gigabytes of cache (total cache size is st_gbytes + st_bytes) -
size_t st_bytes;
Bytes of cache (total cache size is st_gbytes + st_bytes) -
u_int32_t st_ncache;
Number of caches. -
u_int32_t st_regsize;
Individual cache size. -
u_int32_t st_cache_hit;
Requested pages found in the cache. -
u_int32_t st_cache_miss;
Requested pages not found in the cache. -
u_int32_t st_map;
Requested pages mapped into the process' address space (there is no -available information as to whether or not this request caused disk I/O, -although examining the application page fault rate may be helpful). -
u_int32_t st_page_create;
Pages created in the cache. -
u_int32_t st_page_in;
Pages read into the cache. -
u_int32_t st_page_out;
Pages written from the cache to the backing file. -
u_int32_t st_ro_evict;
Clean pages forced from the cache. -
u_int32_t st_rw_evict;
Dirty pages forced from the cache. -
u_int32_t st_hash_buckets;
Number of hash buckets in buffer hash table. -
u_int32_t st_hash_searches;
Total number of buffer hash table lookups. -
u_int32_t st_hash_longest;
The longest chain ever encountered in buffer hash table lookups. -
u_int32_t st_hash_examined;
Total number of hash elements traversed during hash table lookups. -
u_int32_t st_page_clean;
Clean pages currently in the cache. -
u_int32_t st_page_dirty;
Dirty pages currently in the cache. -
u_int32_t st_page_trickle;
Dirty pages written using the memp_trickle interface. -
u_int32_t st_region_wait;
The number of times that a thread of control was forced to wait before -obtaining the region lock. -
u_int32_t st_region_nowait;
The number of times that a thread of control was able to obtain -the region lock without waiting. -
-

If fsp is non-NULL, a pointer to a NULL-terminated variable -length array of statistics for individual files, in the memory pool mp, -is copied into the memory location it references. If no individual files -currently exist in the memory pool, fsp will be set to NULL. -

The per-file statistics are stored in structures of type DB_MPOOL_FSTAT. -The following DB_MPOOL_FSTAT fields will be filled in for each file in -the pool, i.e., each element of the array: -

-
char *file_name;
The name of the file. -
size_t st_pagesize;
Page size in bytes. -
u_int32_t st_cache_hit;
Requested pages found in the cache. -
u_int32_t st_cache_miss;
Requested pages not found in the cache. -
u_int32_t st_map;
Requested pages mapped into the process' address space. -
u_int32_t st_page_create;
Pages created in the cache. -
u_int32_t st_page_in;
Pages read into the cache. -
u_int32_t st_page_out;
Pages written from the cache to the backing file. -
-

The memp_stat function returns a non-zero error value on failure and 0 on success. -

Errors

-

The memp_stat function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The memp_stat 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 memp_stat function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_sync.html b/bdb/docs/api_c/memp_sync.html deleted file mode 100644 index fc693d47eff..00000000000 --- a/bdb/docs/api_c/memp_sync.html +++ /dev/null @@ -1,83 +0,0 @@ - - - - - -Berkeley DB: memp_sync - - - - - - - -
-

memp_sync

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_sync(DB_ENV *env, DB_LSN *lsn);
-

-

Description

-

The memp_sync function ensures that any modified pages in the pool with -log sequence numbers less than the lsn argument are written to -disk. If lsn is NULL all modified pages in the pool are -flushed. -

The primary purpose of the memp_sync function is to enable a -transaction manager to ensure, as part of a checkpoint, that all pages -modified by a certain time have been written to disk. Pages in the pool -that cannot be written back to disk immediately (e.g., that are currently -pinned) are written to disk as soon as it is possible to do so. The -expected behavior of the Berkeley DB or other transaction subsystem is to call -the memp_sync function and then, if the return indicates that some -pages could not be written immediately, to wait briefly and retry again -with the same log sequence number until the memp_sync function -returns that all pages have been written. -

To support the memp_sync functionality, it is necessary that the -pool functions know the location of the log sequence number on the page -for each file type. This location should be specified when the file is -opened using the memp_fopen function. It is not required that -the log sequence number be aligned on the page in any way. -

The memp_sync function returns a non-zero error value on failure, 0 on success, and returns DB_INCOMPLETE if there were pages which need to be -written but which memp_sync was unable to write immediately. -In addition, if memp_sync returns success, the value of -lsn will be overwritten with the largest log sequence number -from any page which was written by memp_sync to satisfy this -request. -

Errors

-

The memp_sync function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -

The memp_sync function was called without logging having been -initialized in the environment. -

-

The memp_sync 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 memp_sync function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/memp_trickle.html b/bdb/docs/api_c/memp_trickle.html deleted file mode 100644 index d7cfd723020..00000000000 --- a/bdb/docs/api_c/memp_trickle.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - -Berkeley DB: memp_trickle - - - - - - - -
-

memp_trickle

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-memp_trickle(DB_ENV *env, int pct, int *nwrotep);
-

-

Description

-

The memp_trickle function ensures that at least pct percent of -the pages in the shared memory pool are clean by writing dirty pages to -their backing files. -If the nwrotep argument is non-NULL, the number of pages that -were written to reach the correct percentage is returned in the memory -location it references. -

The purpose of the memp_trickle function is to enable a memory -pool manager to ensure that a page is always available for reading in new -information without having to wait for a write. -

The memp_trickle function returns a non-zero error value on failure and 0 on success. -

Errors

-

The memp_trickle function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The memp_trickle 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 memp_trickle function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_mp_mmapsize, -memp_fclose, -memp_fget, -memp_fopen, -memp_fput, -memp_fset, -memp_fsync, -memp_register, -memp_stat, -memp_sync -and -memp_trickle. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/pindex.src b/bdb/docs/api_c/pindex.src deleted file mode 100644 index 1818c50a6d1..00000000000 --- a/bdb/docs/api_c/pindex.src +++ /dev/null @@ -1,301 +0,0 @@ -__APIREL__/api_c/db_create.html#2 @db_create -__APIREL__/api_c/db_create.html#DB_XA_CREATE db_create@DB_XA_CREATE -__APIREL__/api_c/db_err.html#2 @DBENV-__GT__err -__APIREL__/api_c/db_lsn.html#2 @DB_LSN -__APIREL__/api_c/db_set_errfile.html#2 @DB-__GT__set_errfile -__APIREL__/api_c/db_set_malloc.html#2 @DB-__GT__set_malloc -__APIREL__/api_c/db_set_paniccall.html#2 @DB-__GT__set_paniccall -__APIREL__/api_c/db_set_realloc.html#2 @DB-__GT__set_realloc -__APIREL__/api_c/dbm.html#2 @dbm/ndbm -__APIREL__/api_c/dbt.html#2 @key/data pairs -__APIREL__/api_c/dbt.html#data DBT@data -__APIREL__/api_c/dbt.html#size DBT@size -__APIREL__/api_c/dbt.html#ulen DBT@ulen -__APIREL__/api_c/dbt.html#dlen DBT@dlen -__APIREL__/api_c/dbt.html#doff DBT@doff -__APIREL__/api_c/dbt.html#DB_DBT_MALLOC DBT@DB_DBT_MALLOC -__APIREL__/api_c/dbt.html#DB_DBT_REALLOC DBT@DB_DBT_REALLOC -__APIREL__/api_c/dbt.html#DB_DBT_USERMEM DBT@DB_DBT_USERMEM -__APIREL__/api_c/dbt.html#DB_DBT_PARTIAL DBT@DB_DBT_PARTIAL -__APIREL__/api_c/dbt.html#3 retrieved key/data @permanence -__APIREL__/api_c/dbt.html#4 retrieved @key/data permanence -__APIREL__/api_c/dbt.html#5 data @alignment -__APIREL__/api_c/dbt.html#6 logical @record number format -__APIREL__/api_c/env_create.html#2 @db_env_create -__APIREL__/api_c/env_create.html#DB_CLIENT db_env_create@DB_CLIENT -__APIREL__/api_c/env_set_errfile.html#2 @DBENV-__GT__set_errfile -__APIREL__/api_c/env_set_paniccall.html#2 @DBENV-__GT__set_paniccall -__APIREL__/api_c/hsearch.html#2 @hsearch -__APIREL__/api_c/set_func_close.html#2 @db_env_set_func_close -__APIREL__/api_c/set_func_dirfree.html#2 @db_env_set_func_dirfree -__APIREL__/api_c/set_func_dirlist.html#2 @db_env_set_func_dirlist -__APIREL__/api_c/set_func_exists.html#2 @db_env_set_func_exists -__APIREL__/api_c/set_func_free.html#2 @db_env_set_func_free -__APIREL__/api_c/set_func_fsync.html#2 @db_env_set_func_fsync -__APIREL__/api_c/set_func_ioinfo.html#2 @db_env_set_func_ioinfo -__APIREL__/api_c/set_func_malloc.html#2 @db_env_set_func_malloc -__APIREL__/api_c/set_func_map.html#2 @db_env_set_func_map -__APIREL__/api_c/set_func_open.html#2 @db_env_set_func_open -__APIREL__/api_c/set_func_read.html#2 @db_env_set_func_read -__APIREL__/api_c/set_func_realloc.html#2 @db_env_set_func_realloc -__APIREL__/api_c/set_func_rename.html#2 @db_env_set_func_rename -__APIREL__/api_c/set_func_seek.html#2 @db_env_set_func_seek -__APIREL__/api_c/set_func_sleep.html#2 @db_env_set_func_sleep -__APIREL__/api_c/set_func_unlink.html#2 @db_env_set_func_unlink -__APIREL__/api_c/set_func_unmap.html#2 @db_env_set_func_unmap -__APIREL__/api_c/set_func_write.html#2 @db_env_set_func_write -__APIREL__/api_c/set_func_yield.html#2 @db_env_set_func_yield -__APIREL__/api_c/db_close.html#2 @DB-__GT__close -__APIREL__/api_c/db_close.html#DB_NOSYNC DB-__GT__close@DB_NOSYNC -__APIREL__/api_c/db_close.html#3 DB-__GT__close @DB_INCOMPLETE -__APIREL__/api_c/db_cursor.html#2 @DB-__GT__cursor -__APIREL__/api_c/db_cursor.html#DB_WRITECURSOR DB-__GT__cursor@DB_WRITECURSOR -__APIREL__/api_c/db_del.html#2 @DB-__GT__del -__APIREL__/api_c/db_fd.html#2 @DB-__GT__fd -__APIREL__/api_c/db_get.html#2 @DB-__GT__get -__APIREL__/api_c/db_get.html#DB_CONSUME DB-__GT__get@DB_CONSUME -__APIREL__/api_c/db_get.html#DB_CONSUME_WAIT DB-__GT__get@DB_CONSUME_WAIT -__APIREL__/api_c/db_get.html#DB_GET_BOTH DB-__GT__get@DB_GET_BOTH -__APIREL__/api_c/db_get.html#DB_SET_RECNO DB-__GT__get@DB_SET_RECNO -__APIREL__/api_c/db_get.html#DB_RMW DB-__GT__get@DB_RMW -__APIREL__/api_c/db_get_byteswapped.html#2 @DB-__GT__get_byteswapped -__APIREL__/api_c/db_get_type.html#2 @DB-__GT__get_type -__APIREL__/api_c/db_join.html#2 @DB-__GT__join -__APIREL__/api_c/db_join.html#DB_JOIN_NOSORT DB-__GT__join@DB_JOIN_NOSORT -__APIREL__/api_c/db_join.html#DB_JOIN_ITEM DB-__GT__join@DB_JOIN_ITEM -__APIREL__/api_c/db_join.html#DB_RMW DB-__GT__join@DB_RMW -__APIREL__/api_c/db_key_range.html#2 @DB-__GT__key_range -__APIREL__/api_c/db_open.html#2 @DB-__GT__open -__APIREL__/api_c/db_open.html#DB_CREATE DB-__GT__open@DB_CREATE -__APIREL__/api_c/db_open.html#DB_EXCL DB-__GT__open@DB_EXCL -__APIREL__/api_c/db_open.html#DB_NOMMAP DB-__GT__open@DB_NOMMAP -__APIREL__/api_c/db_open.html#DB_RDONLY DB-__GT__open@DB_RDONLY -__APIREL__/api_c/db_open.html#DB_THREAD DB-__GT__open@DB_THREAD -__APIREL__/api_c/db_open.html#DB_TRUNCATE DB-__GT__open@DB_TRUNCATE -__APIREL__/api_c/db_open.html#DB_OLD_VERSION DB-__GT__open@DB_OLD_VERSION -__APIREL__/api_c/db_put.html#2 @DB-__GT__put -__APIREL__/api_c/db_put.html#DB_APPEND DB-__GT__put@DB_APPEND -__APIREL__/api_c/db_put.html#DB_NODUPDATA DB-__GT__put@DB_NODUPDATA -__APIREL__/api_c/db_put.html#DB_NOOVERWRITE DB-__GT__put@DB_NOOVERWRITE -__APIREL__/api_c/db_remove.html#2 @DB-__GT__remove -__APIREL__/api_c/db_rename.html#2 @DB-__GT__rename -__APIREL__/api_c/db_set_append_recno.html#2 @DB-__GT__set_append_recno -__APIREL__/api_c/db_set_bt_compare.html#2 @DB-__GT__set_bt_compare -__APIREL__/api_c/db_set_bt_minkey.html#2 @DB-__GT__set_bt_minkey -__APIREL__/api_c/db_set_bt_prefix.html#2 @DB-__GT__set_bt_prefix -__APIREL__/api_c/db_set_cachesize.html#2 @DB-__GT__set_cachesize -__APIREL__/api_c/db_set_dup_compare.html#2 @DB-__GT__set_dup_compare -__APIREL__/api_c/db_set_errcall.html#2 @DB-__GT__set_errcall -__APIREL__/api_c/db_set_errpfx.html#2 @DB-__GT__set_errpfx -__APIREL__/api_c/db_set_feedback.html#2 @DB-__GT__set_feedback -__APIREL__/api_c/db_set_feedback.html#DB_UPGRADE DB-__GT__set_feedback@DB_UPGRADE -__APIREL__/api_c/db_set_feedback.html#DB_VERIFY DB-__GT__set_feedback@DB_VERIFY -__APIREL__/api_c/db_set_flags.html#2 @DB-__GT__set_flags -__APIREL__/api_c/db_set_flags.html#DB_DUP DB-__GT__set_flags@DB_DUP -__APIREL__/api_c/db_set_flags.html#DB_DUPSORT DB-__GT__set_flags@DB_DUPSORT -__APIREL__/api_c/db_set_flags.html#DB_RECNUM DB-__GT__set_flags@DB_RECNUM -__APIREL__/api_c/db_set_flags.html#DB_REVSPLITOFF DB-__GT__set_flags@DB_REVSPLITOFF -__APIREL__/api_c/db_set_flags.html#DB_DUP DB-__GT__set_flags@DB_DUP -__APIREL__/api_c/db_set_flags.html#DB_DUPSORT DB-__GT__set_flags@DB_DUPSORT -__APIREL__/api_c/db_set_flags.html#DB_RENUMBER DB-__GT__set_flags@DB_RENUMBER -__APIREL__/api_c/db_set_flags.html#DB_SNAPSHOT DB-__GT__set_flags@DB_SNAPSHOT -__APIREL__/api_c/db_set_h_ffactor.html#2 @DB-__GT__set_h_ffactor -__APIREL__/api_c/db_set_h_hash.html#2 @DB-__GT__set_h_hash -__APIREL__/api_c/db_set_h_nelem.html#2 @DB-__GT__set_h_nelem -__APIREL__/api_c/db_set_lorder.html#2 @DB-__GT__set_lorder -__APIREL__/api_c/db_set_pagesize.html#2 @DB-__GT__set_pagesize -__APIREL__/api_c/db_set_q_extentsize.html#2 @DB-__GT__set_q_extentsize -__APIREL__/api_c/db_set_re_delim.html#2 @DB-__GT__set_re_delim -__APIREL__/api_c/db_set_re_len.html#2 @DB-__GT__set_re_len -__APIREL__/api_c/db_set_re_pad.html#2 @DB-__GT__set_re_pad -__APIREL__/api_c/db_set_re_source.html#2 @DB-__GT__set_re_source -__APIREL__/api_c/db_stat.html#2 @DB-__GT__stat -__APIREL__/api_c/db_stat.html#DB_CACHED_COUNTS DB-__GT__stat@DB_CACHED_COUNTS -__APIREL__/api_c/db_stat.html#DB_RECORDCOUNT DB-__GT__stat@DB_RECORDCOUNT -__APIREL__/api_c/db_sync.html#2 @DB-__GT__sync -__APIREL__/api_c/db_upgrade.html#2 @DB-__GT__upgrade -__APIREL__/api_c/db_upgrade.html#DB_DUPSORT DB-__GT__upgrade@DB_DUPSORT -__APIREL__/api_c/db_upgrade.html#DB_OLD_VERSION DB-__GT__upgrade@DB_OLD_VERSION -__APIREL__/api_c/db_verify.html#2 @DB-__GT__verify -__APIREL__/api_c/db_verify.html#DB_SALVAGE DB-__GT__verify@DB_SALVAGE -__APIREL__/api_c/db_verify.html#DB_AGGRESSIVE DB-__GT__verify@DB_AGGRESSIVE -__APIREL__/api_c/db_verify.html#DB_NOORDERCHK DB-__GT__verify@DB_NOORDERCHK -__APIREL__/api_c/db_verify.html#DB_ORDERCHKONLY DB-__GT__verify@DB_ORDERCHKONLY -__APIREL__/api_c/dbc_close.html#2 @DBcursor-__GT__c_close -__APIREL__/api_c/dbc_count.html#2 @DBcursor-__GT__c_count -__APIREL__/api_c/dbc_del.html#2 @DBcursor-__GT__c_del -__APIREL__/api_c/dbc_dup.html#2 @DBcursor-__GT__c_dup -__APIREL__/api_c/dbc_dup.html#DB_POSITION DBcursor-__GT__c_dup@DB_POSITION -__APIREL__/api_c/dbc_get.html#2 @DBcursor-__GT__c_get -__APIREL__/api_c/dbc_get.html#DB_CURRENT DBcursor-__GT__c_get@DB_CURRENT -__APIREL__/api_c/dbc_get.html#DB_FIRST DBcursor-__GT__c_get@DB_FIRST -__APIREL__/api_c/dbc_get.html#DB_LAST DBcursor-__GT__c_get@DB_LAST -__APIREL__/api_c/dbc_get.html#DB_GET_BOTH DBcursor-__GT__c_get@DB_GET_BOTH -__APIREL__/api_c/dbc_get.html#DB_GET_RECNO DBcursor-__GT__c_get@DB_GET_RECNO -__APIREL__/api_c/dbc_get.html#DB_JOIN_ITEM DBcursor-__GT__c_get@DB_JOIN_ITEM -__APIREL__/api_c/dbc_get.html#DB_NEXT DBcursor-__GT__c_get@DB_NEXT -__APIREL__/api_c/dbc_get.html#DB_PREV DBcursor-__GT__c_get@DB_PREV -__APIREL__/api_c/dbc_get.html#DB_NEXT_DUP DBcursor-__GT__c_get@DB_NEXT_DUP -__APIREL__/api_c/dbc_get.html#DB_NEXT_NODUP DBcursor-__GT__c_get@DB_NEXT_NODUP -__APIREL__/api_c/dbc_get.html#DB_PREV_NODUP DBcursor-__GT__c_get@DB_PREV_NODUP -__APIREL__/api_c/dbc_get.html#DB_SET DBcursor-__GT__c_get@DB_SET -__APIREL__/api_c/dbc_get.html#DB_SET_RANGE DBcursor-__GT__c_get@DB_SET_RANGE -__APIREL__/api_c/dbc_get.html#DB_SET_RECNO DBcursor-__GT__c_get@DB_SET_RECNO -__APIREL__/api_c/dbc_get.html#DB_RMW DBcursor-__GT__c_get@DB_RMW -__APIREL__/api_c/dbc_put.html#2 @DBcursor-__GT__c_put -__APIREL__/api_c/dbc_put.html#DB_AFTER DBcursor-__GT__c_put@DB_AFTER -__APIREL__/api_c/dbc_put.html#DB_BEFORE DBcursor-__GT__c_put@DB_BEFORE -__APIREL__/api_c/dbc_put.html#DB_CURRENT DBcursor-__GT__c_put@DB_CURRENT -__APIREL__/api_c/dbc_put.html#DB_KEYFIRST DBcursor-__GT__c_put@DB_KEYFIRST -__APIREL__/api_c/dbc_put.html#DB_KEYLAST DBcursor-__GT__c_put@DB_KEYLAST -__APIREL__/api_c/dbc_put.html#DB_NODUPDATA DBcursor-__GT__c_put@DB_NODUPDATA -__APIREL__/api_c/env_close.html#2 @DBENV-__GT__close -__APIREL__/api_c/env_open.html#2 @DBENV-__GT__open -__APIREL__/api_c/env_open.html#DB_JOINENV DBENV-__GT__open@DB_JOINENV -__APIREL__/api_c/env_open.html#DB_INIT_CDB DBENV-__GT__open@DB_INIT_CDB -__APIREL__/api_c/env_open.html#DB_INIT_LOCK DBENV-__GT__open@DB_INIT_LOCK -__APIREL__/api_c/env_open.html#DB_INIT_LOG DBENV-__GT__open@DB_INIT_LOG -__APIREL__/api_c/env_open.html#DB_INIT_MPOOL DBENV-__GT__open@DB_INIT_MPOOL -__APIREL__/api_c/env_open.html#DB_INIT_TXN DBENV-__GT__open@DB_INIT_TXN -__APIREL__/api_c/env_open.html#DB_RECOVER DBENV-__GT__open@DB_RECOVER -__APIREL__/api_c/env_open.html#DB_RECOVER_FATAL DBENV-__GT__open@DB_RECOVER_FATAL -__APIREL__/api_c/env_open.html#DB_USE_ENVIRON DBENV-__GT__open@DB_USE_ENVIRON -__APIREL__/api_c/env_open.html#DB_USE_ENVIRON_ROOT DBENV-__GT__open@DB_USE_ENVIRON_ROOT -__APIREL__/api_c/env_open.html#DB_CREATE DBENV-__GT__open@DB_CREATE -__APIREL__/api_c/env_open.html#DB_LOCKDOWN DBENV-__GT__open@DB_LOCKDOWN -__APIREL__/api_c/env_open.html#DB_PRIVATE DBENV-__GT__open@DB_PRIVATE -__APIREL__/api_c/env_open.html#DB_SYSTEM_MEM DBENV-__GT__open@DB_SYSTEM_MEM -__APIREL__/api_c/env_open.html#DB_THREAD DBENV-__GT__open@DB_THREAD -__APIREL__/api_c/env_remove.html#2 @DBENV-__GT__remove -__APIREL__/api_c/env_remove.html#DB_FORCE DBENV-__GT__remove@DB_FORCE -__APIREL__/api_c/env_remove.html#DB_USE_ENVIRON DBENV-__GT__remove@DB_USE_ENVIRON -__APIREL__/api_c/env_remove.html#DB_USE_ENVIRON_ROOT DBENV-__GT__remove@DB_USE_ENVIRON_ROOT -__APIREL__/api_c/env_set_cachesize.html#2 @DBENV-__GT__set_cachesize -__APIREL__/api_c/env_set_data_dir.html#2 @DBENV-__GT__set_data_dir -__APIREL__/api_c/env_set_errcall.html#2 @DBENV-__GT__set_errcall -__APIREL__/api_c/env_set_errpfx.html#2 @DBENV-__GT__set_errpfx -__APIREL__/api_c/env_set_feedback.html#2 @DBENV-__GT__set_feedback -__APIREL__/api_c/env_set_feedback.html#DB_RECOVER DBENV-__GT__set_feedback@DB_RECOVER -__APIREL__/api_c/env_set_flags.html#2 @DBENV-__GT__set_flags -__APIREL__/api_c/env_set_flags.html#DB_CDB_ALLDB DBENV-__GT__set_flags@DB_CDB_ALLDB -__APIREL__/api_c/env_set_flags.html#DB_NOMMAP DBENV-__GT__set_flags@DB_NOMMAP -__APIREL__/api_c/env_set_flags.html#DB_TXN_NOSYNC DBENV-__GT__set_flags@DB_TXN_NOSYNC -__APIREL__/api_c/env_set_lg_bsize.html#2 @DBENV-__GT__set_lg_bsize -__APIREL__/api_c/env_set_lg_dir.html#2 @DBENV-__GT__set_lg_dir -__APIREL__/api_c/env_set_lg_max.html#2 @DBENV-__GT__set_lg_max -__APIREL__/api_c/env_set_lk_conflicts.html#2 @DBENV-__GT__set_lk_conflicts -__APIREL__/api_c/env_set_lk_detect.html#2 @DBENV-__GT__set_lk_detect -__APIREL__/api_c/env_set_lk_detect.html#DB_LOCK_DEFAULT DBENV-__GT__set_lk_detect@DB_LOCK_DEFAULT -__APIREL__/api_c/env_set_lk_detect.html#DB_LOCK_OLDEST DBENV-__GT__set_lk_detect@DB_LOCK_OLDEST -__APIREL__/api_c/env_set_lk_detect.html#DB_LOCK_RANDOM DBENV-__GT__set_lk_detect@DB_LOCK_RANDOM -__APIREL__/api_c/env_set_lk_detect.html#DB_LOCK_YOUNGEST DBENV-__GT__set_lk_detect@DB_LOCK_YOUNGEST -__APIREL__/api_c/env_set_lk_max.html#2 @DBENV-__GT__set_lk_max -__APIREL__/api_c/env_set_lk_max_locks.html#2 @DBENV-__GT__set_lk_max_locks -__APIREL__/api_c/env_set_lk_max_lockers.html#2 @DBENV-__GT__set_lk_max_lockers -__APIREL__/api_c/env_set_lk_max_objects.html#2 @DBENV-__GT__set_lk_max_objects -__APIREL__/api_c/env_set_mp_mmapsize.html#2 @DBENV-__GT__set_mp_mmapsize -__APIREL__/api_c/env_set_mutexlocks.html#2 @DBENV-__GT__set_mutexlocks -__APIREL__/api_c/env_set_pageyield.html#2 @db_env_set_pageyield -__APIREL__/api_c/env_set_panicstate.html#2 @db_env_set_panicstate -__APIREL__/api_c/env_set_rec_init.html#2 @DBENV-__GT__set_recovery_init -__APIREL__/api_c/env_set_region_init.html#2 @db_env_set_region_init -__APIREL__/api_c/env_set_server.html#2 @DBENV-__GT__set_server -__APIREL__/api_c/env_set_server.html#DB_NOSERVER DBENV-__GT__set_server@DB_NOSERVER -__APIREL__/api_c/env_set_server.html#DB_NOSERVER_ID DBENV-__GT__set_server@DB_NOSERVER_ID -__APIREL__/api_c/env_set_shm_key.html#2 @DBENV-__GT__set_shm_key -__APIREL__/api_c/env_set_tas_spins.html#2 @db_env_set_tas_spins -__APIREL__/api_c/env_set_tmp_dir.html#2 @DBENV-__GT__set_tmp_dir -__APIREL__/api_c/env_set_tx_max.html#2 @DBENV-__GT__set_tx_max -__APIREL__/api_c/env_set_tx_recover.html#2 @DBENV-__GT__set_tx_recover -__APIREL__/api_c/env_set_tx_recover.html#DB_TXN_BACKWARD_ROLL DBENV-__GT__set_tx_recover@DB_TXN_BACKWARD_ROLL -__APIREL__/api_c/env_set_tx_recover.html#DB_TXN_FORWARD_ROLL DBENV-__GT__set_tx_recover@DB_TXN_FORWARD_ROLL -__APIREL__/api_c/env_set_tx_recover.html#DB_TXN_ABORT DBENV-__GT__set_tx_recover@DB_TXN_ABORT -__APIREL__/api_c/env_set_tx_timestamp.html#2 @DBENV-__GT__set_tx_timestamp -__APIREL__/api_c/env_set_verbose.html#2 @DBENV-__GT__set_verbose -__APIREL__/api_c/env_set_verbose.html#DB_VERB_CHKPOINT DBENV-__GT__set_verbose@DB_VERB_CHKPOINT -__APIREL__/api_c/env_set_verbose.html#DB_VERB_DEADLOCK DBENV-__GT__set_verbose@DB_VERB_DEADLOCK -__APIREL__/api_c/env_set_verbose.html#DB_VERB_RECOVERY DBENV-__GT__set_verbose@DB_VERB_RECOVERY -__APIREL__/api_c/env_set_verbose.html#DB_VERB_WAITSFOR DBENV-__GT__set_verbose@DB_VERB_WAITSFOR -__APIREL__/api_c/env_strerror.html#2 @db_strerror -__APIREL__/api_c/env_version.html#2 @db_version -__APIREL__/api_c/lock_detect.html#2 @lock_detect -__APIREL__/api_c/lock_detect.html#DB_LOCK_CONFLICT lock_detect@DB_LOCK_CONFLICT -__APIREL__/api_c/lock_get.html#2 @lock_get -__APIREL__/api_c/lock_get.html#DB_LOCK_NOWAIT lock_get@DB_LOCK_NOWAIT -__APIREL__/api_c/lock_get.html#DB_LOCK_NOTGRANTED lock_get@DB_LOCK_NOTGRANTED -__APIREL__/api_c/lock_id.html#2 @lock_id -__APIREL__/api_c/lock_put.html#2 @lock_put -__APIREL__/api_c/lock_stat.html#2 @lock_stat -__APIREL__/api_c/lock_vec.html#2 @lock_vec -__APIREL__/api_c/lock_vec.html#DB_LOCK_NOWAIT lock_vec@DB_LOCK_NOWAIT -__APIREL__/api_c/lock_vec.html#op lock_vec@op -__APIREL__/api_c/lock_vec.html#DB_LOCK_GET lock_vec@DB_LOCK_GET -__APIREL__/api_c/lock_vec.html#DB_LOCK_PUT lock_vec@DB_LOCK_PUT -__APIREL__/api_c/lock_vec.html#DB_LOCK_PUT_ALL lock_vec@DB_LOCK_PUT_ALL -__APIREL__/api_c/lock_vec.html#DB_LOCK_PUT_OBJ lock_vec@DB_LOCK_PUT_OBJ -__APIREL__/api_c/lock_vec.html#obj lock_vec@obj -__APIREL__/api_c/lock_vec.html#mode lock_vec@mode -__APIREL__/api_c/lock_vec.html#lock lock_vec@lock -__APIREL__/api_c/lock_vec.html#DB_LOCK_NOTGRANTED lock_vec@DB_LOCK_NOTGRANTED -__APIREL__/api_c/log_archive.html#2 @log_archive -__APIREL__/api_c/log_archive.html#DB_ARCH_ABS log_archive@DB_ARCH_ABS -__APIREL__/api_c/log_archive.html#DB_ARCH_DATA log_archive@DB_ARCH_DATA -__APIREL__/api_c/log_archive.html#DB_ARCH_LOG log_archive@DB_ARCH_LOG -__APIREL__/api_c/log_compare.html#2 @log_compare -__APIREL__/api_c/log_file.html#2 @log_file -__APIREL__/api_c/log_flush.html#2 @log_flush -__APIREL__/api_c/log_get.html#2 @log_get -__APIREL__/api_c/log_get.html#DB_CHECKPOINT log_get@DB_CHECKPOINT -__APIREL__/api_c/log_get.html#DB_FIRST log_get@DB_FIRST -__APIREL__/api_c/log_get.html#DB_LAST log_get@DB_LAST -__APIREL__/api_c/log_get.html#DB_NEXT log_get@DB_NEXT -__APIREL__/api_c/log_get.html#DB_PREV log_get@DB_PREV -__APIREL__/api_c/log_get.html#DB_CURRENT log_get@DB_CURRENT -__APIREL__/api_c/log_get.html#DB_SET log_get@DB_SET -__APIREL__/api_c/log_put.html#2 @log_put -__APIREL__/api_c/log_put.html#DB_CHECKPOINT log_put@DB_CHECKPOINT -__APIREL__/api_c/log_put.html#DB_CURLSN log_put@DB_CURLSN -__APIREL__/api_c/log_put.html#DB_FLUSH log_put@DB_FLUSH -__APIREL__/api_c/log_register.html#2 @log_register -__APIREL__/api_c/log_stat.html#2 @log_stat -__APIREL__/api_c/log_unregister.html#2 @log_unregister -__APIREL__/api_c/memp_fclose.html#2 @memp_fclose -__APIREL__/api_c/memp_fget.html#2 @memp_fget -__APIREL__/api_c/memp_fget.html#DB_MPOOL_CREATE memp_fget@DB_MPOOL_CREATE -__APIREL__/api_c/memp_fget.html#DB_MPOOL_LAST memp_fget@DB_MPOOL_LAST -__APIREL__/api_c/memp_fget.html#DB_MPOOL_NEW memp_fget@DB_MPOOL_NEW -__APIREL__/api_c/memp_fopen.html#2 @memp_fopen -__APIREL__/api_c/memp_fopen.html#DB_CREATE memp_fopen@DB_CREATE -__APIREL__/api_c/memp_fopen.html#DB_NOMMAP memp_fopen@DB_NOMMAP -__APIREL__/api_c/memp_fopen.html#DB_RDONLY memp_fopen@DB_RDONLY -__APIREL__/api_c/memp_fopen.html#ftype memp_fopen@ftype -__APIREL__/api_c/memp_fopen.html#pgcookie memp_fopen@pgcookie -__APIREL__/api_c/memp_fopen.html#fileid memp_fopen@fileid -__APIREL__/api_c/memp_fopen.html#lsn_offset memp_fopen@lsn_offset -__APIREL__/api_c/memp_fopen.html#clear_len memp_fopen@clear_len -__APIREL__/api_c/memp_fput.html#2 @memp_fput -__APIREL__/api_c/memp_fput.html#DB_MPOOL_CLEAN memp_fput@DB_MPOOL_CLEAN -__APIREL__/api_c/memp_fput.html#DB_MPOOL_DIRTY memp_fput@DB_MPOOL_DIRTY -__APIREL__/api_c/memp_fput.html#DB_MPOOL_DISCARD memp_fput@DB_MPOOL_DISCARD -__APIREL__/api_c/memp_fset.html#2 @memp_fset -__APIREL__/api_c/memp_fset.html#DB_MPOOL_CLEAN memp_fset@DB_MPOOL_CLEAN -__APIREL__/api_c/memp_fset.html#DB_MPOOL_DIRTY memp_fset@DB_MPOOL_DIRTY -__APIREL__/api_c/memp_fset.html#DB_MPOOL_DISCARD memp_fset@DB_MPOOL_DISCARD -__APIREL__/api_c/memp_fsync.html#2 @memp_fsync -__APIREL__/api_c/memp_register.html#2 @memp_register -__APIREL__/api_c/memp_stat.html#2 @memp_stat -__APIREL__/api_c/memp_sync.html#2 @memp_sync -__APIREL__/api_c/memp_trickle.html#2 @memp_trickle -__APIREL__/api_c/txn_abort.html#2 @txn_abort -__APIREL__/api_c/txn_begin.html#2 @txn_begin -__APIREL__/api_c/txn_begin.html#DB_TXN_NOSYNC txn_begin@DB_TXN_NOSYNC -__APIREL__/api_c/txn_begin.html#DB_TXN_NOWAIT txn_begin@DB_TXN_NOWAIT -__APIREL__/api_c/txn_begin.html#DB_TXN_SYNC txn_begin@DB_TXN_SYNC -__APIREL__/api_c/txn_checkpoint.html#2 @txn_checkpoint -__APIREL__/api_c/txn_checkpoint.html#DB_FORCE txn_checkpoint@DB_FORCE -__APIREL__/api_c/txn_commit.html#2 @txn_commit -__APIREL__/api_c/txn_commit.html#DB_TXN_NOSYNC txn_commit@DB_TXN_NOSYNC -__APIREL__/api_c/txn_commit.html#DB_TXN_SYNC txn_commit@DB_TXN_SYNC -__APIREL__/api_c/txn_id.html#2 @txn_id -__APIREL__/api_c/txn_prepare.html#2 @txn_prepare -__APIREL__/api_c/txn_stat.html#2 @txn_stat diff --git a/bdb/docs/api_c/set_func_close.html b/bdb/docs/api_c/set_func_close.html deleted file mode 100644 index 0d4af0aef66..00000000000 --- a/bdb/docs/api_c/set_func_close.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_close - - - - - - - -
-

db_env_set_func_close

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_close(int (*func_close)(int fd));
-

-

Description

-

Replace Berkeley DB calls to the IEEE/ANSI Std 1003.1 (POSIX) close function -with func_close, which must conform to the standard interface. -

The db_env_set_func_close interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_close interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_close function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_dirfree.html b/bdb/docs/api_c/set_func_dirfree.html deleted file mode 100644 index 249f69cc676..00000000000 --- a/bdb/docs/api_c/set_func_dirfree.html +++ /dev/null @@ -1,75 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_dirfree - - - - - - - -
-

db_env_set_func_dirfree

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_dirfree(void (*func_dirfree)(char **namesp, int cnt));
-

-

Description

-

The Berkeley DB library requires the ability to return any memory allocated as part -of the routine which reads through a directory and creates a list of files -that that the directory contains (see db_env_set_func_dirlist). -The func_dirfree argument must conform to the following interface: -

int dirfree(char **namesp, int cnt);
-

The namesp and cnt arguments are the same values as were -returned by the db_env_set_func_dirlist function. -

The func_dirfree function must return the value of errno on -failure and 0 on success. -

The db_env_set_func_dirfree interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_dirfree interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_dirfree interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The db_env_set_func_dirfree function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_dirlist.html b/bdb/docs/api_c/set_func_dirlist.html deleted file mode 100644 index 5025912e5d9..00000000000 --- a/bdb/docs/api_c/set_func_dirlist.html +++ /dev/null @@ -1,78 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_dirlist - - - - - - - -
-

db_env_set_func_dirlist

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_dirlist(
-    int (*func_dirlist)(const char *dir, char ***namesp, int *cntp));
-

-

Description

-

The Berkeley DB library requires the ability to read through a directory and -create a list of files that that the directory contains. The -func_dirlist argument must conform to the following interface: -

int dirlist(const char *dir, char ***namesp, int *cntp);
-

The dir argument is the name of the directory to be searched. -The function must return a pointer to an array of nul-terminated file -names in the memory location referenced by the argument namesp, -and a count of the number of elements in the array in the memory location -referenced by cntp. -

The func_dirlist function must return the value of errno on -failure and 0 on success. -

The db_env_set_func_dirlist interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_dirlist interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_dirlist interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The db_env_set_func_dirlist function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_exists.html b/bdb/docs/api_c/set_func_exists.html deleted file mode 100644 index 0b38b1e2203..00000000000 --- a/bdb/docs/api_c/set_func_exists.html +++ /dev/null @@ -1,75 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_exists - - - - - - - -
-

db_env_set_func_exists

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_exists(int (*func_exists)(const char *path, int *isdirp));
-

-

Description

-

The Berkeley DB library requires the ability to determine if a file exists, and -optionally, if it is a file of type directory. The func argument -must conform to the following interface: -

int exists(const char *path, int *isdirp);
-

The path argument is the pathname of the file to be checked. -

If the isdirp argument is non-NULL, it must be set to non-0 if -path is a directory, and 0 if path is not a directory. -

The func_exists function must return the value of errno on -failure and 0 on success. -

The db_env_set_func_exists interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_exists interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_exists interface may only be used to configure Berkeley DB before -the DBENV->open interface is called. -

The db_env_set_func_exists function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_free.html b/bdb/docs/api_c/set_func_free.html deleted file mode 100644 index 8b7b1afa60c..00000000000 --- a/bdb/docs/api_c/set_func_free.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_free - - - - - - - -
-

db_env_set_func_free

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_free(void (*func_free)(void *ptr));
-

-

Description

-

Replace Berkeley DB calls to the ANSI C X3.159-1989 (ANSI C) standard -free function with func_free, which must conform to -the standard interface. -

The db_env_set_func_free interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_free interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_free function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_fsync.html b/bdb/docs/api_c/set_func_fsync.html deleted file mode 100644 index f73956108b2..00000000000 --- a/bdb/docs/api_c/set_func_fsync.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_fsync - - - - - - - -
-

db_env_set_func_fsync

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_fsync(int (*func_fsync)(int fd));
-

-

Description

-

Replace Berkeley DB calls to the IEEE/ANSI Std 1003.1 (POSIX) fsync function -with func_fsync, which must conform to the standard interface. -

The db_env_set_func_fsync interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_fsync interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_fsync function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_ioinfo.html b/bdb/docs/api_c/set_func_ioinfo.html deleted file mode 100644 index 3a0143e57ea..00000000000 --- a/bdb/docs/api_c/set_func_ioinfo.html +++ /dev/null @@ -1,83 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_ioinfo - - - - - - - -
-

db_env_set_func_ioinfo

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_ioinfo(int (*func_ioinfo)(const char *path,
-    int fd, u_int32_t *mbytesp, u_int32_t *bytesp, u_int32_t *iosizep));
-

-

Description

-

The Berkeley DB library requires the ability to determine the size and I/O -characteristics of a file. The func_ioinfo argument must conform -to the following interface: -

int ioinfo(const char *path, int fd,
-u_int32_t *mbytesp, u_int32_t *bytesp, u_int32_t *iosizep);
-

The path argument is the pathname of the file to be checked, and the -fd argument is an open file descriptor on the file. -

If the mbytesp and bytesp arguments are non-NULL, the -ioinfo function must return in them the size of the file: the -number of megabytes in the file into the memory location referenced by -the mbytesp argument, and the number of bytes over and above that -number of megabytes into the memory location referenced by the -bytesp argument. -

In addition, if the iosizep argument is non-NULL, the ioinfo -function must return the optimum granularity for I/O operations to the file -in the memory location referenced by it. -

The func_ioinfo function must return the value of errno on -failure and 0 on success. -

The db_env_set_func_ioinfo interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_ioinfo interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_ioinfo function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_malloc.html b/bdb/docs/api_c/set_func_malloc.html deleted file mode 100644 index a4be5bfb04e..00000000000 --- a/bdb/docs/api_c/set_func_malloc.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_malloc - - - - - - - -
-

db_env_set_func_malloc

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_malloc(void *(*func_malloc)(size_t size));
-

-

Description

-

Replace Berkeley DB calls to the ANSI C X3.159-1989 (ANSI C) standard -malloc function with func_malloc, which must conform to -the standard interface. -

The db_env_set_func_malloc interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_malloc interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_malloc function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_map.html b/bdb/docs/api_c/set_func_map.html deleted file mode 100644 index e14e9c4aad7..00000000000 --- a/bdb/docs/api_c/set_func_map.html +++ /dev/null @@ -1,86 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_map - - - - - - - -
-

db_env_set_func_map

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_map(int (*func_map)(char *path,
-    size_t len, int is_region, int is_rdonly, void **addr));
-

-

Description

-

The Berkeley DB library requires the ability to map a file into memory and to -create shared memory regions (which may or may not be backed by files). -The func_map argument must conform to the following interface: -

int map(char *path, size_t len,
-int is_region, int is_rdonly, void **addr);
-

The path argument is the name of a file. -

The is_region argument will be zero if the intention is to map a -file into shared memory. In this case, the map function must map -the first len bytes of the file into memory and return a pointer -to the mapped location in the memory location referenced by the argument -addr. The is_rdonly argument will be non-zero if the file -is considered read-only by the caller. -

The is_region argument will be non-zero if the memory is intended -to be used as a shared memory region for synchronization between Berkeley DB -threads/processes. In this case, the returned memory may be of any kind -(e.g., anonymous), but must be able to support semaphores. In this case, -the path argument may be ignored (although future map -calls using the same path must return the same memory), and the -is_rdonly argument will always be zero. -

The func_map function must return the value of errno on -failure and 0 on success. -

The db_env_set_func_map interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_map interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_map function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_open.html b/bdb/docs/api_c/set_func_open.html deleted file mode 100644 index ff72d9882ed..00000000000 --- a/bdb/docs/api_c/set_func_open.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_open - - - - - - - -
-

db_env_set_func_open

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_open(int (*func_open)(const char *path, int flags, int mode));
-

-

Description

-

Replace Berkeley DB calls to the IEEE/ANSI Std 1003.1 (POSIX) open function -with func_open, which must conform to the standard interface. -

The db_env_set_func_open interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_open interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_open function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_read.html b/bdb/docs/api_c/set_func_read.html deleted file mode 100644 index b3ee9308118..00000000000 --- a/bdb/docs/api_c/set_func_read.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_read - - - - - - - -
-

db_env_set_func_read

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_read(ssize_t (*func_read)(int fd, void *buf, size_t nbytes));
-

-

Description

-

Replace Berkeley DB calls to the IEEE/ANSI Std 1003.1 (POSIX) read function -with func_read, which must conform to the standard interface. -

The db_env_set_func_read interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_read interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_read function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_realloc.html b/bdb/docs/api_c/set_func_realloc.html deleted file mode 100644 index 91e5835bcca..00000000000 --- a/bdb/docs/api_c/set_func_realloc.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_realloc - - - - - - - -
-

db_env_set_func_realloc

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_realloc(void *(*func_realloc)(void *ptr, size_t size));
-

-

Description

-

Replace Berkeley DB calls to the ANSI C X3.159-1989 (ANSI C) standard -realloc function with func_realloc, which must conform to -the standard interface. -

The db_env_set_func_realloc interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_realloc interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_realloc function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_rename.html b/bdb/docs/api_c/set_func_rename.html deleted file mode 100644 index bb588672359..00000000000 --- a/bdb/docs/api_c/set_func_rename.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_rename - - - - - - - -
-

db_env_set_func_rename

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_rename(int (*func_rename)(int fd));
-

-

Description

-

Replace Berkeley DB calls to the IEEE/ANSI Std 1003.1 (POSIX) close function -with func_close, which must conform to the standard interface. -

The db_env_set_func_rename interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_rename interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_rename function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_seek.html b/bdb/docs/api_c/set_func_seek.html deleted file mode 100644 index dd27384f672..00000000000 --- a/bdb/docs/api_c/set_func_seek.html +++ /dev/null @@ -1,81 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_seek - - - - - - - -
-

db_env_set_func_seek

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_seek(int (*func_seek)(int fd, size_t pgsize,
-    db_pgno_t pageno, u_int32_t relative, int rewind, int whence));
-

-

Description

-

The Berkeley DB library requires the ability to specify that a subsequent read -from or write to a file will occur at a specific location in that file. -The func_seek argument must conform to the following interface: -

int seek(int fd, size_t pgsize, db_pgno_t pageno,
-u_int32_t relative, int rewind, int whence);
-

The fd argument is an open file descriptor on the file. -

The seek function must cause a subsequent read from or write to -the file to occur at a byte offset specified by the calculation: -

(pgsize * pageno) + relative
-

If rewind is non-zero, the byte offset is treated as a backwards -seek, not a forwards one. -

The whence argument specifies where in the file the byte offset -is relative to, as described by the IEEE/ANSI Std 1003.1 (POSIX) lseek system -call. -

The func_seek function must return the value of errno on -failure and 0 on success. -

The db_env_set_func_seek interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_seek interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_seek function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_sleep.html b/bdb/docs/api_c/set_func_sleep.html deleted file mode 100644 index dd454b1a725..00000000000 --- a/bdb/docs/api_c/set_func_sleep.html +++ /dev/null @@ -1,76 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_sleep - - - - - - - -
-

db_env_set_func_sleep

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_sleep(int (*func_sleep)(u_long seconds, u_long microseconds));
-

-

Description

-

The Berkeley DB library requires the ability to cause a process to suspend itself -for a period of time, relinquishing control of the processor to any other -waiting thread of control. The func_sleep argument must conform -to the following interface: -

int sleep(u_long seconds, u_long microseconds);
-

The seconds and microseconds arguments specify the amount -of time to wait until the suspending thread of control should run again. -

The seconds and microseconds arguments may not be -normalized when the sleep function is called, i.e., the -microseconds argument may be greater than 1000000. -

The func_sleep function must return the value of errno on -failure and 0 on success. -

The db_env_set_func_sleep interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_sleep interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_sleep function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_unlink.html b/bdb/docs/api_c/set_func_unlink.html deleted file mode 100644 index 1e5e8e3cba9..00000000000 --- a/bdb/docs/api_c/set_func_unlink.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_unlink - - - - - - - -
-

db_env_set_func_unlink

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_unlink(int (*func_unlink)(const char *path));
-

-

Description

-

Replace Berkeley DB calls to the IEEE/ANSI Std 1003.1 (POSIX) unlink function -with func_unlink, which must conform to the standard interface. -

The db_env_set_func_unlink interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_unlink interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_unlink function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_unmap.html b/bdb/docs/api_c/set_func_unmap.html deleted file mode 100644 index 07635b48a80..00000000000 --- a/bdb/docs/api_c/set_func_unmap.html +++ /dev/null @@ -1,75 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_unmap - - - - - - - -
-

db_env_set_func_unmap

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_unmap(int (*func_unmap)(void *addr, size_t len));
-

-

Description

-

The Berkeley DB library requires the ability to unmap a file or shared memory -region from memory. The func_unmap argument must conform to the -following interface: -

int unmap(void *addr, size_t len);
-

The addr argument is the argument returned by the -db_env_set_func_map function when the file or region was mapped -into memory, and the len argument is the same as the len -argument specified to the db_env_set_func_map function when the -file or region was mapped into memory. -

The func_unmap function must return the value of errno on -failure and 0 on success. -

The db_env_set_func_unmap interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_unmap interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_unmap function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_write.html b/bdb/docs/api_c/set_func_write.html deleted file mode 100644 index 7b52b5078ba..00000000000 --- a/bdb/docs/api_c/set_func_write.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_write - - - - - - - -
-

db_env_set_func_write

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_write(
-    ssize_t (*func_write)(int fd, const void *buffer, size_t nbytes));
-

-

Description

-

Replace Berkeley DB calls to the IEEE/ANSI Std 1003.1 (POSIX) write function -with func_write, which must conform to the standard interface. -

The db_env_set_func_write interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_write interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_write function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/set_func_yield.html b/bdb/docs/api_c/set_func_yield.html deleted file mode 100644 index 23915aea68b..00000000000 --- a/bdb/docs/api_c/set_func_yield.html +++ /dev/null @@ -1,84 +0,0 @@ - - - - - -Berkeley DB: db_env_set_func_yield - - - - - - - -
-

db_env_set_func_yield

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-db_env_set_func_yield(int (*func_yield)(void));
-

-

Description

-

The Berkeley DB library requires the ability to yield the processor from the current -thread of control to any other waiting threads of control. -The func_yield argument must conform to the following interface: -

int yield(void);
-

The func_yield function must be able to cause the rescheduling -all participants in the current Berkeley DB environment, whether threaded or -not. It may be incorrect to supply a thread yield function if -more than a single process is operating in the Berkeley DB environment. This -is because many thread-yield functions will not allow other processes to -run, and the contested lock may be held by another process, not by another -thread. -

If no func_yield function is specified, or if the yield -function returns an error, the function specified by the -db_env_set_func_sleep entry will be used instead or subsequently, -i.e., if no yield function is specified, or it is possible for -the yield function to fail, the sleep function -must cause the processor to reschedule any waiting threads of -control for execution. -

The func_yield function must return the value of errno on -failure and 0 on success. -

The db_env_set_func_yield interface affects the entire application, not a single -database or database environment. -

While the db_env_set_func_yield interface may be used to configure Berkeley DB at any time -during the life of the application, it should normally be called before -making any calls to the db_env_create or db_create functions. -

The db_env_set_func_yield function returns a non-zero error value on failure and 0 on success. -

Errors

-

-

EINVAL
An invalid flag value or parameter was specified. -
-

See Also

-db_env_set_func_close, -db_env_set_func_dirfree, -db_env_set_func_dirlist, -db_env_set_func_exists, -db_env_set_func_free, -db_env_set_func_fsync, -db_env_set_func_ioinfo, -db_env_set_func_malloc, -db_env_set_func_map, -db_env_set_func_open, -db_env_set_func_read, -db_env_set_func_realloc, -db_env_set_func_seek, -db_env_set_func_sleep, -db_env_set_func_unlink, -db_env_set_func_unmap, -db_env_set_func_write -and -db_env_set_func_yield. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/txn_abort.html b/bdb/docs/api_c/txn_abort.html deleted file mode 100644 index 00056023aba..00000000000 --- a/bdb/docs/api_c/txn_abort.html +++ /dev/null @@ -1,63 +0,0 @@ - - - - - -Berkeley DB: txn_abort - - - - - - - -
-

txn_abort

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-txn_abort(DB_TXN *tid);
-

-

Description

-

The txn_abort function causes an abnormal termination of the -transaction. The log is played backwards and any necessary recovery -operations are initiated through the recover function specified -to DBENV->open. After the log processing is completed, all locks -held by the transaction are released. As is the case for -txn_commit, applications that require strict two-phase locking -should not explicitly release any locks. -

In the case of nested transactions, aborting a parent transaction causes -all children (unresolved or not) of the parent transaction to be aborted. -

Once the txn_abort function returns, the DB_TXN handle may not -be accessed again. -

The txn_abort function returns a non-zero error value on failure and 0 on success. -

Errors

-

The txn_abort 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 txn_abort function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/txn_begin.html b/bdb/docs/api_c/txn_begin.html deleted file mode 100644 index 0241d5c1fdb..00000000000 --- a/bdb/docs/api_c/txn_begin.html +++ /dev/null @@ -1,93 +0,0 @@ - - - - - -Berkeley DB: txn_begin - - - - - - - -
-

txn_begin

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-txn_begin(DB_ENV *env,
-	DB_TXN *parent, DB_TXN **tid, u_int32_t flags);
-

-

Description

-

The txn_begin method creates a new transaction in the environment -and copies a pointer to a DB_TXN that uniquely identifies it into -the memory referenced by tid. -

If the parent argument is non-NULL, the new transaction will -be a nested transaction, with the transaction indicated by -parent as its parent. Transactions may be -nested to any level. -

The flags parameter must be set to 0 or one of the following -values: -

-

DB_TXN_NOSYNC
Do not synchronously flush the log when this transaction commits or -prepares. This means the transaction will exhibit the ACI (atomicity, -consistency and isolation) properties, but not D (durability), i.e., -database integrity will be maintained but it is possible that this -transaction may be undone during recovery instead of being redone. -

This behavior may be set for an entire Berkeley DB environment as part of the -DBENV->set_flags interface. -

DB_TXN_NOWAIT
If a lock is unavailable for any Berkeley DB operation performed in the context -of this transaction, return immediately instead of blocking on the lock. -The error return in the case will be DB_LOCK_NOTGRANTED. -

DB_TXN_SYNC
Synchronously flush the log when this transaction commits or prepares. -This means the transaction will exhibit all of the ACID (atomicity, -consistency and isolation and durability) properties. -

This behavior is the default for Berkeley DB environments unless the -DB_TXN_NOSYNC flag was specified to the DBENV->set_flags -interface. -

-

Note: An transaction may not span threads, -i.e., each transaction must begin and end in the same thread, and each -transaction may only be used by a single thread. -

Note: cursors may not span transactions, i.e., each cursor must be opened -and closed within a single transaction. -

Note: a parent transaction may not issue any Berkeley DB operations, except for -txn_begin, txn_abort and txn_commit, while it has -active child transactions (child transactions that have not yet been -committed or aborted). -

The txn_begin function returns a non-zero error value on failure and 0 on success. -

Errors

-

The txn_begin function may fail and return a non-zero error for the following conditions: -

-

ENOMEM
The maximum number of concurrent transactions has been reached. -
-

The txn_begin 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 txn_begin function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/txn_checkpoint.html b/bdb/docs/api_c/txn_checkpoint.html deleted file mode 100644 index 140edee57d7..00000000000 --- a/bdb/docs/api_c/txn_checkpoint.html +++ /dev/null @@ -1,75 +0,0 @@ - - - - - -Berkeley DB: txn_checkpoint - - - - - - - -
-

txn_checkpoint

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-txn_checkpoint(const DB_ENV *env,
-    u_int32_t kbyte, u_int32_t min, u_int32_t flags);
-

-

Description

-

The txn_checkpoint function flushes the underlying memory pool, -writes a checkpoint record to the log and then flushes the log. -

If either kbyte or min is non-zero, the checkpoint is only -done if there has been activity since the last checkpoint and either -more than min minutes have passed since the last checkpoint, -or if more than kbyte kilobytes of log data have been written since -the last checkpoint. -

The flags parameter must be set to 0 or one of the following -values: -

-

DB_FORCE
Force a checkpoint record even if there has been no activity since the -last checkpoint. -
-

The txn_checkpoint function returns a non-zero error value on failure, 0 on success, and returns DB_INCOMPLETE if there were pages that needed to be -written to complete the checkpoint but that memp_sync was unable -to write immediately. -

The txn_checkpoint function is the underlying function used by the db_checkpoint utility. -See the db_checkpoint utility source code for an example of using txn_checkpoint -in a IEEE/ANSI Std 1003.1 (POSIX) environment. -

Errors

-

The txn_checkpoint function may fail and return a non-zero error for the following conditions: -

-

EINVAL
An invalid flag value or parameter was specified. -
-

The txn_checkpoint 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 txn_checkpoint function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/txn_commit.html b/bdb/docs/api_c/txn_commit.html deleted file mode 100644 index 7fca3d08d7b..00000000000 --- a/bdb/docs/api_c/txn_commit.html +++ /dev/null @@ -1,83 +0,0 @@ - - - - - -Berkeley DB: txn_commit - - - - - - - -
-

txn_commit

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-txn_commit(DB_TXN *tid, u_int32_t flags);
-

-

Description

-

The txn_commit function ends the transaction. In the case of nested -transactions, if the transaction is a parent transaction, committing -the parent transaction causes all unresolved children of the parent to -be committed. -

In the case of nested transactions, if the transaction is a child -transaction, its locks are not released, but are acquired by its parent. -While the commit of the child transaction will succeed, the actual -resolution of the child transaction is postponed until the parent -transaction is committed or aborted, i.e., if its parent transaction -commits, it will be committed, and if its parent transaction aborts, it -will be aborted. -

The flags parameter must be set to 0 or one of the following -values: -

-

DB_TXN_NOSYNC
Do not synchronously flush the log. This means the transaction will -exhibit the ACI (atomicity, consistency and isolation) properties, but -not D (durability), i.e., database integrity will be maintained but it is -possible that this transaction may be undone during recovery instead of -being redone. -

This behavior may be set for an entire Berkeley DB environment as part of the -DBENV->set_flags interface. -

DB_TXN_SYNC
Synchronously flush the log. This means the transaction will exhibit -all of the ACID (atomicity, consistency and isolation and durability) -properties. -

This behavior is the default for Berkeley DB environments unless the -DB_TXN_NOSYNC flag was specified to the DBENV->set_flags -or txn_begin interfaces. -

-

Once the txn_commit function returns, the DB_TXN handle may not -be accessed again. If txn_commit encounters an error, the -transaction and all child transactions of the transaction are aborted. -

The txn_commit function returns a non-zero error value on failure and 0 on success. -

Errors

-

The txn_commit 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 txn_commit function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/txn_id.html b/bdb/docs/api_c/txn_id.html deleted file mode 100644 index bcda4bcdfff..00000000000 --- a/bdb/docs/api_c/txn_id.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - -Berkeley DB: txn_id - - - - - - - -
-

txn_id

-		 -APIRef -
-

- -

-#include <db.h>
-

-u_int32_t
-txn_id(DB_TXN *tid);
-

-

Description

-

The txn_id function returns the unique transaction id associated with the -specified transaction. Locking calls made on behalf of this transaction -should use the value returned from txn_id as the locker parameter -to the lock_get or lock_vec calls. -

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/txn_prepare.html b/bdb/docs/api_c/txn_prepare.html deleted file mode 100644 index 549a6f074a0..00000000000 --- a/bdb/docs/api_c/txn_prepare.html +++ /dev/null @@ -1,63 +0,0 @@ - - - - - -Berkeley DB: txn_prepare - - - - - - - -
-

txn_prepare

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-txn_prepare(DB_TXN *tid);
-

-

Description

-

The txn_prepare function initiates the beginning of a two-phase commit. -

In a distributed transaction environment, Berkeley DB can be used as a local -transaction manager. In this case, the distributed transaction manager -must send prepare messages to each local manager. The local -manager must then issue a txn_prepare and await its successful -return before responding to the distributed transaction manager. Only -after the distributed transaction manager receives successful responses -from all of its prepare messages should it issue any -commit messages. -

In the case of nested transactions, preparing a parent transaction -causes all unresolved children of the parent transaction to be prepared. -

The txn_prepare function returns a non-zero error value on failure and 0 on success. -

Errors

-

The txn_prepare 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 txn_prepare function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - diff --git a/bdb/docs/api_c/txn_stat.html b/bdb/docs/api_c/txn_stat.html deleted file mode 100644 index 769283f93c2..00000000000 --- a/bdb/docs/api_c/txn_stat.html +++ /dev/null @@ -1,94 +0,0 @@ - - - - - -Berkeley DB: txn_stat - - - - - - - -
-

txn_stat

-		 -APIRef -
-

- -

-#include <db.h>
-

-int
-txn_stat(DB_ENV *env,
-    DB_TXN_STAT **statp, void *(*db_malloc)(size_t));
-

-

Description

-

The txn_stat function -creates a statistical structure and copies a pointer to it into a -user-specified memory location. -

Statistical structures are created in allocated memory. If db_malloc is non-NULL, it -is called to allocate the memory, otherwise, the library function -malloc(3) is used. The function db_malloc must match -the calling conventions of the malloc(3) library routine. -Regardless, the caller is responsible for deallocating the returned -memory. To deallocate returned memory, free the returned memory -reference, references inside the returned memory do not need to be -individually freed. -

The transaction region statistics are stored in a structure of type -DB_TXN_STAT. The following DB_TXN_STAT fields will be filled in: -

-
DB_LSN st_last_ckp;
The LSN of the last checkpoint. -
DB_LSN st_pending_ckp;
The LSN of any checkpoint that is currently in progress. If -st_pending_ckp is the same as st_last_ckp there -is no checkpoint in progress. -
time_t st_time_ckp;
The time the last completed checkpoint finished (as the number of seconds -since the Epoch, returned by the IEEE/ANSI Std 1003.1 (POSIX) time interface). -
u_int32_t st_last_txnid;
The last transaction ID allocated. -
u_int32_t st_maxtxns;
The maximum number of active transactions possible. -
u_int32_t st_nactive;
The number of transactions that are currently active. -
u_int32_t st_maxnactive;
The maximum number of active transactions at any one time. -
u_int32_t st_nbegins;
The number of transactions that have begun. -
u_int32_t st_naborts;
The number of transactions that have aborted. -
u_int32_t st_ncommits;
The number of transactions that have committed. -
u_int32_t st_regsize;
The size of the region. -
u_int32_t st_region_wait;
The number of times that a thread of control was forced to wait before -obtaining the region lock. -
u_int32_t st_region_nowait;
The number of times that a thread of control was able to obtain -the region lock without waiting. -
DB_TXN_ACTIVE * st_txnarray;
A pointer to an array of st_nactive DB_TXN_ACTIVE structures, -describing the currently active transactions. The following fields of -the DB_TXN_ACTIVE structure will be filled in: -

-

u_int32_t txnid;
The transaction ID as returned by txn_begin. -
u_int32_t parentid;
The transaction ID of the parent transaction (or 0, if no parent). -
DB_LSN lsn;
The log sequence number of the transaction-begin record. -
-
-

The txn_stat function returns a non-zero error value on failure and 0 on success. -

Errors

-

The txn_stat 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 txn_stat function may fail and return -DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail -in the same way. -

See Also

-DBENV->set_tx_max, -DBENV->set_tx_recover, -DBENV->set_tx_timestamp, -txn_abort, -txn_begin, -txn_checkpoint, -txn_commit, -txn_id, -txn_prepare -and -txn_stat. - -

 -APIRef -
-

Copyright Sleepycat Software - - -- cgit v1.2.1