summaryrefslogtreecommitdiff
path: root/docs/programmer_reference/dumpload.html
diff options
context:
space:
mode:
authorLorry Tar Creator <lorry-tar-importer@baserock.org>2015-02-17 17:25:57 +0000
committer <>2015-03-17 16:26:24 +0000
commit780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch)
tree598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/dumpload.html
parent7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff)
downloadberkeleydb-master.tar.gz
Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz.HEADdb-6.1.23master
Diffstat (limited to 'docs/programmer_reference/dumpload.html')
-rw-r--r--docs/programmer_reference/dumpload.html58
1 files changed, 45 insertions, 13 deletions
diff --git a/docs/programmer_reference/dumpload.html b/docs/programmer_reference/dumpload.html
index 5489304e..5597a5a9 100644
--- a/docs/programmer_reference/dumpload.html
+++ b/docs/programmer_reference/dumpload.html
@@ -14,13 +14,12 @@
<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">Chapter 23. 
- Dumping and Reloading Databases
- </th>
+ <th colspan="3" align="center">Chapter 23.  Dumping and Reloading Databases
+ </th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="ext_php.html">Prev</a> </td>
@@ -34,9 +33,8 @@
<div class="titlepage">
<div>
<div>
- <h2 class="title"><a id="dumpload"></a>Chapter 23. 
- Dumping and Reloading Databases
- </h2>
+ <h2 class="title"><a id="dumpload"></a>Chapter 23.  Dumping and Reloading Databases
+ </h2>
</div>
</div>
</div>
@@ -70,12 +68,46 @@
</div>
</div>
</div>
- <p>There are three utilities used for dumping and loading Berkeley DB databases: the <a href="../api_reference/C/db_dump.html" class="olink">db_dump</a> utility, the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility and the <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility.</p>
- <p>The <a href="../api_reference/C/db_dump.html" class="olink">db_dump</a> utility and the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility dump Berkeley DB databases into a flat-text representation of the data that can be read by <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility. The only difference between them is that the <a href="../api_reference/C/db_dump.html" class="olink">db_dump</a> utility reads Berkeley DB version 2 and greater database formats, whereas the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility reads Berkeley DB version 1.85 and 1.86 database formats.</p>
- <p>The <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility reads either the output format used by the dump utilities or (optionally) a flat-text representation created using other tools, and stores it into a Berkeley DB database.</p>
- <p>Dumping and reloading Hash databases that use user-defined hash functions will result in new databases that use the default hash function. Although using the default hash function may not be optimal for the new database, it will continue to work correctly.</p>
- <p>Dumping and reloading Btree databases that use user-defined prefix or comparison functions will result in new databases that use the default prefix and comparison functions. In this case, it is quite likely that applications will be unable to retrieve records, and it is possible that the load process itself will fail.</p>
- <p>The only available workaround for either Hash or Btree databases is to modify the sources for the <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility to load the database using the correct hash, prefix, and comparison functions.</p>
+ <p>
+ There are three utilities used for dumping and loading
+ Berkeley DB databases: the <a href="../api_reference/C/db_dump.html" class="olink">db_dump</a> utility, the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility and the
+ <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility.
+ </p>
+ <p>
+ The <a href="../api_reference/C/db_dump.html" class="olink">db_dump</a> utility and the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility dump Berkeley DB
+ databases into a flat-text representation of the data that can
+ be read by <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility. The only difference between them is that
+ the <a href="../api_reference/C/db_dump.html" class="olink">db_dump</a> utility reads Berkeley DB version 2 and greater database
+ formats, whereas the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility reads Berkeley DB version
+ 1.85 and 1.86 database formats.
+ </p>
+ <p>
+ The <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility reads either the output format used by the
+ dump utilities or (optionally) a flat-text representation
+ created using other tools, and stores it into a Berkeley DB
+ database.
+ </p>
+ <p>
+ Dumping and reloading Hash databases that use user-defined
+ hash functions will result in new databases that use the
+ default hash function. Although using the default hash
+ function may not be optimal for the new database, it will
+ continue to work correctly.
+ </p>
+ <p>
+ Dumping and reloading Btree databases that use user-defined
+ prefix or comparison functions will result in new databases
+ that use the default prefix and comparison functions. In this
+ case, it is quite likely that applications will be unable to
+ retrieve records, and it is possible that the load process
+ itself will fail.
+ </p>
+ <p>
+ The only available workaround for either Hash or Btree
+ databases is to modify the sources for the <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility to load
+ the database using the correct hash, prefix, and comparison
+ functions.
+ </p>
</div>
</div>
<div class="navfooter">