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.54.00; author rse; state dead;
branches;
next 1.1;
commitid z4cpSiAhOCXk5PLs;
1.1
date 2001.07.23.20.45.37; author rse; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2001.07.23.20.45.37; author rse; state Exp;
branches;
next 1.1.1.2;
1.1.1.2
date 2002.01.08.00.30.10; author rse; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2003.01.18.13.49.00; author rse; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2001.12.06.00.08.12; author rse; state Exp;
branches;
next 1.1.1.5;
1.1.1.5
date 2003.01.18.14.04.59; author rse; state Exp;
branches;
next ;
desc
@@
1.2
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB: DbEnv.log_put
DbEnv.log_put
|
 
|
import com.sleepycat.db.*;
public void log_put(DbLsn lsn, Dbt data, int flags)
throws DbException;
Description
The DbEnv.log_put method appends records to the log. The DbLsn of
the put record is returned in the lsn argument. The flags
argument may be set to one of the following values:
- Db.DB_CHECKPOINT
- The log should write a checkpoint record, recording any information
necessary to make the log structures recoverable after a crash.
- Db.DB_CURLSN
- The DbLsn of the next record to be put is returned in the
lsn argument.
- Db.DB_FLUSH
- The log is forced to disk after this record is written, guaranteeing
that all records with DbLsn 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 DbTxn.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
DbLsn of the previous log record for the same transaction, to
support chaining back through the transaction's log records during
undo.)
The DbEnv.log_put method throws an exception that encapsulates a non-zero error value on
failure.
Errors
The DbEnv.log_flush method may fail and throw an exception encapsulating 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 DbEnv.log_put method may fail and throw an exception for errors specified for other Berkeley DB and C library or system methods.
If a catastrophic error has occurred, the DbEnv.log_put method may fail and throw
a DbRunRecoveryException, in which case all subsequent Berkeley DB calls
will fail in the same way.
Class
DbEnv
See Also
DbEnv.set_lg_bsize,
DbEnv.set_lg_dir,
DbEnv.set_lg_max,
DbEnv.set_lg_regionmax,
DbEnv.log_archive,
DbEnv.log_compare,
DbEnv.log_file,
DbEnv.log_flush,
DbEnv.log_get,
DbEnv.log_put,
DbEnv.log_register,
DbEnv.log_stat,
and
DbEnv.log_unregister.
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
d17 1
a17 1
d25 1
a25 1
throws DbException;
d38 3
a40 2
one being "put" are on disk before DbEnv.log_put returns.
d49 1
a70 1
DbEnv.log_cursor,
d73 1
a76 2
DbEnv.log_unregister,
DbLogc.logc_close
d78 1
a78 1
DbLogc.logc_get.
d81 1
a81 1
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d1 2
a2 2
a3 1
d32 4
d57 3
a59 3
If a catastrophic error has occurred, the DbEnv.log_put method may fail and
throw a DbRunRecoveryException,
in which case all subsequent Berkeley DB calls will fail in the same way.
d61 1
a61 1
DbEnv, DbLogc, DbLsn
d63 16
a78 1
Logging Subsystem and Related Methods
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d1 2
a2 2
d4 1
a32 4
Db.DB_CHECKPOINTThe log should write a checkpoint record, recording any information
necessary to make the log structures recoverable after a crash.
Db.DB_CURLSNThe DbLsn of the next record to be put is returned in the
lsn argument.
d54 3
a56 3
If a catastrophic error has occurred, the DbEnv.log_put method may fail and throw
a DbRunRecoveryException, in which case all subsequent Berkeley DB calls
will fail in the same way.
d58 1
a58 1
DbEnv
d60 1
a60 16
DbEnv.set_lg_bsize,
DbEnv.set_lg_dir,
DbEnv.set_lg_max,
DbEnv.set_lg_regionmax,
DbEnv.log_archive,
DbEnv.log_compare,
DbEnv.log_cursor,
DbEnv.log_file,
DbEnv.log_flush,
DbEnv.log_put,
DbEnv.log_register,
DbEnv.log_stat,
DbEnv.log_unregister,
DbLogc.logc_close
and
DbLogc.logc_get.
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d1 2
a2 2
a3 1
d32 4
d57 3
a59 3
If a catastrophic error has occurred, the DbEnv.log_put method may fail and
throw a DbRunRecoveryException,
in which case all subsequent Berkeley DB calls will fail in the same way.
d61 1
a61 1
DbEnv, DbLogc, DbLsn
d63 16
a78 1
Logging Subsystem and Related Methods
@