diff options
Diffstat (limited to 'docs/programmer_reference/am_sync.html')
| -rw-r--r-- | docs/programmer_reference/am_sync.html | 56 |
1 files changed, 34 insertions, 22 deletions
diff --git a/docs/programmer_reference/am_sync.html b/docs/programmer_reference/am_sync.html index 12ac2310..366cdbfb 100644 --- a/docs/programmer_reference/am_sync.html +++ b/docs/programmer_reference/am_sync.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="am_verify.html">Prev</a> </td> - <th width="60%" align="center">Chapter 3. - Access Method Operations - </th> + <th width="60%" align="center">Chapter 3. Access Method Operations </th> <td width="20%" align="right"> <a accesskey="n" href="am_close.html">Next</a></td> </tr> </table> @@ -38,26 +36,39 @@ </div> </div> </div> - <p>The <a href="../api_reference/C/dbsync.html" class="olink">DB->sync()</a> method flushes all modified records from the database -cache to disk.</p> <p> - <span class="bold"> - <strong>It is important to understand that flushing cached information -to disk only minimizes the window of opportunity for corrupted data, it -does not eliminate the possibility.</strong> - </span> - </p> - <p>While unlikely, it is possible for database corruption to happen if a -system or application crash occurs while writing data to the database. To -ensure that database corruption never occurs, applications must either:</p> + The <a href="../api_reference/C/dbsync.html" class="olink">DB->sync()</a> method flushes all modified records from the + database cache to disk. + </p> + <p> + <span class="bold"><strong>It is important to understand that + flushing cached information to disk only minimizes the + window of opportunity for corrupted data, it does not + eliminate the possibility.</strong></span> + </p> + <p> + While unlikely, it is possible for database corruption to + happen if a system or application crash occurs while writing + data to the database. To ensure that database corruption never + occurs, applications must either: + </p> <div class="itemizedlist"> <ul type="disc"> - <li>Use transactions and logging with automatic recovery.</li> - <li>Use logging and application-specific recovery.</li> - <li>Edit a copy of the database, and, once all applications -using the database have successfully called <a href="../api_reference/C/dbclose.html" class="olink">DB->close()</a>, use -system operations (for example, the POSIX rename system call) to -atomically replace the original database with the updated copy.</li> + <li> + Use transactions and logging with automatic + recovery. + </li> + <li> + Use logging and application-specific + recovery. + </li> + <li> + Edit a copy of the database, and, once all + applications using the database have successfully called + <a href="../api_reference/C/dbclose.html" class="olink">DB->close()</a>, use system operations (for example, the POSIX + rename system call) to atomically replace the original + database with the updated copy. + </li> </ul> </div> </div> @@ -72,7 +83,8 @@ atomically replace the original database with the updated copy.</li> <td width="40%" align="right"> <a accesskey="n" href="am_close.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Database verification and salvage </td> + <td width="40%" align="left" valign="top">Database verification and + salvage </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> |