head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.52.54; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.08; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.56; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.07.58; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.56; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: DB_ENV->set_tx_timestamp

DB_ENV->set_tx_timestamp

 APIRef 

#include <db.h>


int
DB_ENV->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; that is, 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 DB_ENV->set_tx_timestamp interface may be used only to configure Berkeley DB before the DB_ENV->open interface is called.

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

Errors

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

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.

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

See Also

DB_ENV->set_tx_max, DB_ENV->set_tx_recover, DB_ENV->set_tx_timestamp, txn_abort, txn_begin, txn_checkpoint, txn_commit, txn_discard, txn_id, txn_prepare, txn_recover, and txn_stat.

APIRef

Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 d54 8 a61 9 DB_TXN->abort, DB_ENV->txn_begin, DB_ENV->txn_checkpoint, DB_TXN->commit, DB_TXN->discard, DB_TXN->id, DB_TXN->prepare, DB_ENV->txn_recover, DB_TXN->set_timeout d63 1 a63 1 DB_ENV->txn_stat. @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d36 3 a38 6

The DB_ENV->set_tx_timestamp method configures operations performed using the specified DB_ENV handle, not all operations performed on the underlying database environment.

The DB_ENV->set_tx_timestamp interface may not be called after the DB_ENV->open interface is called.

The DB_ENV->set_tx_timestamp method returns a non-zero error value on failure and 0 on success. d40 1 a40 1

The DB_ENV->set_tx_timestamp method may fail and return a non-zero error for the following conditions: d46 4 a49 6

The DB_ENV->set_tx_timestamp method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_tx_timestamp method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_TXN d51 14 a64 1 Transaction Subsystem and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d37 6 a42 3

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

The DB_ENV->set_tx_timestamp function returns a non-zero error value on failure and 0 on success. d44 1 a44 1

The DB_ENV->set_tx_timestamp function may fail and return a non-zero error for the following conditions: d50 6 a55 4

The DB_ENV->set_tx_timestamp 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->set_tx_timestamp function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d57 1 a57 14 DB_ENV->set_tx_max, DB_ENV->set_tx_recover, DB_ENV->set_tx_timestamp, DB_TXN->abort, DB_ENV->txn_begin, DB_ENV->txn_checkpoint, DB_TXN->commit, DB_TXN->discard, DB_TXN->id, DB_TXN->prepare, DB_ENV->txn_recover, DB_TXN->set_timeout and DB_ENV->txn_stat. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d36 3 a38 6

The DB_ENV->set_tx_timestamp method configures operations performed using the specified DB_ENV handle, not all operations performed on the underlying database environment.

The DB_ENV->set_tx_timestamp interface may not be called after the DB_ENV->open interface is called.

The DB_ENV->set_tx_timestamp method returns a non-zero error value on failure and 0 on success. d40 1 a40 1

The DB_ENV->set_tx_timestamp method may fail and return a non-zero error for the following conditions: d46 4 a49 6

The DB_ENV->set_tx_timestamp method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_tx_timestamp method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_TXN d51 14 a64 1 Transaction Subsystem and Related Methods @