diff options
Diffstat (limited to 'docs/programmer_reference/intro_what.html')
| -rw-r--r-- | docs/programmer_reference/intro_what.html | 92 |
1 files changed, 57 insertions, 35 deletions
diff --git a/docs/programmer_reference/intro_what.html b/docs/programmer_reference/intro_what.html index 84da80b6..e9cd540f 100644 --- a/docs/programmer_reference/intro_what.html +++ b/docs/programmer_reference/intro_what.html @@ -14,7 +14,7 @@ <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> @@ -22,9 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="intro_need.html">Prev</a> </td> - <th width="60%" align="center">Chapter 1. - Introduction - </th> + <th width="60%" align="center">Chapter 1. Introduction </th> <td width="20%" align="right"> <a accesskey="n" href="intro_distrib.html">Next</a></td> </tr> </table> @@ -38,49 +36,72 @@ </div> </div> </div> - <p>Berkeley DB also provides core database services to developers. These -services include:</p> + <p> + Berkeley DB also provides core database services to + developers. These services include: + </p> <div class="variablelist"> <dl> <dt> <span class="term">Page cache management:</span> </dt> - <dd>The page cache provides fast access to a cache of database pages, -handling the I/O associated with the cache to ensure that dirty pages -are written back to the file system and that new pages are allocated on -demand. Applications may use the Berkeley DB shared memory buffer manager to -serve their own files and pages.</dd> + <dd> + The page cache provides fast access to a cache + of database pages, handling the I/O associated with + the cache to ensure that dirty pages are written back + to the file system and that new pages are allocated on + demand. Applications may use the Berkeley DB shared + memory buffer manager to serve their own files and + pages. + </dd> <dt> <span class="term">Transactions and logging:</span> </dt> - <dd>The transaction and logging systems provide recoverability and atomicity -for multiple database operations. The transaction system uses two-phase -locking and write-ahead logging protocols to ensure that database -operations may be undone or redone in the case of application or system -failure. Applications may use Berkeley DB transaction and logging subsystems -to protect their own data structures and operations from application or -system failure.</dd> + <dd> + The transaction and logging systems provide + recoverability and atomicity for multiple database + operations. The transaction system uses two-phase + locking and write-ahead logging protocols to ensure + that database operations may be undone or redone in + the case of application or system failure. + Applications may use Berkeley DB transaction and + logging subsystems to protect their own data + structures and operations from application or system + failure. + </dd> <dt> <span class="term">Locking:</span> </dt> - <dd>The locking system provides multiple reader or single writer access to -objects. The Berkeley DB access methods use the locking system to acquire -the right to read or write database pages. Applications may use the -Berkeley DB locking subsystem to support their own locking needs.</dd> + <dd> + The locking system provides multiple reader or + single writer access to objects. The Berkeley DB + access methods use the locking system to acquire the + right to read or write database pages. Applications + may use the Berkeley DB locking subsystem to support + their own locking needs. + </dd> </dl> </div> - <p>By combining the page cache, transaction, locking, and logging systems, -Berkeley DB provides the same services found in much larger, more complex and -more expensive database systems. Berkeley DB supports multiple simultaneous -readers and writers and guarantees that all changes are recoverable, even -in the case of a catastrophic hardware failure during a database update.</p> - <p>Developers may select some or all of the core database services for any -access method or database. Therefore, it is possible to choose the -appropriate storage structure and the right degrees of concurrency and -recoverability for any application. In addition, some of the subsystems -(for example, the Locking subsystem) can be called separately from the -Berkeley DB access method. As a result, developers can integrate non-database -objects into their transactional applications using Berkeley DB.</p> + <p> + By combining the page cache, transaction, locking, and + logging systems, Berkeley DB provides the same services found + in much larger, more complex and more expensive database + systems. Berkeley DB supports multiple simultaneous readers + and writers and guarantees that all changes are recoverable, + even in the case of a catastrophic hardware failure during a + database update. + </p> + <p> + Developers may select some or all of the core database + services for any access method or database. Therefore, it is + possible to choose the appropriate storage structure and the + right degrees of concurrency and recoverability for any + application. In addition, some of the subsystems (for example, + the Locking subsystem) can be called separately from the + Berkeley DB access method. As a result, developers can + integrate non-database objects into their transactional + applications using Berkeley DB. + </p> </div> <div class="navfooter"> <hr /> @@ -97,7 +118,8 @@ objects into their transactional applications using Berkeley DB.</p> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> What does the Berkeley DB distribution include?</td> + <td width="40%" align="right" valign="top"> What does the Berkeley DB + distribution include?</td> </tr> </table> </div> |