|
|
DB_ENV->set_app_dispatch |
#include <db.h>int DB_ENV->set_app_dispatch(DB_ENV *dbenv, int (*tx_recover)(DB_ENV *dbenv, DBT *log_rec, DB_LSN *lsn, db_recops op));
Declare a function to be called during transaction abort and recovery to process application-specific log records.
The DB_ENV->set_app_dispatch method configures operations performed using the specified DB_ENV handle, not all operations performed on the underlying database environment.
The DB_ENV->set_app_dispatch method may not be called after the DB_ENV->open method is called. If the database environment already exists when DB_ENV->open is called, the information specified to DB_ENV->set_app_dispatch must be consistent with the existing environment or corruption can occur.
The DB_ENV->set_app_dispatch method returns a non-zero error value on failure and 0 on success.
The DB_TXN_FORWARD_ROLL and DB_TXN_APPLY operations frequently imply the same actions, redoing changes that appear in the log record, although if a recovery function is to be used on a replication client where reads may be taking place concurrently with the processing of incoming messages, DB_TXN_APPLY operations should also perform appropriate locking. The macro DB_REDO(op) checks that the operation is one of DB_TXN_FORWARD_ROLL or DB_TXN_APPLY, and should be used in the recovery code to refer to the conditions under which operations should be redone. Similarly, the macro DB_UNDO(op) checks if the operation is one of DB_TXN_BACKWARD_ROLL or DB_TXN_ABORT.
The function must return 0 on success and either errno or a value outside of the Berkeley DB error name space on failure.
The DB_ENV->set_app_dispatch method may fail and return one of the following non-zero errors:
Copyright (c) 1996-2005 Sleepycat Software, Inc. - All rights reserved.