DbTxn
DbTxn |
|
import com.sleepycat.db.*;public class DbTxn extends Object { ... }
This manual page describes the specific details of the DbTxn class.
The DbEnv transaction methods and the DbTxn class provide transaction semantics. Full transaction support is provided by a collection of modules that provide interfaces to the services required for transaction processing. These services are recovery, concurrency control, and the management of shared data.
Transaction semantics can be applied to the access methods described in Db through method call parameters.
The model intended for transactional use (and the one that is used by the access methods) is write-ahead logging to record both before- and after-images. Locking follows a two-phase protocol with all locks being released at transaction commit.
|
|
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
a51 1
DbTxn.set_timeout
d56 1
a56 1
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d1 2
a2 2
a3 1
d27 12
a38 13
The DbTxn object is the handle for a transaction. Methods off the DbTxn handle are used to configure, abort and commit the transaction. DbTxn handles are provided to Db methods in order to transactionally protect those database operations.
DbTxn handles are not free-threaded; transactions handles may be used by multiple threads, but only serially, that is, the application must serialize access to the DbTxn handle. Once the DbTxn.abort or DbTxn.commit methods are called, the handle may not be accessed again, regardless of the method's return. In addition, parent transactions may not issue any Berkeley DB operations while they have active child transactions (child transactions that have not yet been committed or aborted) except for DbEnv.txn_begin, DbTxn.abort and DbTxn.commit. d40 1 a40 1 DbEnv, DbTxn d42 13 a54 1 Transaction Subsystem and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d28 13 a40 12
This manual page describes the specific details of the DbTxn class.
The DbEnv transaction methods and the DbTxn class provide transaction semantics. Full transaction support is provided by a collection of modules that provide interfaces to the services required for transaction processing. These services are recovery, concurrency control, and the management of shared data.
Transaction semantics can be applied to the access methods described in Db through method call parameters.
The model intended for transactional use (and the one that is used by the access methods) is write-ahead logging to record both before- and after-images. Locking follows a two-phase protocol with all locks being released at transaction commit. d42 1 a42 1 DbEnv, DbTxn d44 1 a44 13 DbEnv.set_tx_max, DbEnv.set_tx_timestamp, DbTxn.abort, DbEnv.txn_begin, DbEnv.txn_checkpoint, DbTxn.commit, DbTxn.discard, DbTxn.id, DbTxn.prepare, DbEnv.txn_recover, DbTxn.set_timeout and DbEnv.txn_stat. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d27 12 a38 13
The DbTxn object is the handle for a transaction. Methods off the DbTxn handle are used to configure, abort and commit the transaction. DbTxn handles are provided to Db methods in order to transactionally protect those database operations.
DbTxn handles are not free-threaded; transactions handles may be used by multiple threads, but only serially, that is, the application must serialize access to the DbTxn handle. Once the DbTxn.abort or DbTxn.commit methods are called, the handle may not be accessed again, regardless of the method's return. In addition, parent transactions may not issue any Berkeley DB operations while they have active child transactions (child transactions that have not yet been committed or aborted) except for DbEnv.txn_begin, DbTxn.abort and DbTxn.commit. d40 1 a40 1 DbEnv, DbTxn d42 13 a54 1 Transaction Subsystem and Related Methods @