head 1.2; access; symbols RPM_4_2_1:1.1.1.4 RPM_4_2:1.1.1.4 RPM_4_1_1:1.1.1.4 RPM_4_1:1.1.1.3 RPM_4_0_5:1.1.1.2 RPM_4_0_4:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.56.25; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2002.01.08.00.30.13; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2002.01.08.00.30.13; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2003.01.18.13.49.04; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2001.10.15.03.47.35; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2003.01.18.14.05.00; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB Reference Guide: Release 4.0: log_XXX

Berkeley DB Reference Guide:
Upgrading Berkeley DB Applications

 PrevRefNext

Release 4.0: log_XXX

The C API for the Berkeley DB Logging subsystem was reworked in the 4.0 release as follows:

Historic functional interfaceBerkeley DB 4.X method
log_archiveDB_ENV->log_archive
log_fileDB_ENV->log_file
log_flushDB_ENV->log_flush
log_getDB_ENV->log_cursor, DB_LOGC->get, DB_LOGC->close
log_putDB_ENV->log_put
log_registerDB_ENV->log_register
log_statDB_ENV->log_stat
log_unregisterDB_ENV->log_unregister

Applications calling any of these functions should update their calls to use the enclosing DB_ENV handle's method (in all cases other than the log_get call, this is easily done as the first argument to the existing call is the correct handle to use).

Application calls to the historic log_get interface must be replaced with the creation of a log file cursor (a DB_LOGC object), using the DB_ENV->log_cursor function, calls to the DB_LOGC->get function to retrieve log records and calls to the DB_LOGC->close function to destroy the cursor. It may also be possible to simplify some applications. In previous releases of Berkeley DB, the DB_CURRENT, DB_NEXT, and DB_PREV flags to the log_get function could not be used by a free-threaded DB_ENV handle. If their DB_ENV handle was free-threaded, applications had to create an additional, unique environment handle by separately calling DB_ENV->open without specifying DB_THREAD. This is no longer an issue in the log cursor interface, and applications may be able to remove the now unnecessary creation of the additional DB_ENV object.

Finally, the DB_ENV->log_stat call has been changed in the 4.0 release to take a flags argument. To leave their historic behavior unchanged, applications should add a final argument of 0 to any calls made to DB_ENV->log_stat.

PrevRefNext

Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Import: RPM 4.0.4 @ text @@ 1.1.1.2 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d26 1 a26 1 log_registerDB_ENV->log_register d28 1 a28 1 log_unregisterDB_ENV->log_unregister d31 1 a31 1 to use the enclosing DB_ENV handle's method (in all cases other d35 3 a37 3 with the creation of a log file cursor (a DB_LOGC object), using the DB_ENV->log_cursor method, calls to the DB_LOGC->get method to retrieve log records and calls to the DB_LOGC->close method to destroy the cursor. It d40 2 a41 2 log_get function could not be used by a free-threaded DB_ENV handle. If their DB_ENV handle was free-threaded, applications d46 1 a46 1 DB_ENV object. @ 1.1.1.3 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d27 1 a27 1 log_registerDB_ENV->log_register d29 1 a29 1 log_unregisterDB_ENV->log_unregister d32 1 a32 1 to use the enclosing DB_ENV handle's method (in all cases other d36 3 a38 3 with the creation of a log file cursor (a DB_LOGC object), using the DB_ENV->log_cursor function, calls to the DB_LOGC->get function to retrieve log records and calls to the DB_LOGC->close function to destroy the cursor. It d41 2 a42 2 log_get function could not be used by a free-threaded DB_ENV handle. If their DB_ENV handle was free-threaded, applications d47 1 a47 1 DB_ENV object. @ 1.1.1.4 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d26 1 a26 1 log_registerDB_ENV->log_register d28 1 a28 1 log_unregisterDB_ENV->log_unregister d31 1 a31 1 to use the enclosing DB_ENV handle's method (in all cases other d35 3 a37 3 with the creation of a log file cursor (a DB_LOGC object), using the DB_ENV->log_cursor method, calls to the DB_LOGC->get method to retrieve log records and calls to the DB_LOGC->close method to destroy the cursor. It d40 2 a41 2 log_get function could not be used by a free-threaded DB_ENV handle. If their DB_ENV handle was free-threaded, applications d46 1 a46 1 DB_ENV object. @