diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2015-02-17 17:25:57 +0000 |
|---|---|---|
| committer | <> | 2015-03-17 16:26:24 +0000 |
| commit | 780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch) | |
| tree | 598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/transapp_admin.html | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'docs/programmer_reference/transapp_admin.html')
| -rw-r--r-- | docs/programmer_reference/transapp_admin.html | 71 |
1 files changed, 44 insertions, 27 deletions
diff --git a/docs/programmer_reference/transapp_admin.html b/docs/programmer_reference/transapp_admin.html index f115930f..dfa1b83f 100644 --- a/docs/programmer_reference/transapp_admin.html +++ b/docs/programmer_reference/transapp_admin.html @@ -14,17 +14,16 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> - <th colspan="3" align="center">Environment infrastructure</th> + <th colspan="3" align="center">Environment + infrastructure</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="transapp_nested.html">Prev</a> </td> - <th width="60%" align="center">Chapter 11. - Berkeley DB Transactional Data Store Applications - </th> + <th width="60%" align="center">Chapter 11. Berkeley DB Transactional Data Store Applications </th> <td width="20%" align="right"> <a accesskey="n" href="transapp_deadlock.html">Next</a></td> </tr> </table> @@ -34,35 +33,53 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="transapp_admin"></a>Environment infrastructure</h2> + <h2 class="title" style="clear: both"><a id="transapp_admin"></a>Environment + infrastructure</h2> </div> </div> </div> - <p>When building transactional applications, it is usually necessary to -build an administrative infrastructure around the database environment. -There are five components to this infrastructure, and each is -supported by the Berkeley DB package in two different ways: a standalone -utility and one or more library interfaces.</p> + <p> + When building transactional applications, it is usually + necessary to build an administrative infrastructure around the + database environment. There are five components to this + infrastructure, and each is supported by the Berkeley DB + package in two different ways: a standalone utility and one or + more library interfaces. + </p> <div class="itemizedlist"> <ul type="disc"> - <li>Deadlock detection: <a href="../api_reference/C/db_deadlock.html" class="olink">db_deadlock</a> utility, <a href="../api_reference/C/lockdetect.html" class="olink">DB_ENV->lock_detect()</a>, <a href="../api_reference/C/envset_lk_detect.html" class="olink">DB_ENV->set_lk_detect()</a></li> - <li>Checkpoints: the <a href="../api_reference/C/db_checkpoint.html" class="olink">db_checkpoint</a> utility, <a href="../api_reference/C/txncheckpoint.html" class="olink">DB_ENV->txn_checkpoint()</a></li> - <li>Database and log file archival: the <a href="../api_reference/C/db_archive.html" class="olink">db_archive</a> utility, <a href="../api_reference/C/logarchive.html" class="olink">DB_ENV->log_archive()</a></li> - <li>Log file removal: <a href="../api_reference/C/db_archive.html" class="olink">db_archive</a> utility, <a href="../api_reference/C/logarchive.html" class="olink">DB_ENV->log_archive()</a></li> - <li>Recovery procedures: <a href="../api_reference/C/db_recover.html" class="olink">db_recover</a> utility, <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a></li> + <li> + Deadlock detection: <a href="../api_reference/C/db_deadlock.html" class="olink">db_deadlock</a> utility, <a href="../api_reference/C/lockdetect.html" class="olink">DB_ENV->lock_detect()</a>, + <a href="../api_reference/C/envset_lk_detect.html" class="olink">DB_ENV->set_lk_detect()</a></li> + <li> + Checkpoints: the <a href="../api_reference/C/db_checkpoint.html" class="olink">db_checkpoint</a> utility, + <a href="../api_reference/C/txncheckpoint.html" class="olink">DB_ENV->txn_checkpoint()</a></li> + <li> + Database and log file archival: the <a href="../api_reference/C/db_archive.html" class="olink">db_archive</a> utility, + <a href="../api_reference/C/logarchive.html" class="olink">DB_ENV->log_archive()</a></li> + <li> + Log file removal: <a href="../api_reference/C/db_archive.html" class="olink">db_archive</a> utility, + <a href="../api_reference/C/logarchive.html" class="olink">DB_ENV->log_archive()</a></li> + <li> + Recovery procedures: <a href="../api_reference/C/db_recover.html" class="olink">db_recover</a> utility, + <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a></li> </ul> </div> - <p>When writing multithreaded server applications and/or applications -intended for download from the Web, it is usually simpler to create -local threads that are responsible for administration of the database -environment as scheduling is often simpler in a single-process model, -and only a single binary need be installed and run. However, the -supplied utilities can be generally useful tools even when the -application is responsible for doing its own administration because -applications rarely offer external interfaces to database -administration. The utilities are required when programming to a Berkeley DB -scripting interface because the scripting APIs do not always offer -interfaces to the administrative functionality.</p> + <p> + When writing multithreaded server applications and/or + applications intended for download from the Web, it is usually + simpler to create local threads that are responsible for + administration of the database environment as scheduling is + often simpler in a single-process model, and only a single + binary need be installed and run. However, the supplied + utilities can be generally useful tools even when the + application is responsible for doing its own administration + because applications rarely offer external interfaces to + database administration. The utilities are required when + programming to a Berkeley DB scripting interface because the + scripting APIs do not always offer interfaces to the + administrative functionality. + </p> </div> <div class="navfooter"> <hr /> |