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/installation | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'docs/installation')
134 files changed, 13097 insertions, 5078 deletions
diff --git a/docs/installation/BDB_Installation.pdf b/docs/installation/BDB_Installation.pdf Binary files differindex 895b2443..1c16c80e 100644 --- a/docs/installation/BDB_Installation.pdf +++ b/docs/installation/BDB_Installation.pdf diff --git a/docs/installation/bdb_sql_encryption.html b/docs/installation/bdb_sql_encryption.html new file mode 100644 index 00000000..63c7adde --- /dev/null +++ b/docs/installation/bdb_sql_encryption.html @@ -0,0 +1,67 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>UNIX/POSIX SQL Encryption Default</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="sql_logbuf.html" title="New Berkeley DB SQL API Pragma" /> + <link rel="next" href="seq_datatype.html" title="Sequence Datatype Changes" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">UNIX/POSIX SQL Encryption Default</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="sql_logbuf.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="seq_datatype.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="bdb_sql_encryption"></a>UNIX/POSIX SQL Encryption Default</h2> + </div> + </div> + </div> + <p> + Encryption is no longer enabled by default when + building the SQL interface, either with or without the + JDBC driver, on UNIX/POSIX platforms. To enable + encryption, use the <code class="literal">configure</code> argument + <code class="literal">--with-cryptography=yes</code>. + </p> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="sql_logbuf.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="seq_datatype.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">New Berkeley DB SQL API Pragma </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Sequence Datatype Changes</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/bdbsql_ha_more_options.html b/docs/installation/bdbsql_ha_more_options.html new file mode 100644 index 00000000..d6105559 --- /dev/null +++ b/docs/installation/bdbsql_ha_more_options.html @@ -0,0 +1,117 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Enhanced BDB SQL Replication Options</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="rep_views.html" title="Replication Views" /> + <link rel="next" href="rep_auto_takeover.html" title="Replication Manager Automatic Takeover" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Enhanced BDB SQL Replication Options</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="rep_views.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="rep_auto_takeover.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="bdbsql_ha_more_options"></a>Enhanced BDB SQL Replication Options</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="bdbsql_ha_more_options.html#idp1049920">New Pragmas</a> + </span> + </dt> + </dl> + </div> + <p> + Berkeley DB SQL replicated applications now support + multiprocess access. Also, there are several new + replication pragmas. The + <code class="literal">replication_ack_policy</code>, + <code class="literal">replication_ack_timeout</code> and + <code class="literal">replication_priority</code> pragmas + provide ways to configure a site's acknowledgement + criteria and election priority. The other new pragmas + provide additional information about the current state of + the replication group or the local site. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1049920"></a>New Pragmas</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <code class="literal">PRAGMA + replication_ack_policy[=all|all_available|none|one|quorum]</code> + </li> + <li> + <code class="literal">PRAGMA + replication_ack_timeout[=n]</code> + </li> + <li> + <code class="literal">PRAGMA replication_priority[=n]</code> + </li> + <li> + <code class="literal">PRAGMA replication_get_master</code> + </li> + <li> + <code class="literal">PRAGMA replication_num_sites</code> + </li> + <li> + <code class="literal">PRAGMA replication_perm_failed</code> + </li> + <li> + <code class="literal">PRAGMA replication_site_status</code> + </li> + </ul> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="rep_views.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="rep_auto_takeover.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Replication Views </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Replication Manager Automatic Takeover</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/blob-support.html b/docs/installation/blob-support.html new file mode 100644 index 00000000..8c507e66 --- /dev/null +++ b/docs/installation/blob-support.html @@ -0,0 +1,229 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Binary Large Object Support</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="next" href="rep_views.html" title="Replication Views" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Binary Large Object Support</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="upgrade_60_toc.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="rep_views.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="blob-support"></a>Binary Large Object Support</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp865296">New Functions</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp998896">New Flags Accepted by Blob Streaming Interfaces</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp1063832">Other New Flags</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp1064912">New Pragma</a> + </span> + </dt> + </dl> + </div> + <p> + Berkeley DB now has improved facilities for managing + binary large objects (blobs). There is a new streaming + interface to efficiently read and write blobs. There are + new configuration interfaces to set an optional size + threshold above which an object is created as a blob, and + to manage the location of blob storage. A new SQL pragma + enables SQL users to set a similar optional size threshold + above which rows are stored internally in Berkeley DB as + blobs. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp865296"></a>New Functions</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <code class="literal"> + <a href="../api_reference/C/dbstream.html" class="olink">DBC->db_stream()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/dbstream_close.html" class="olink">DB_STREAM->close()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/dbstream_read.html" class="olink">DB_STREAM->read()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/dbstream_size.html" class="olink">DB_STREAM->size()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/dbstream_write.html" class="olink">DB_STREAM->write()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/envset_blob_threshold.html" class="olink">DB_ENV->set_blob_threshold()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/envget_blob_threshold.html" class="olink">DB_ENV->get_blob_threshold()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/set_blob_threshold.html" class="olink">DB->set_blob_threshold()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/get_blob_threshold.html" class="olink">DB->get_blob_threshold()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/envset_blob_dir.html" class="olink">DB_ENV->set_blob_dir()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/envget_blob_dir.html" class="olink">DB_ENV->get_blob_dir()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/set_blob_dir.html" class="olink">DB->set_blob_dir()</a> + </code> + </li> + <li> + <code class="literal"> + <a href="../api_reference/C/get_blob_dir.html" class="olink">DB->get_blob_dir()</a> + </code> + </li> + </ul> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp998896"></a>New Flags Accepted by Blob Streaming Interfaces</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li><a href="../api_reference/C/dbstream.html#blobs_DB_STREAM_READ" class="olink">DB_STREAM_READ</a> — accepted by + <a href="../api_reference/C/dbstream.html" class="olink">DBC->db_stream()</a></li> + <li><a href="../api_reference/C/dbstream.html#blobs_DB_STREAM_WRITE" class="olink">DB_STREAM_WRITE</a> — accepted by + <a href="../api_reference/C/dbstream.html" class="olink">DBC->db_stream()</a></li> + <li><a href="../api_reference/C/dbstream.html#blobs_DB_STREAM_SYNC_WRITE" class="olink">DB_STREAM_SYNC_WRITE</a> — accepted by + <a href="../api_reference/C/dbstream.html" class="olink">DBC->db_stream()</a> and <a href="../api_reference/C/dbstream_write.html" class="olink">DB_STREAM->write()</a></li> + </ul> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1063832"></a>Other New Flags</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li><a href="../api_reference/C/dbt.html#dbt_DB_DBT_BLOB" class="olink">DB_DBT_BLOB</a> — Used on the data DBT + accepted by <a href="../api_reference/C/dbput.html" class="olink">DB->put()</a> and <a href="../api_reference/C/dbcput.html" class="olink">DBC->put()</a> to indicate that + the DBT is a blob. + </li> + <li><a href="../api_reference/C/envlog_set_config.html#log_set_config_DB_LOG_BLOB" class="olink">DB_LOG_BLOB</a> — Accepted by + <a href="../api_reference/C/envlog_set_config.html" class="olink">DB_ENV->log_set_config()</a> and <a href="../api_reference/C/envlog_get_config.html" class="olink">DB_ENV->log_get_config()</a> to + indicate full logging of blobs. + </li> + </ul> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1064912"></a>New Pragma</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <code class="literal">PRAGMA large_record_opt[=n]</code> + </li> + </ul> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="upgrade_60_toc.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="rep_views.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Replication Views</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/blobdb_format.html b/docs/installation/blobdb_format.html new file mode 100644 index 00000000..1cf6983c --- /dev/null +++ b/docs/installation/blobdb_format.html @@ -0,0 +1,69 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>New Database Format for BLOBs</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="prev" href="repmgr_inqueue.html" title="Replication Manager Incoming Queue Size Limit" /> + <link rel="next" href="sqlite_ver61.html" title="Updated SQLite Version" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">New Database Format for BLOBs</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="repmgr_inqueue.html">Prev</a> </td> + <th width="60%" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + <td width="20%" align="right"> <a accesskey="n" href="sqlite_ver61.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="blobdb_format"></a>New Database Format for BLOBs</h2> + </div> + </div> + </div> + <p> + The database record format for databases containing BLOBs was + changed in 12.1.6.0.30. Any database from version 12.1.6.0.21 or + earlier that contains BLOBs must be upgraded before it can be + opened by this or any later version of Berkeley DB. Databases + from version 12.1.6.0.30 or later that contain BLOBs and databases + without BLOBs do not require upgrading. + </p> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="repmgr_inqueue.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_61_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="sqlite_ver61.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Replication Manager Incoming Queue + Size Limit </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Updated SQLite Version</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/build_android_adfmobile.html b/docs/installation/build_android_adfmobile.html new file mode 100644 index 00000000..7f5ffcf5 --- /dev/null +++ b/docs/installation/build_android_adfmobile.html @@ -0,0 +1,275 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Using the JDBC Driver in ADF Mobile for Android</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="build_android_intro.html" title="Chapter 4. Building Berkeley DB for Android" /> + <link rel="prev" href="build_android_config.html" title="Android Configuration Options" /> + <link rel="next" href="build_win.html" title="Chapter 5. Building Berkeley DB for Windows" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Using the JDBC Driver in ADF Mobile for Android</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="build_android_config.html">Prev</a> </td> + <th width="60%" align="center">Chapter 4. Building Berkeley DB for + Android</th> + <td width="20%" align="right"> <a accesskey="n" href="build_win.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="build_android_adfmobile"></a>Using the JDBC Driver in ADF Mobile for Android</h2> + </div> + </div> + </div> + <p> + This section describes how to build and use BDB JDBC + driver for Android in ADF Mobile. + </p> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Setup the ADF Mobile environments: + </p> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <p> + ADF Business Components: 11.1.2.4.39.64.36.1 + </p> + </li> + <li> + <p> + ADF Mobile Framework: 11.1.2.4.39.64 + </p> + </li> + <li> + <p> + JDeveloper: 11g Release 2(11.1.2.4.0) + </p> + </li> + </ul> + </div> + </li> + <li> + <p> + Prepare the building environment. + </p> + <div class="orderedlist"> + <ol type="a"> + <li> + <p> + Download the OJEC1.1.1 headless package from + </p> + <p> + <a class="ulink" href=" http://www.oracle.com/technetwork/java/embedded/downloads/javame/index.html#2" target="_top"> http://www.oracle.com/technetwork/java/embedded/downloads/javame/index.html#2</a> + </p> + <p> + Unzip it and move btclasses.zip from OJEC1.1.1_HOME to OJEC1.1.1_HOME/lib. + </p> + </li> + <li> + <p> + Modify BDB_HOME/lang/sql/jdbc/config.ojec11 as follows: + </p> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <p> + Specify OJEC_HOME with the location where OJEC1.1.1 is unzipped to + </p> + </li> + <li> + <p> + Specify JDBCSQLITE_HOME with BDB_HOME/build_unix/jdbc + </p> + </li> + <li> + <p> + Remove foundation.jar from BOOT_CLASSPATH + </p> + </li> + <li> + Remove the last line which is "./configure" + </li> + </ul> + </div> + </li> + <li> + <p> + Export the variables in config.ojec11 to the environment using an appropriate + shell command for example, ". BDB_HOME/lang/sql/jdbc/config.ojec11". + </p> + </li> + </ol> + </div> + </li> + <li> + <p> + Build the Android JDBC driver. + </p> + <p> + For instructions on how to build Android JDBC driver, + see <a class="xref" href="build_android_jdbc.html" title="Building the Android JDBC Driver">Building the Android JDBC + Driver</a>. + </p> + <p> + Ensure that the JDBC driver includes SQLite/JDBC0 classes by "jar tf sqlite.jar". + </p> + </li> + <li> + <p> + Apply Android JDBC in ADF Mobile. + </p> + <div class="orderedlist"> + <ol type="a"> + <li> + <p> + Download the ADF Mobile in JDeveloper by selecting + Help -> Check for Updates. The ADF Mobile extension will be downloaded in + jdev_install/jdeveloper/jdev/extensions/oracle.adf.mobile. + </p> + </li> + <li> + <p> + In JDeveloper, open the HR sample application in + jdev_install/jdeveloper/jdev/extensions/oracle.adf.mobile/Samples/HR. + </p> + </li> + <li> + <p> + Add BDB Android JDBC to application libraries and classpath. + </p> + </li> + <li> + <p> + Replace the JDBC driver in ADF Mobile framework as follows. + </p> + <pre class="programlisting"> +$ cd jdev_install/jdeveloper/jdev/extensions/oracle.adf.mobile +/Android +$ unzip Oracle_ADFmf_Framework.zip +... +$ cp <db>/build_unix/jdbc/sqlite.jar ./framework/Android/build/ +java_res_<release and debug>/assets/storage/jvm/lib/ +$ cp <db>/build_android/jdbc/libs/armeabi/liboracle-jdbc.so . +/framework/Android/build/java_res_<release and debug>/assets/storage +/jvm/lib/ +$ zip -9 -r Oracle_ADFmf_Framework.zip framework +... +$ rm -fr framework +</pre> + </li> + </ol> + </div> + </li> + <li> + <p> + Modify the sample application. + </p> + <div class="orderedlist"> + <ol type="a"> + <li> + <p> + Migrate the database file from SQLite to BDB by the following commands: + </p> + <pre class="programlisting"> +$ cd HR_SAMPLE/.adf/META-INF +$ mv HR.db HR.db.orig +$ mv hr.sql hr.sql.orig +$ vi hr.sql (Remove all lines with "COMMIT" and "REM") $ +BDB_HOME/build_unix/dbsql HR.db +.read hr.sql +.exit +</pre> + </li> + <li> + <p> + Modify LifeCycleListernImpl.start() method by replacing the try + catch block of getting a connection and executing the query with copyDB(). + </p> + </li> + </ol> + </div> + </li> + <li> + <p> + Run the sample application. + </p> + <div class="orderedlist"> + <ol type="a"> + <li> + <p> + Configure the ADF Mobile preferences for Android. + Select Tools -> Preferences -> ADF Mobile -> Platforms -> Android. + Specify the locations of Android SDK, Android platform, and the + keystore in the Release mode which is used to sign on the application. + </p> + </li> + <li> + <p> + Create a deployment profile. Select Application -> Deploy -> New Deployment Profile. + Choose ADF Mobile for Android as profile type. In the form of deployment profile + properties, choose Release Mode. + </p> + </li> + <li> + <p> + Launch the Android SDK Manager and start the AVD emulator. + </p> + </li> + <li> + <p> + Deploy the application by selecting Application -> deploy -> + (the_just_created_deployment_profile). Before deployment, ensure that the folder HR_SAMPLE/deploy is removed. + </p> + </li> + <li> + <p> + Run the application by clicking the application icon in the emulator. + </p> + </li> + </ol> + </div> + </li> + </ol> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="build_android_config.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="build_android_intro.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="build_win.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Android Configuration + Options </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Chapter 5. Building Berkeley DB for Windows </td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/build_android_config.html b/docs/installation/build_android_config.html index 05fac582..778656c0 100644 --- a/docs/installation/build_android_config.html +++ b/docs/installation/build_android_config.html @@ -9,21 +9,23 @@ <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> <link rel="up" href="build_android_intro.html" title="Chapter 4. Building Berkeley DB for Android" /> <link rel="prev" href="build_android_jdbc.html" title="Building the Android JDBC Driver" /> - <link rel="next" href="build_win.html" title="Chapter 5. Building Berkeley DB for Windows" /> + <link rel="next" href="build_android_adfmobile.html" title="Using the JDBC Driver in ADF Mobile for Android" /> </head> <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">Android Configuration Options</th> + <th colspan="3" align="center">Android Configuration + Options</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_android_jdbc.html">Prev</a> </td> - <th width="60%" align="center">Chapter 4. Building Berkeley DB for Android</th> - <td width="20%" align="right"> <a accesskey="n" href="build_win.html">Next</a></td> + <th width="60%" align="center">Chapter 4. Building Berkeley DB for + Android</th> + <td width="20%" align="right"> <a accesskey="n" href="build_android_adfmobile.html">Next</a></td> </tr> </table> <hr /> @@ -32,67 +34,93 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_android_config"></a>Android Configuration Options</h2> + <h2 class="title" style="clear: both"><a id="build_android_config"></a>Android Configuration + Options</h2> </div> </div> </div> - <p>There are several configuration options you can specify in <code class="literal">LOCAL_CFLAGS</code> located in the <code class="literal">Android.mk</code> file. </p> + <p> + There are several configuration options you can specify in + <code class="literal">LOCAL_CFLAGS</code> located in the + <code class="literal">Android.mk</code> file. + </p> <div class="itemizedlist"> <ul type="disc"> <li> + <p> + BDBSQL_CONVERT_SQLITE + </p> <p> - BDBSQL_CONVERT_SQLITE - </p> - <p> - This option enables to convert SQLite database to BDB SQL database format. See <a class="xref" href="build_android_intro.html#build_android_migrate" title="Migrating from SQLite to Berkeley DB">Migrating from SQLite to Berkeley DB</a> - for more information. - </p> + This option enables to convert SQLite database to + BDB SQL database format. See <a class="xref" href="build_android_intro.html#build_android_migrate" title="Migrating from SQLite to Berkeley DB">Migrating from SQLite to + Berkeley DB</a> for more + information. + </p> </li> <li> <p> - BDBSQL_SHARE_PRIVATE - </p> - <p> - This flag is enabled by default and keeps all the region files in - memory instead of the disk. - This flag also implements database-level locking. - </p> + BDBSQL_SHARE_PRIVATE + </p> + <p> + This flag is enabled by default and keeps all the + region files in memory instead of the disk. This flag + also implements database-level locking. + </p> </li> <li> <p> - SQLITE_DEFAULT_CACHE_SIZE - </p> + SQLITE_DEFAULT_CACHE_SIZE + </p> + <p> + SQLite provides an in-memory cache which you size + according to the maximum number of database pages that + you want to hold in memory at any given time. See + <a class="xref" href="build_unix_sql.html#config_sql" title="Changing Compile Options">Changing Compile Options</a>. + </p> + </li> + <li> <p> - SQLite provides an in-memory cache which you size according to the maximum number of - database pages that you want to hold in memory at any given time. - See <a class="xref" href="build_unix_sql.html#config_sql" title="Changing Compile Options">Changing Compile Options</a>. - </p> + SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT + </p> + <p> For SQLite, this pragma identifies the maximum size + that the journal file is allowed to be. Berkeley DB + does not have a journal file, but it writes and uses + log files. A new log file is created when the current + log file has reached the defined maximum size. This + flag defines the maximum size for a log file. Default + value is 10 MB for Berkeley DB SQL interface. </p> </li> <li> <p> - SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT - </p> + SQLITE_HAS_CODEC + </p> <p> - For SQLite, this pragma identifies the maximum size that the journal file is allowed - to be. Berkeley DB does not have a journal file, but it writes and uses log files. A new log file is - created when the current log file has reached the defined maximum size. - This flag defines this maximum size for a log file. Default value is 10 MB for Berkeley DB SQL interface. - </p> + Causes the Berkeley DB SQL interface to be built + with encryption support. See <a href="../bdb-sql/sql_encryption.html" class="olink">SQL Encryption</a> in the + <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide for + usage details. + </p> </li> </ul> </div> <p> -Hard-coded numbers in the build can be adjusted using the following SQLite PRAGMA commands: </p> + Hard-coded numbers in the build can be adjusted using the + following SQLite PRAGMA commands: + </p> <div class="itemizedlist"> <ul type="disc"> - <li>PRAGMA cache_size</li> - <li>PRAGMA journal_size_limit</li> + <li> + PRAGMA cache_size + </li> + <li> + PRAGMA journal_size_limit + </li> </ul> </div> <p> -You can configure most aspects of your Berkeley DB environment by using the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file. - -</p> + You can configure most aspects of your Berkeley DB + environment by using the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file. + </p> </div> <div class="navfooter"> <hr /> @@ -102,16 +130,15 @@ You can configure most aspects of your Berkeley DB environment by using the <a h <td width="20%" align="center"> <a accesskey="u" href="build_android_intro.html">Up</a> </td> - <td width="40%" align="right"> <a accesskey="n" href="build_win.html">Next</a></td> + <td width="40%" align="right"> <a accesskey="n" href="build_android_adfmobile.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Building the Android JDBC Driver </td> + <td width="40%" align="left" valign="top">Building the Android JDBC + Driver </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 5. - Building Berkeley DB for Windows - </td> + <td width="40%" align="right" valign="top"> Using the JDBC Driver in ADF Mobile for Android</td> </tr> </table> </div> diff --git a/docs/installation/build_android_intro.html b/docs/installation/build_android_intro.html index d8586dc1..13ff8fdf 100644 --- a/docs/installation/build_android_intro.html +++ b/docs/installation/build_android_intro.html @@ -14,11 +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 4. Building Berkeley DB for Android</th> + <th colspan="3" align="center">Chapter 4. Building Berkeley DB for + Android</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="debug_printlog.html">Prev</a> </td> @@ -32,7 +33,8 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="build_android_intro"></a>Chapter 4. Building Berkeley DB for Android</h2> + <h2 class="title"><a id="build_android_intro"></a>Chapter 4. Building Berkeley DB for + Android</h2> </div> </div> </div> @@ -43,51 +45,63 @@ <dl> <dt> <span class="sect1"> - <a href="build_android_intro.html#build_android">Building the Drop-In Replacement for Android</a> + <a href="build_android_intro.html#build_android">Building the Drop-In Replacement + for Android</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> - <a href="build_android_intro.html#build_android_migrate">Migrating from SQLite to Berkeley DB</a> + <a href="build_android_intro.html#build_android_migrate">Migrating from SQLite to + Berkeley DB</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> - <a href="build_android_jdbc.html">Building the Android JDBC Driver</a> + <a href="build_android_jdbc.html">Building the Android JDBC + Driver</a> </span> </dt> <dt> <span class="sect1"> - <a href="build_android_config.html">Android Configuration Options</a> + <a href="build_android_config.html">Android Configuration + Options</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="build_android_adfmobile.html">Using the JDBC Driver in ADF Mobile for Android</a> </span> </dt> </dl> </div> <p> - Berkeley DB provides support for the Android platform enabling you to - develop and deploy a wide range of mobile applications and services. - Android provides SQLite as the default database for developing - applications that need database support. Berkeley DB SQL API is fully - compatible with SQLite and can be used as a replacement. The - <code class="literal">build_android</code> directory in the Berkeley DB - distribution contains a makefile, <code class="literal">Android.mk</code>, for - building a drop-in replacement for SQLite. + Berkeley DB provides support for the Android platform + enabling you to develop and deploy a wide range of mobile + applications and services. Android provides SQLite as the + default database for developing applications that need + database support. Berkeley DB SQL API is fully compatible with + SQLite and can be used as a replacement. The + <code class="literal">build_android</code> directory in the Berkeley + DB distribution contains a makefile, + <code class="literal">Android.mk</code>, for building a drop-in + replacement for SQLite. </p> <p> - Oracle offers two different solutions for building the - BDB SQL API for Android. The first creates a library - that can be used as a drop-in replacement for SQLite on - Android. The second creates a JDBC driver for Android. + Oracle offers two different solutions for building the BDB + SQL API for Android. The first creates a library that can be + used as a drop-in replacement for SQLite on Android. The + second creates a JDBC driver for Android. </p> <div class="sect1" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_android"></a>Building the Drop-In Replacement for Android</h2> + <h2 class="title" style="clear: both"><a id="build_android"></a>Building the Drop-In Replacement + for Android</h2> </div> </div> </div> @@ -95,54 +109,68 @@ <dl> <dt> <span class="sect2"> - <a href="build_android_intro.html#build_android_migrate">Migrating from SQLite to Berkeley DB</a> + <a href="build_android_intro.html#build_android_migrate">Migrating from SQLite to + Berkeley DB</a> </span> </dt> </dl> </div> - <p> - This section describes how to build a library that can be used as a - drop-in replacement for SQLite on Android. + <p> + This section describes how to build a library that can be + used as a drop-in replacement for SQLite on Android. </p> + <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> + <h3 class="title">Note</h3> + <p> + A drop in replacement refers to replacing all instances + of SQLite in an Android OS build with Berkeley DB SQL. All + databases will be created in the Berkeley DB SQL format + including any created with the Java SQLite.* API. This + solution requires that users re-compile a custom Android + OS image (it is only relevant for platform/device + vendors). + </p> + </div> <div class="orderedlist"> <ol type="1"> <li> - <p> - Download and compile the Android source tree. + <p> + Download and compile the Android source tree. </p> - <p> - The compiling process takes time but is a one time activity. - For information on downloading and compiling the Android source - code, see - <a class="ulink" href="http://source.android.com/source/download.html" target="_top">http://source.android.com/source/download.html</a>. + <p> + The compiling process takes time but is a one time + activity. For information on downloading and compiling + the Android source code, see <a class="ulink" href="http://source.android.com/source/download.html" target="_top">http://source.android.com/source/download.html</a>. </p> </li> <li> <p> - Copy the Berkeley DB code into the Android build tree. + Copy the Berkeley DB code into the Android build + tree. </p> <pre class="programlisting">$ cd <root>/external/sqlite/dist $ tar zxf ${DB_PATH} </pre> - <p> - where <root> is the root of the Android source tree and - ${DB_PATH} is the path where you saved the - <code class="literal">db-xx.tar.gz</code> version of the Berkeley DB - distribution. + <p> + where <root> is the root of the Android + source tree and ${DB_PATH} is the path where you saved + the <code class="literal">db-xx.tar.gz</code> version of the + Berkeley DB distribution. </p> </li> <li> <p> - Update the Android build file to identify Berkeley DB. + Update the Android build file to identify Berkeley + DB. </p> - <p> - Replace the <code class="literal">Android.mk</code> file with the one - from the Berkeley DB source tree by doing the - following: + <p> + Replace the <code class="literal">Android.mk</code> file with + the one from the Berkeley DB source tree by doing the + following: </p> <pre class="programlisting">$ cd <root>/external/sqlite/dist $ mv Android.mk Android.mk.sqlite $ cp ${DB_INSTALL}/build_android/Android.mk ./ </pre> - <p> + <p> where ${DB_INSTALL} is the directory into which you installed the Berkeley DB library. </p> @@ -151,26 +179,27 @@ $ cp ${DB_INSTALL}/build_android/Android.mk ./ </pre> <p> Tuning parameters. </p> - <p> - The configuration options for performance tuning can be - added/edited in the <code class="literal">Android.mk</code> file by - modifying <code class="literal">LOCAL_CFLAGS</code> located in the - <code class="literal">build libsqlite replacement</code> section. For - more information, see - <a class="xref" href="build_android_config.html" title="Android Configuration Options">Android Configuration Options</a>. + <p> + The configuration options for performance tuning + can be added/edited in the + <code class="literal">Android.mk</code> file by modifying + <code class="literal">LOCAL_CFLAGS</code> located in the + <code class="literal">build libsqlite replacement</code> + section. For more information, see <a class="xref" href="build_android_config.html" title="Android Configuration Options">Android Configuration + Options</a>. </p> - <p> - It is also possible to change these settings using PRAGMA - commands or through the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file. + <p> + It is also possible to change these settings using + PRAGMA commands or through the <a href="../api_reference/C/configuration_reference.html" class="olink">DB_CONFIG</a> file. </p> </li> <li> - <p> - Build the new Android image. + <p> + Build the new Android image. </p> - <p> - To build the Android image with Berkeley DB SQL included, - do the following: + <p> + To build the Android image with Berkeley DB SQL + included, do the following: </p> <pre class="programlisting">$ cd <root> $ . build/envsetup.sh @@ -180,7 +209,7 @@ $ make snod </pre> <p> You can locate the new image in - <code class="literal"><root>/out/target/product/generic</code>. + <code class="literal"><root>/out/target/product/generic</code>. </p> </li> </ol> @@ -189,23 +218,24 @@ $ make snod <div class="titlepage"> <div> <div> - <h3 class="title"><a id="build_android_migrate"></a>Migrating from SQLite to Berkeley DB</h3> + <h3 class="title"><a id="build_android_migrate"></a>Migrating from SQLite to + Berkeley DB</h3> </div> </div> </div> - <p> - This section describes how to enable automatic conversion of SQLite - format databases to Berkeley DB SQL when they are opened. To do - this, you must first make sure that the - <code class="literal">-DBDBSQL_CONVERT_SQLITE</code> option is added to - <code class="literal">LOCAL_CFLAGS</code> when you configure your Berkeley DB - database build. + <p> + This section describes how to enable automatic conversion + of SQLite format databases to Berkeley DB SQL when they are + opened. To do this, you must first make sure that the + <code class="literal">-DBDBSQL_CONVERT_SQLITE</code> option is added + to <code class="literal">LOCAL_CFLAGS</code> when you configure your + Berkeley DB database build. </p> <div class="orderedlist"> <ol type="1"> <li> <p> - Build a static SQLite shell for Android platform. + Build a static SQLite shell for Android platform. </p> <p> Create a script, build_sqlite3_shell.sh, in the @@ -244,44 +274,45 @@ ${CC} -DANDROID -DOS_ANDROID --sysroot="${SYSROOT}" -mandroid \ -fPIC ${LDFLAGS} ${CFLAGS} \ sqlite3.c shell.c -o sqlite3orig </pre> - <p> - Ensure you adjust the variables as per your actual Android - environment. This script is suited for Android 2.2. + <p> + Ensure you adjust the variables as per your actual + Android environment. This script is suited for Android + 2.2. </p> </li> <li> <p> - Execute the build_sqlite3_shell.sh script and to get the - static sqlite3 shell utility - sqlite3orig. + Execute the build_sqlite3_shell.sh script and to + get the static sqlite3 shell utility - sqlite3orig. </p> </li> <li> - <p> - Change the system image file. + <p> + Change the system image file. </p> <p> - Use the <code class="literal">xyaffs2</code> utiltiy to decompress - the <code class="literal">system.img</code> and get the directory - system. + Use the <code class="literal">xyaffs2</code> utiltiy to + decompress the <code class="literal">system.img</code> and get + the directory system. </p> <pre class="programlisting">$ xyaffs2 ./system.img system</pre> <p> - Add static sqlite3 shell utility. + Add static sqlite3 shell utility. </p> <pre class="programlisting">$ cp <root>/external/sqlite/dist/sqlite3orig \ system/xbin/sqlite3orig</pre> - <p> - Use the <code class="literal">mkyaffs2image</code> utility to rebuild - <code class="literal">system.img</code> from the changed directory - system. - </p> + <p> + Use the <code class="literal">mkyaffs2image</code> utility to + rebuild <code class="literal">system.img</code> from the changed + directory system. + </p> <pre class="programlisting">$ mkyaffs2image -f $PWD/system system.img</pre> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> - <p> - To open the database in the <code class="literal">SQLite</code> - format use the <code class="literal">sqlite3orig</code> - command. + <p> + To open the database in the + <code class="literal">SQLite</code> format use the + <code class="literal">sqlite3orig</code> command. </p> </div> </li> @@ -303,7 +334,8 @@ ${CC} -DANDROID -DOS_ANDROID --sysroot="${SYSROOT}" -mandroid \ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Building the Android JDBC Driver</td> + <td width="40%" align="right" valign="top"> Building the Android JDBC + Driver</td> </tr> </table> </div> diff --git a/docs/installation/build_android_jdbc.html b/docs/installation/build_android_jdbc.html index 11d31974..9ab30ca5 100644 --- a/docs/installation/build_android_jdbc.html +++ b/docs/installation/build_android_jdbc.html @@ -14,15 +14,17 @@ <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">Building the Android JDBC Driver</th> + <th colspan="3" align="center">Building the Android JDBC + Driver</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_android_intro.html">Prev</a> </td> - <th width="60%" align="center">Chapter 4. Building Berkeley DB for Android</th> + <th width="60%" align="center">Chapter 4. Building Berkeley DB for + Android</th> <td width="20%" align="right"> <a accesskey="n" href="build_android_config.html">Next</a></td> </tr> </table> @@ -32,32 +34,40 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_android_jdbc"></a>Building the Android JDBC Driver</h2> + <h2 class="title" style="clear: both"><a id="build_android_jdbc"></a>Building the Android JDBC + Driver</h2> </div> </div> </div> <p> - This section describes how to build and use the BDB JDBC driver - for Android. Note that the BDB JDBC driver cannot currently be - built on a Windows platform. + The JDBC API is an alternative to the drop-in replacement. + It is possible to build Berkeley DB SQL for Android in such a + way that a JDBC API is exposed to Android application + developers. This is done using the Android NDK. + </p> + <p> + This section describes how to build and use the BDB JDBC + driver for Android. Note that the BDB JDBC driver cannot + currently be built on a Windows platform. </p> <div class="orderedlist"> <ol type="1"> <li> - <p> - Download and install the Android SDK. The installation - instructions can be found here: + <p> + Download and install the Android SDK. The + installation instructions can be found here: </p> <p> - <a class="ulink" href="http://developer.android.com/sdk/installing.html" target="_top">http://developer.android.com/sdk/installing.html</a> + <a class="ulink" href="http://developer.android.com/sdk/installing/index.html" target="_top">http://developer.android.com/sdk/installing/index.html</a> </p> </li> <li> <p> - Download and install the Android NDK. It can be found here: + Download and install the Android NDK. It can be + found here: </p> <p> - <a class="ulink" href="http://developer.android.com/sdk/ndk/index.html" target="_top">http://developer.android.com/sdk/ndk/index.html</a> + <a class="ulink" href="http://developer.android.com/tools/sdk/ndk/index.html" target="_top">http://developer.android.com/tools/sdk/ndk/index.html</a> </p> </li> <li> @@ -72,56 +82,56 @@ Berkeley DB package from here: </p> <p> - <a class="ulink" href="http://www.oracle.com/technetwork/database/berkeleydb/downloads/index.html" target="_top">http://www.oracle.com/technetwork/database/berkeleydb/downloads/index.html</a> + <a class="ulink" href="http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index.html" target="_top">http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index.html</a> </p> <p> - Note that you must be using a 5.3.x or higher - version of the product in order for these - instructions to work. Once you have the package, - unpack it: + Note that you must be using a 5.3.x or + higher version of the product in order for + these instructions to work. Once you have the + package, unpack it: </p> <pre class="programlisting">$ tar zxvf db-x.y.z.tar.gz $ cd db-x.y.z</pre> - <p> - Where <code class="literal">x.y.z</code> the major, minor, - and point release version of the Berkeley DB - distribution which you are using. + <p> + Where <code class="literal">x.y.z</code> the major, + minor, and point release version of the + Berkeley DB distribution which you are using. </p> <p> - Also, note that in the following instructions, the - directory denoted by <code class="literal">db-x.y.z</code>, - above, is referred to as - <code class="literal"><db></code>. + Also, note that in the following + instructions, the directory denoted by + <code class="literal">db-x.y.z</code>, above, is + referred to as <code class="literal"><db></code>. </p> </li> <li> - <p> - Build an x86/x64 JDBC package. This is required - because the building process will generate target - files which are required to build Android NDK. - Also, the built JAR file can be imported by - eclipse, which will then convert it to the Android - Dalvik JAR format. + <p> + Build an x86/x64 JDBC package. This is + required because the building process will + generate target files which are required to + build Android NDK. Also, the built JAR file + can be imported by eclipse, which will then + convert it to the Android Dalvik JAR format. </p> - <p> + <p> To do this, edit - <code class="literal"><db>/lang/sql/jdbc/SQLit/Database.java</code> + <code class="literal"><db>/lang/sql/jdbc/SQLit/Database.java</code> and replace all instances of - <code class="literal">System.loadLibrary("sqlite_jni")</code> + <code class="literal">System.loadLibrary("sqlite_jni")</code> with - <code class="literal">System.loadLibrary("oracle-jdbc")</code>. + <code class="literal">System.loadLibrary("oracle-jdbc")</code>. </p> <p> - Once you have done this, configure and make the - library. The following example shows the minimum - configuration options that you need to use in order - to configure the Berkeley DB JDBC driver. For your - particular installation, other configuration - options might be interesting to you. See - <a class="xref" href="build_unix_conf.html" title="Configuring Berkeley DB">Configuring Berkeley DB</a> - and - <a class="xref" href="build_android_config.html" title="Android Configuration Options">Android Configuration Options</a> - for more information. + Once you have done this, configure and make + the library. The following example shows the + minimum configuration options that you need to + use in order to configure the Berkeley DB JDBC + driver. For your particular installation, + other configuration options might be + interesting to you. See <a class="xref" href="build_unix_conf.html" title="Configuring Berkeley DB">Configuring Berkeley DB</a> and + <a class="xref" href="build_android_config.html" title="Android Configuration Options">Android Configuration + Options</a> for + more information. </p> <pre class="programlisting">cd <db>/build_unix ../dist/configure --enable-jdbc && make</pre> @@ -130,8 +140,36 @@ $ cd db-x.y.z</pre> </div> </li> <li> + <p> + Enable encryption if required. + </p> + <p> + By default, encryption is disabled. To enable it, + edit + <code class="literal"><db>/build_android/jdbc/jni/Android.mk</code> + and change <code class="literal">BDB_ENABLE_ENCRYPTION</code> + from <code class="literal">false</code> to + <code class="literal">true</code>. + </p> + <p> + After enabling encryption, use <code class="literal">pragma + key</code> to set the password. You must do + this before performing any database operations. For + example: + </p> + <pre class="programlisting"> # ./dbsql test.db +dbsql> pragma key="xyzzy"; +dbsql> create table t1(x); +dbsql> .quit + +# ./dbsql test.db +dbsql> pragma key="xyzzy"; +dbsql> .tables +t1 </pre> + </li> + <li> <p> - Build the Android NDK: + Build the Android NDK: </p> <pre class="programlisting">$ cd <db>/build_android/jdbc/jni $ <ndk-install-directory>/ndk-build </pre> @@ -152,29 +190,29 @@ $ <ndk-install-directory>/ndk-build </pre> </li> </ol> </div> - <p> - Having built the JDBC driver, you can now use it with your project. - You can do this using Eclipse and the ADT plugin, which you can get - from here: + <p> + Having built the JDBC driver, you can now use it with your + project. You can do this using Eclipse and the ADT plugin, + which you can get from here: </p> <p> - <a class="ulink" href="http://developer.android.com/sdk/eclipse-adt.html" target="_top">http://developer.android.com/sdk/eclipse-adt.html</a> + <a class="ulink" href="http://developer.android.com/tools/sdk/eclipse-adt.html" target="_top">http://developer.android.com/tools/sdk/eclipse-adt.html</a> </p> - <p> + <p> To make sure everything is working: </p> <div class="orderedlist"> <ol type="1"> <li> - <p> - Start Eclipse and create an Android project. Use: + <p> + Start Eclipse and create an Android project. Use: </p> <div class="itemizedlist"> <ul type="disc"> <li> <p> - <code class="literal">test_jdbc</code> as the Android project - name. + <code class="literal">test_jdbc</code> as the Android + project name. </p> </li> <li> @@ -183,18 +221,18 @@ $ <ndk-install-directory>/ndk-build </pre> </p> </li> <li> - <p> + <p> For the package name, use - <code class="literal">example.jdbc</code>. + <code class="literal">example.jdbc</code>. </p> </li> </ul> </div> </li> <li> - <p> - This results in an empty code file. Copy and paste the - following example code into that file: + <p> + This results in an empty code file. Copy and paste + the following example code into that file: </p> <pre class="programlisting">package example.testjdbc; @@ -285,8 +323,8 @@ public class Test_jdbcActivity extends Activity { } </pre> </li> <li> - <p> - Copy the following files into place: + <p> + Copy the following files into place: </p> <pre class="programlisting">$ cd <workspace>/test_jdbc $ mkdir -p libs/armeabi @@ -295,18 +333,16 @@ libs/armeabi $ cp -r <db>/build_unix/jdbc/sqlite.jar libs</pre> </li> <li> - <p> - Back in Eclipse, right click the project name, and select - the <code class="literal">refresh</code> option to reload the project - from the directory. The two new files that were copied into - place in the previous step are now included in the project - view. + <p> + Back in Eclipse, right click the project name, and + select the <code class="literal">refresh</code> option to reload + the project from the directory. The two new files that + were copied into place in the previous step are now + included in the project view. </p> </li> <li> - <p> - Convert the JAR file to the Android Dalvik format: - </p> + <p> Convert the JAR file to the Android Dalvik format: </p> <div class="orderedlist"> <ol type="a"> <li> @@ -316,7 +352,8 @@ $ cp -r <db>/build_unix/jdbc/sqlite.jar libs</pre> </li> <li> <p> - Choose <code class="literal">Build Path -> Configure Build Path</code> + Choose <code class="literal">Build Path -> Configure + Build Path</code> </p> </li> <li> @@ -325,39 +362,42 @@ $ cp -r <db>/build_unix/jdbc/sqlite.jar libs</pre> </p> </li> <li> - <p> - Click <code class="literal">Add JARS</code>. + <p> + Click <code class="literal">Add JARS</code>. </p> </li> </ol> </div> </li> <li> - <p> - Run the project: + <p> + Run the project: </p> <div class="orderedlist"> <ol type="a"> <li> <p> - Choose <code class="literal">Property -> Android</code> - and select any one of the usable build targets. + Choose <code class="literal">Property -> + Android</code> and select any one of + the usable build targets. </p> </li> <li> - <p> - Right click the project. Choose <code class="literal">Run As -> Android</code> + <p> + Right click the project. Choose + <code class="literal">Run As -> Android</code> </p> </li> </ol> </div> </li> <li> - <p> - Verify your installation. After a short pause (depending - on the speed of your system), the application logo is - displayed. Use the Android adb command line application to - make sure the application is running as expected: + <p> + Verify your installation. After a short pause + (depending on the speed of your system), the + application logo is displayed. Use the Android adb + command line application to make sure the application + is running as expected: </p> <pre class="programlisting">$ cd <android-sdk>/platform-tools $ ./adb logcat @@ -368,9 +408,9 @@ I/System.out( 539): French_Roast 8.99 I/System.out( 539): Espresso 9.99 I/System.out( 539): Colombian_Decaf 8.99 I/System.out( 539): French_Roast_Decaf 9.99</pre> - <p> + <p> You can also check if the database - (<code class="literal">example.db</code>) exists in the + (<code class="literal">example.db</code>) exists in the emulator: </p> <pre class="programlisting">$ ./adb shell ls /data/data/example.testjdbc @@ -378,7 +418,8 @@ example.db example.db-journal lib </pre> <p> - Finally, check the database using the BDB SQL shell: + Finally, check the database using the BDB SQL + shell: </p> <pre class="programlisting"> $ ./adb push <db>/build_android/jdbc/libs/armeabi/dbsql \ @@ -414,11 +455,13 @@ dbsql> .quit </pre> <td width="40%" align="right"> <a accesskey="n" href="build_android_config.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 4. Building Berkeley DB for Android </td> + <td width="40%" align="left" valign="top">Chapter 4. Building Berkeley DB for + Android </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Android Configuration Options</td> + <td width="40%" align="right" valign="top"> Android Configuration + Options</td> </tr> </table> </div> diff --git a/docs/installation/build_unix.html b/docs/installation/build_unix.html index 12b188c7..e01861eb 100644 --- a/docs/installation/build_unix.html +++ b/docs/installation/build_unix.html @@ -8,22 +8,21 @@ <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> <link rel="up" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="prev" href="build_wince_faq.html" title="Windows Mobile FAQ" /> + <link rel="prev" href="build_winec_intro.html" title="Building for Windows Embedded Compact 7" /> <link rel="next" href="build_unix_conf.html" title="Configuring Berkeley DB" /> </head> <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 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th colspan="3" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> </tr> <tr> - <td width="20%" align="left"><a accesskey="p" href="build_wince_faq.html">Prev</a> </td> + <td width="20%" align="left"><a accesskey="p" href="build_winec_intro.html">Prev</a> </td> <th width="60%" align="center"> </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_conf.html">Next</a></td> </tr> @@ -34,9 +33,8 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="build_unix"></a>Chapter 7. - Building Berkeley DB for UNIX/POSIX - </h2> + <h2 class="title"><a id="build_unix"></a>Chapter 7. Building Berkeley DB for UNIX/POSIX + </h2> </div> </div> </div> @@ -66,7 +64,8 @@ </dt> <dt> <span class="sect1"> - <a href="build_unix_sql.html">Configuring the SQL Interface</a> + <a href="build_unix_sql.html">Configuring the SQL + Interface</a> </span> </dt> <dd> @@ -78,7 +77,7 @@ </dt> <dt> <span class="sect2"> - <a href="build_unix_sql.html#idp249752">Enabling Extensions</a> + <a href="build_unix_sql.html#idp698856">Enabling Extensions</a> </span> </dt> <dt> @@ -88,12 +87,12 @@ </dt> <dt> <span class="sect2"> - <a href="build_unix_sql.html#idp327120">Using the JDBC Driver</a> + <a href="build_unix_sql.html#idp704816">Using the JDBC Driver</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_unix_sql.html#idp349152">Building the ODBC Driver</a> + <a href="build_unix_sql.html#idp736952">Building the ODBC Driver</a> </span> </dt> <dt> @@ -110,17 +109,20 @@ </dt> <dt> <span class="sect1"> - <a href="build_unix_flags.html">Changing compile or load options</a> + <a href="build_unix_flags.html">Changing compile or load + options</a> </span> </dt> <dt> <span class="sect1"> - <a href="cross_compile_unix.html">Cross-Compiling on Unix</a> + <a href="cross_compile_unix.html">Cross-Compiling on + Unix</a> </span> </dt> <dt> <span class="sect1"> - <a href="build_unix_install.html">Installing Berkeley DB</a> + <a href="build_unix_install.html">Installing Berkeley + DB</a> </span> </dt> <dt> @@ -130,7 +132,8 @@ </dt> <dt> <span class="sect1"> - <a href="build_unix_test.html">Running the test suite under UNIX</a> + <a href="build_unix_test.html">Running the test suite under + UNIX</a> </span> </dt> <dd> @@ -217,30 +220,31 @@ </dl> </div> <p> - The Berkeley DB distribution builds up to four separate libraries: - the base C API Berkeley DB library and the optional C++, Java, and - Tcl API libraries. For portability reasons, each library is - standalone and contains the full Berkeley DB support necessary to - build applications; that is, the C++ API Berkeley DB library does - not require any other Berkeley DB libraries to build and run C++ - applications. + The Berkeley DB distribution builds up to six separate + libraries: the base C API Berkeley DB library and the optional + C++, Java, Tcl, SQL, and JDBC API libraries. For portability + reasons, each library is standalone and contains the full + Berkeley DB support necessary to build applications; that is, + the C++ API Berkeley DB library does not require any other + Berkeley DB libraries to build and run C++ applications. </p> - <p> - Building for Linux, Apple iOS (known as iPhone OS previously), Mac OS X or the QNX Neutrino release is the same - as building for a conventional UNIX platform. + <p> + Building for Linux, Apple iOS (known as iPhone OS + previously), Mac OS X or the QNX Neutrino release is the same + as building for a conventional UNIX platform. </p> - <p> - The Berkeley DB distribution uses the Free Software Foundation's - <a class="ulink" href="http://www.gnu.org/software/autoconf/autoconf.html" target="_top">autoconf</a> + <p> + The Berkeley DB distribution uses the Free Software + Foundation's <a class="ulink" href="http://www.gnu.org/software/autoconf/autoconf.html" target="_top">autoconf</a> and <a class="ulink" href="http://www.gnu.org/software/libtool/libtool.html" target="_top">libtool</a> - tools to build on UNIX platforms. In general, the standard - configuration and installation options for these tools apply to the - Berkeley DB distribution. + tools to build on UNIX platforms. In + general, the standard configuration and installation options + for these tools apply to the Berkeley DB distribution. </p> - <p> - To perform a standard UNIX build of Berkeley DB, change to the - <span class="bold"><strong>build_unix</strong></span> - directory and then enter the following two commands: + <p> + To perform a standard UNIX build of Berkeley DB, change to + the <span class="bold"><strong>build_unix</strong></span> directory and + then enter the following two commands: </p> <pre class="programlisting">../dist/configure make</pre> @@ -248,30 +252,32 @@ make</pre> This will build the Berkeley DB library. </p> <p> - To install the Berkeley DB library, enter the following command: + To install the Berkeley DB library, enter the following + command: </p> <pre class="programlisting">make install</pre> - <p> + <p> To rebuild Berkeley DB, enter: </p> <pre class="programlisting">make clean make</pre> <p> - If you change your mind about how Berkeley DB is to be configured, you must - start from scratch by entering the following command: + If you change your mind about how Berkeley DB is to be + configured, you must start from scratch by entering the + following command: </p> <pre class="programlisting">make realclean ../dist/configure make</pre> - <p> + <p> To uninstall Berkeley DB, enter: </p> <pre class="programlisting">make uninstall</pre> <p> - To build multiple UNIX versions of Berkeley DB in the same source - tree, create a new directory at the same level as the build_unix - directory, and then configure and build in that directory as - described previously. + To build multiple UNIX versions of Berkeley DB in the same + source tree, create a new directory at the same level as the + build_unix directory, and then configure and build in that + directory as described previously. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> @@ -281,37 +287,40 @@ make</pre> </div> </div> </div> - <p> - To perform a standard UNIX build of the Berkeley DB SQL interface, go - to the <span class="bold"><strong>build_unix</strong></span> directory and then - enter the following two commands: + <p> + To perform a standard UNIX build of the Berkeley DB SQL + interface, go to the <span class="bold"><strong>build_unix</strong></span> + directory and then enter the following two commands: </p> <pre class="programlisting">../dist/configure --enable-sql make </pre> - <p> - This creates a library, <code class="literal">libdb_sql</code>, and a command - line tool, <code class="literal">dbsql</code>. You can create and manipulate SQL - databases using the <code class="literal">dbsql</code> shell. + <p> + This creates a library, <code class="literal">libdb_sql</code>, + and a command line tool, <code class="literal">dbsql</code>. You can + create and manipulate SQL databases using the + <code class="literal">dbsql</code> shell. </p> <p> - You can optionally provide the <code class="literal">--enable-sql_compat</code> - argument to the <code class="literal">configure</code> script. In addition to - creating <code class="literal">libdb_sql</code> and <code class="literal">dbsql</code> this - causes a thin wrapper library called <code class="literal">libsqlite3</code> and - a command line tool called <code class="literal">sqlite3</code> to be built. This - library can be used as a drop-in replacement for SQLite. The - <code class="literal">sqlite3</code> command line tool is identical to the - <code class="literal">dbsql</code> executable but is named so that existing - scripts for SQLite can easily work with Berkeley DB. + You can optionally provide the + <code class="literal">--enable-sql_compat</code> argument to the + <code class="literal">configure</code> script. In addition to + creating <code class="literal">libdb_sql</code> and + <code class="literal">dbsql</code> this causes a thin wrapper + library called <code class="literal">libsqlite3</code> and a command + line tool called <code class="literal">sqlite3</code> to be built. + This library can be used as a drop-in replacement for + SQLite. The <code class="literal">sqlite3</code> command line tool + is identical to the <code class="literal">dbsql</code> executable + but is named so that existing scripts for SQLite can + easily work with Berkeley DB. </p> <pre class="programlisting"> ../dist/configure --enable-sql_compat make </pre> <p> - There are several arguments you can specify when configuring the - Berkeley DB SQL Interface. See - <a class="xref" href="build_unix_sql.html" title="Configuring the SQL Interface">Configuring the SQL Interface</a> - for more information. + There are several arguments you can specify when + configuring the Berkeley DB SQL Interface. See <a class="xref" href="build_unix_sql.html" title="Configuring the SQL Interface">Configuring the SQL + Interface</a> for more information. </p> </div> </div> @@ -320,12 +329,13 @@ make </pre> <hr /> <table width="100%" summary="Navigation footer"> <tr> - <td width="40%" align="left"><a accesskey="p" href="build_wince_faq.html">Prev</a> </td> + <td width="40%" align="left"><a accesskey="p" href="build_winec_intro.html">Prev</a> </td> <td width="20%" align="center"> </td> <td width="40%" align="right"> <a accesskey="n" href="build_unix_conf.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Windows Mobile FAQ </td> + <td width="40%" align="left" valign="top">Building for Windows + Embedded Compact 7 </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/build_unix_aix.html b/docs/installation/build_unix_aix.html index 498038c2..00587363 100644 --- a/docs/installation/build_unix_aix.html +++ b/docs/installation/build_unix_aix.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_notes.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_freebsd.html">Next</a></td> </tr> </table> @@ -42,94 +41,160 @@ <ol type="1"> <li> <span class="bold"> - <strong>I can't compile and run multithreaded applications.</strong> + <strong>I can't compile and run + multithreaded applications.</strong> </span> - <p>Special compile-time flags are required when compiling threaded -applications on AIX. If you are compiling a threaded application, you -must compile with the _THREAD_SAFE flag and load with specific -libraries; for example, "-lc_r". Specifying the compiler name with a -trailing "_r" usually performs the right actions for the system.</p> + <p> + Special compile-time flags are required when + compiling threaded applications on AIX. If you are + compiling a threaded application, you must compile + with the _THREAD_SAFE flag and load with specific + libraries; for example, "-lc_r". Specifying the + compiler name with a trailing "_r" usually performs + the right actions for the system. + </p> <pre class="programlisting">xlc_r ... cc -D_THREAD_SAFE -lc_r ...</pre> - <p>The Berkeley DB library will automatically build with the correct options.</p> + <p> + The Berkeley DB library will automatically build + with the correct options. + </p> </li> <li> <span class="bold"> - <strong>I can't run using the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> option to -<a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a>.</strong> + <strong>I can't run using the + <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> option to <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a>.</strong> </span> - <p>AIX 4.1 allows applications to map only 10 system shared memory -segments. In AIX 4.3, this has been raised to 256K segments, but only -if you set the environment variable "export EXTSHM=ON".</p> + <p> + AIX 4.1 allows applications to map only 10 system + shared memory segments. In AIX 4.3, this has been + raised to 256K segments, but only if you set the + environment variable "export EXTSHM=ON". + </p> </li> <li> <span class="bold"> - <strong>On AIX 4.3.2 (or before) I see duplicate symbol warnings when -building the C++ shared library and when linking applications.</strong> + <strong>On AIX 4.3.2 (or before) I see + duplicate symbol warnings when building the C++ shared + library and when linking applications.</strong> </span> - <p>We are aware of some duplicate symbol warnings with this platform, -but they do not appear to affect the correct operation of applications.</p> + <p> + We are aware of some duplicate symbol warnings with + this platform, but they do not appear to affect the + correct operation of applications. + </p> </li> <li> <span class="bold"> - <strong>On AIX 4.3.3 I see undefined symbols for DbEnv::set_error_stream, -Db::set_error_stream or DbEnv::verify when linking C++ applications. -(These undefined symbols also appear when building the Berkeley DB C++ example -applications).</strong> + <strong>On AIX 4.3.3 I see undefined symbols + for DbEnv::set_error_stream, Db::set_error_stream or + DbEnv::verify when linking C++ applications. (These + undefined symbols also appear when building the + Berkeley DB C++ example applications).</strong> </span> - <p>By default, Berkeley DB is built with _LARGE_FILES set to 1 to support the -creation of "large" database files. However, this also affects how -standard classes, like iostream, are named internally. When building -your application, use a "-D_LARGE_FILES=1" compilation option, or insert -"#define _LARGE_FILES 1" before any #include statements.</p> + <p> + By default, Berkeley DB is built with _LARGE_FILES + set to 1 to support the creation of "large" database + files. However, this also affects how standard + classes, like iostream, are named internally. When + building your application, use a "-D_LARGE_FILES=1" + compilation option, or insert "#define _LARGE_FILES 1" + before any #include statements. + </p> </li> <li> <span class="bold"> - <strong>I can't create database files larger than 1GB on AIX.</strong> + <strong>I can't create database files larger + than 1GB on AIX.</strong> </span> - <p>If you're running on AIX 4.1 or earlier, try changing the source code -for <code class="filename">os/os_open.c</code> to always specify the <span class="bold"><strong>O_LARGEFILE</strong></span> -flag to the <code class="literal">open</code>(2) system call, and recompile Berkeley DB from -scratch.</p> - <p>Also, the documentation for the IBM Visual Age compiler states that it -does not not support the 64-bit filesystem APIs necessary for creating -large files; the ibmcxx product must be used instead. We have not heard -whether the GNU gcc compiler supports the 64-bit APIs or not.</p> - <p>Finally, to create large files under AIX, the filesystem has to be -configured to support large files and the system wide user hard-limit -for file sizes has to be greater than 1GB.</p> + <p> + If you're running on AIX 4.1 or earlier, try + changing the source code for + <code class="filename">os/os_open.c</code> to always + specify the <span class="bold"><strong>O_LARGEFILE</strong></span> flag to the + <code class="literal">open</code>(2) system call, and + recompile Berkeley DB from scratch. + </p> + <p> + Also, the documentation for the IBM Visual Age + compiler states that it does not not support the + 64-bit filesystem APIs necessary for creating large + files; the ibmcxx product must be used instead. We + have not heard whether the GNU gcc compiler supports + the 64-bit APIs or not. + </p> + <p> + Finally, to create large files under AIX, the + filesystem has to be configured to support large files + and the system wide user hard-limit for file sizes has + to be greater than 1GB. + </p> </li> <li> <span class="bold"> - <strong>I see errors about "open64" when building Berkeley DB applications.</strong> + <strong>I see errors about "open64" when + building Berkeley DB applications.</strong> </span> - <p>System include files (most commonly fcntl.h) in some releases of AIX -and Solaris redefine "open" when large-file support is enabled for -applications. This causes problems when compiling applications because -"open" is a method in the Berkeley DB APIs. To work around this problem: -</p> + <p> + System include files (most commonly fcntl.h) in + some releases of AIX and Solaris redefine "open" when + large-file support is enabled for applications. This + causes problems when compiling applications because + "open" is a method in the Berkeley DB APIs. To work + around this problem: + </p> <div class="orderedlist"> <ol type="a"> - <li>Avoid including the problematical system include files in source code -files which also include Berkeley DB include files and call into the Berkeley DB -API.</li> - <li>Before building Berkeley DB, modify the generated include file db.h to itself -include the problematical system include files.</li> - <li>Turn off Berkeley DB large-file support by specifying the -<a class="link" href="build_unix_conf.html#build_unix_conf.--disable-largefile">--disable-largefile</a> configuration option and rebuilding.</li> + <li> + Avoid including the problematical system + include files in source code files which also + include Berkeley DB include files and call into + the Berkeley DB API. + </li> + <li> + Before building Berkeley DB, modify the + generated include file db.h to itself include the + problematical system include files. + </li> + <li> + Turn off Berkeley DB large-file support by + specifying the <a class="link" href="build_unix_conf.html#build_unix_conf.--disable-largefile">--disable-largefile</a> + configuration option and rebuilding. + </li> </ol> </div> </li> <li> <span class="bold"> - <strong>I see the error "Redeclaration of lseek64" when building Berkeley DB with the --enable-sql and --enable-test options.</strong> + <strong>I see the error "Redeclaration of + lseek64" when building Berkeley DB with the + --enable-sql and --enable-test options.</strong> </span> - <p>In some releases of AIX, the system include files (most commonly <code class="literal">unistd.h</code>) redefine <code class="literal">lseek</code> to <code class="literal">lseek64</code> when large-file support is enabled even though <code class="literal">lseek</code> may have already been defined when the <code class="literal">_LARGE_FILE_API</code> macro is on. To work around this problem, do either one of the following: -</p> + <p> + In some releases of AIX, the system include files + (most commonly <code class="literal">unistd.h</code>) redefine + <code class="literal">lseek</code> to + <code class="literal">lseek64</code> when large-file support + is enabled even though <code class="literal">lseek</code> may + have already been defined when the + <code class="literal">_LARGE_FILE_API</code> macro is on. To + work around this problem, do either one of the + following: + </p> <div class="orderedlist"> <ol type="a"> - <li>Disable large-file support in Berkeley DB by specifying the <code class="literal">--disable-largefile</code> configuration option and rebuilding. </li> - <li>Edit <code class="literal">db.h</code> manually after running the configure command, and remove the line that includes <code class="literal">unistd.h</code>. </li> + <li> + Disable large-file support in Berkeley + DB by specifying the + <code class="literal">--disable-largefile</code> + configuration option and rebuilding. + </li> + <li> + Edit <code class="literal">db.h</code> manually + after running the configure command, and + remove the line that includes + <code class="literal">unistd.h</code>. + </li> </ol> </div> </li> diff --git a/docs/installation/build_unix_conf.html b/docs/installation/build_unix_conf.html index 88135f3b..65cb1716 100644 --- a/docs/installation/build_unix_conf.html +++ b/docs/installation/build_unix_conf.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_sql.html">Next</a></td> </tr> </table> @@ -38,495 +37,634 @@ </div> </div> </div> - <p>There are several arguments you can specify when configuring Berkeley DB. -Although only the Berkeley DB-specific ones are described here, most of the -standard GNU autoconf arguments are available and supported. To see a -complete list of possible arguments, specify the --help flag to the -configure program.</p> - <p>The Berkeley DB specific arguments are as follows:</p> + <p> + There are several arguments you can specify when configuring + Berkeley DB. Although only the Berkeley DB-specific ones are + described here, most of the standard GNU autoconf arguments + are available and supported. To see a complete list of + possible arguments, specify the --help flag to the configure + program. + </p> + <p> + The Berkeley DB specific arguments are as follows: + </p> <div class="itemizedlist"> <ul type="disc"> <li> <p><a id="build_unix_conf.--disable-largefile"></a> - <span class="bold"><strong>--disable-largefile</strong></span> - </p> - <p> - Some systems, notably versions of Solaris, require - special compile-time options in order to create files larger - than 2^32 bytes. These options are automatically enabled when - Berkeley DB is compiled. For this reason, binaries built on - current versions of these systems may not run on earlier - versions of the system because the library and system calls - necessary for large files are not available. To disable - building with these compile-time options, enter - --disable-largefile as an argument to configure. - </p> + <span class="bold"><strong>--disable-largefile</strong></span> + </p> + <p> + Some systems, notably versions of Solaris, require + special compile-time options in order to create files + larger than 2^32 bytes. These options are + automatically enabled when Berkeley DB is compiled. + For this reason, binaries built on current versions of + these systems may not run on earlier versions of the + system because the library and system calls necessary + for large files are not available. To disable building + with these compile-time options, enter + --disable-largefile as an argument to configure. + </p> </li> <li> <p> - <span class="bold"><strong>--disable-shared, --disable-static</strong></span> - </p> - <p> - On systems supporting shared libraries, Berkeley DB builds both - static and shared libraries by default. (Shared libraries are - built using - <a class="ulink" href="http://www.gnu.org/software/libtool/libtool.html" target="_top"> - the GNU Project's Libtool</a> distribution, which supports - shared library builds on many (although not all) systems.) To - not build shared libraries, configure using the - --disable-shared argument. To not build static libraries, - configure using the --disable-static argument. - </p> + <span class="bold"><strong>--disable-shared, + --disable-static</strong></span> + </p> + <p> + On systems supporting shared libraries, Berkeley DB + builds both static and shared libraries by default. + (Shared libraries are built using <a class="ulink" href="http://www.gnu.org/software/libtool/libtool.html" target="_top"> the GNU + Project's Libtool</a> distribution, + which supports shared library builds on many (although + not all) systems.) To not build shared libraries, + configure using the --disable-shared argument. To not + build static libraries, configure using the + --disable-static argument. + </p> </li> <li> <p><a id="build_unix_conf.--disable-heap"></a> - <span class="bold"><strong>--disable-heap</strong></span> - </p> - <p> - Disables the Heap access method so that it cannot be used by - Berkeley DB applications. - </p> + <span class="bold"><strong>--disable-heap</strong></span> + </p> + <p> + Disables the Heap access method so that it cannot + be used by Berkeley DB applications. + </p> </li> <li> <p> - <span class="bold"><strong>--enable-compat185</strong></span> - </p> + <span class="bold"><strong>--enable-compat185</strong></span> + </p> <p> - To compile or load Berkeley DB 1.85 applications against this - release of the Berkeley DB library, enter --enable-compat185 as - an argument to configure. This will include Berkeley DB 1.85 - API compatibility code in the library. - </p> + To compile or load Berkeley DB 1.85 applications + against this release of the Berkeley DB library, enter + --enable-compat185 as an argument to configure. This + will include Berkeley DB 1.85 API compatibility code + in the library. + </p> </li> <li> <p> - <span class="bold"><strong>--enable-cxx</strong></span> - </p> - <p> - To build the Berkeley DB C++ API, enter --enable-cxx as an - argument to configure. - </p> + <span class="bold"><strong>--enable-cxx</strong></span> + </p> + <p> + To build the Berkeley DB C++ API, enter + --enable-cxx as an argument to configure. + </p> </li> <li> <p><a id="build_unix_conf.--enable-debug"></a> - <span class="bold"><strong>--enable-debug</strong></span> - </p> - <p> - To build Berkeley DB with <span class="bold"><strong>-g</strong></span> - as a compiler flag and with <span class="bold"><strong>DEBUG</strong></span> #defined during compilation, - enter --enable-debug as an argument to configure. This will - create a Berkeley DB library and utilities with debugging - symbols, as well as load various routines that can be called - from a debugger to display pages, cursor queues, and so forth. - If installed, the utilities will not be stripped. This - argument should not be specified when configuring to build - production binaries. - </p> + <span class="bold"><strong>--enable-debug</strong></span> + </p> + <p> + To build Berkeley DB with <span class="bold"><strong>-g</strong></span> + as a compiler flag and with <span class="bold"><strong>DEBUG</strong></span> #defined + during compilation, enter --enable-debug as an + argument to configure. This will create a Berkeley DB + library and utilities with debugging symbols, as well + as load various routines that can be called from a + debugger to display pages, cursor queues, and so + forth. If installed, the utilities will not be + stripped. This argument should not be specified when + configuring to build production binaries. + </p> </li> <li> <p><a id="build_unix_conf.--enable-debug_rop"></a> - <span class="bold"><strong>--enable-debug_rop</strong></span> - </p> - <p> - To build Berkeley DB to output log records for read operations, - enter --enable-debug_rop as an argument to configure. This - argument should not be specified when configuring to build - production binaries. - </p> + <span class="bold"><strong>--enable-debug_rop</strong></span> + </p> + <p> + To build Berkeley DB to output log records for read + operations, enter --enable-debug_rop as an argument to + configure. This argument should not be specified when + configuring to build production binaries. + </p> </li> <li> <p><a id="build_unix_conf.--enable-debug_wop"></a> - <span class="bold"><strong>--enable-debug_wop</strong></span> - </p> - <p> - To build Berkeley DB to output log records for write - operations, enter --enable-debug_wop as an argument to - configure. This argument should not be specified when - configuring to build production binaries. - </p> + <span class="bold"><strong>--enable-debug_wop</strong></span> + </p> + <p> + To build Berkeley DB to output log records for + write operations, enter --enable-debug_wop as an + argument to configure. This argument should not be + specified when configuring to build production + binaries. + </p> </li> <li> <p><a id="build_unix_conf.--enable-diagnostic"></a> - <span class="bold"><strong>--enable-diagnostic</strong></span> - </p> - <p> - - To build Berkeley DB with run-time debugging checks, enter - --enable-diagnostic as an argument to configure. This causes a - number of additional checks to be performed when Berkeley DB is - running, and also causes some failures to trigger process abort - rather than returning errors to the application. Applications - built using this argument should not share database - environments with applications built without this argument. - This argument should not be specified when configuring to build - production binaries. - </p> + <span class="bold"><strong>--enable-diagnostic</strong></span> + </p> + <p> + To build Berkeley DB with run-time debugging + checks, enter --enable-diagnostic as an argument to + configure. This causes a number of additional checks + to be performed when Berkeley DB is running, and also + causes some failures to trigger process abort rather + than returning errors to the application. Applications + built using this argument should not share database + environments with applications built without this + argument. This argument should not be specified when + configuring to build production binaries. + </p> </li> <li> <p> - <span class="bold"><strong>--enable-dump185</strong></span> - </p> - <p> - To convert Berkeley DB 1.85 (or earlier) databases to this - release of Berkeley DB, enter --enable-dump185 as an argument - to configure. This will build the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility, which can dump - Berkeley DB 1.85 and 1.86 databases in a format readable by the - Berkeley DB <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility. - </p> - <p> - The system libraries with which you are loading the - <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility must already contain the Berkeley DB 1.85 library - routines for this to work because the Berkeley DB distribution - does not include them. If you are using a non-standard library - for the Berkeley DB 1.85 library routines, you will have to - change the Makefile that the configuration step creates to load - the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility with that library. - </p> + <span class="bold"><strong>--enable-dump185</strong></span> + </p> + <p> + To convert Berkeley DB 1.85 (or earlier) databases + to this release of Berkeley DB, enter --enable-dump185 + as an argument to configure. This will build the + <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility, which can dump Berkeley DB 1.85 and 1.86 + databases in a format readable by the Berkeley DB + <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility. + </p> + <p> + The system libraries with which you are loading the + <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility must already contain the Berkeley DB 1.85 + library routines for this to work because the Berkeley + DB distribution does not include them. If you are + using a non-standard library for the Berkeley DB 1.85 + library routines, you will have to change the Makefile + that the configuration step creates to load the + <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility with that library. + </p> + </li> + <li> + <p><a id="build_unix_conf.--enable-error_history"></a> + <span class="bold"><strong>--enable-error_history</strong></span> + </p> + <p> + Causes more detailed error messages to be displayed for most + error messages. The additional information includes the + process and thread identifiers, timestamp, and certain + previous unusual conditions detected during the API call. + Stack traces are also displayed, where they are supported. + </p> + <p> + This option is available only for Unix-like platforms which + support the pthread_getspecific() thread local storage + functions. + </p> + </li> + <li> + <p><a id="build_unix_conf.--enable-failchk_broadcast"></a> + <span class="bold"><strong>--enable-failchk_broadcast</strong></span> + </p> + <p> + Enable the mode of the <a href="../api_reference/C/envfailchk.html" class="olink">DB_ENV->failchk()</a> feature which causes + processes in the environment to be notified of an + application failure as soon as possible. When this feature + is enabled threads waiting on a mutex owned by a crashed + process will return a + <a href="../programmer_reference/program_errorret.html#program_errorret.DB_RUNRECOVERY" class="olink"> + DB_RUNRECOVERY + </a> error. Without this feature, those + processes may hang until intervention by some other entity, + such as a "watcher process" as mentioned in + <a href="../programmer_reference/transapp_app.html" class="olink"> + Architecting Transactional Data Store applications + </a> or a user interrupting the program. + </p> </li> <li> <p><a id="build_unix_conf.--enable-java"></a> - <span class="bold"><strong>--enable-java</strong></span> - </p> - <p> - To build the Berkeley DB Java API, enter --enable-java as an - argument to configure. To build Java, you must also build with - shared libraries. Before configuring, you must set your PATH - environment variable to include javac. Note that it is not - sufficient to include a symbolic link to javac in your PATH - because the configuration process uses the location of javac to - determine the location of the Java include files (for example, - jni.h). On some systems, additional include directories may be - needed to process jni.h; see <a class="xref" href="build_unix_flags.html" title="Changing compile or load options">Changing compile or load options</a> for more information. - </p> + <span class="bold"><strong>--enable-java</strong></span> + </p> + <p> + To build the Berkeley DB Java API, enter + --enable-java as an argument to configure. To build + Java, you must also build with shared libraries. + Before configuring, you must set your PATH environment + variable to include javac. Note that it is not + sufficient to include a symbolic link to javac in your + PATH because the configuration process uses the + location of javac to determine the location of the + Java include files (for example, jni.h). On some + systems, additional include directories may be needed + to process jni.h; see <a class="xref" href="build_unix_flags.html" title="Changing compile or load options">Changing compile or load + options</a> for more + information. + </p> + <p> + </p> + <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3> + The --enable-java option may not be specified + at the same time as --enable-smallbuild or + --disable-statistics. + </div> + <p> + </p> </li> <li> <p><a id="build_unix_conf.--enable-posixmutexes"></a> - <span class="bold"><strong>--enable-posixmutexes</strong></span> - </p> - <p> - To force Berkeley DB to use the POSIX pthread mutex interfaces - for underlying mutex support, enter --enable-posixmutexes as an - argument to configure. This is rarely necessary: POSIX mutexes - will be selected automatically on systems where they are the - preferred implementation. - </p> - <p> - The --enable-posixmutexes configuration argument is normally - used in two ways: First, when there are multiple mutex - implementations available and the POSIX mutex implementation is - not the preferred one (for example, on Solaris where the LWP - mutexes are used by default). Second, by default the Berkeley - DB library will only select the POSIX mutex implementation if - it supports mutexes shared between multiple processes, as - described for the pthread_condattr_setpshared and - pthread_mutexattr_setpshared interfaces. The - --enable-posixmutexes configuration argument can be used to - force the selection of POSIX mutexes in this case, which can - improve application performance significantly when the - alternative mutex implementation is a non-blocking one (for - example test-and-set assembly instructions). However, - configuring to use POSIX mutexes when the implementation does - not have inter-process support will only allow the creation of - private database environments, that is, environments where the - <a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag is specified to the <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a> method. - </p> - <p> - Specifying the --enable-posixmutexes configuration argument may require - that applications and Berkeley DB be linked with the -lpthread library. - </p> + <span class="bold"><strong>--enable-posixmutexes</strong></span> + </p> + <p> + To force Berkeley DB to use the POSIX pthread mutex + interfaces for underlying mutex support, enter + --enable-posixmutexes as an argument to configure. + This is rarely necessary: POSIX mutexes will be + selected automatically on systems where they are the + preferred implementation. + </p> + <p> + The --enable-posixmutexes configuration argument is + normally used in two ways: First, when there are + multiple mutex implementations available and the POSIX + mutex implementation is not the preferred one (for + example, on Solaris where the LWP mutexes are used by + default). Second, by default the Berkeley DB library + will only select the POSIX mutex implementation if it + supports mutexes shared between multiple processes, as + described for the pthread_condattr_setpshared and + pthread_mutexattr_setpshared interfaces. The + --enable-posixmutexes configuration argument can be + used to force the selection of POSIX mutexes in this + case, which can improve application performance + significantly when the alternative mutex + implementation is a non-blocking one (for example + test-and-set assembly instructions). However, + configuring to use POSIX mutexes when the + implementation does not have inter-process support + will only allow the creation of private database + environments, that is, environments where the + <a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag is specified to the <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a> + method. + </p> + <p> + Specifying the --enable-posixmutexes configuration + argument may require that applications and Berkeley DB + be linked with the -lpthread library. + </p> </li> <li> <p><a id="build_unix_conf.--enable-pthread_api"></a> - <span class="bold"><strong>--enable-pthread_api</strong></span> - </p> - <p> - To configure Berkeley DB for a POSIX pthreads application (with - the exception that POSIX pthread mutexes may not be selected as - the underlying mutex implementation for the build), enter - --enable-pthread_api as an argument to configure. The build - will include the Berkeley DB replication manager interfaces and - will use the POSIX standard pthread_self and pthread_yield - functions to identify threads of control and yield the - processor. The --enable-pthread_api argument requires POSIX - pthread support already be installed on your system. - </p> - <p> - Specifying the --enable-pthread_api configuration argument may - require that applications and Berkeley DB be linked with the - -lpthread library. - </p> + <span class="bold"><strong>--enable-pthread_api</strong></span> + </p> + <p> + To configure Berkeley DB for a POSIX pthreads + application (with the exception that POSIX pthread + mutexes may not be selected as the underlying mutex + implementation for the build), enter + --enable-pthread_api as an argument to configure. The + build will include the Berkeley DB replication manager + interfaces and will use the POSIX standard + pthread_self and pthread_yield functions to identify + threads of control and yield the processor. The + --enable-pthread_api argument requires POSIX pthread + support already be installed on your system. + </p> + <p> + Specifying the --enable-pthread_api configuration + argument may require that applications and Berkeley DB + be linked with the -lpthread library. + </p> </li> <li> <p><a id="build_unix_conf.--enable-sql"></a> - <span class="bold"><strong>--enable-sql</strong></span> - </p> - <p> - To build the command tool dbsql, enter --enable-sql as an argument to configure. The dbsql utility provides access to the Berkeley DB SQL interface. See - <a class="xref" href="build_unix_sql.html" title="Configuring the SQL Interface">Configuring the SQL Interface</a> - for more information. - </p> + <span class="bold"><strong>--enable-sql</strong></span> + </p> + <p> + To build the command tool dbsql, enter --enable-sql + as an argument to configure. The dbsql utility + provides access to the Berkeley DB SQL interface. See + <a class="xref" href="build_unix_sql.html" title="Configuring the SQL Interface">Configuring the SQL + Interface</a> for more + information. + </p> </li> <li> <p> - <span class="bold"><strong>--enable-sql_compat</strong></span> - </p> - <p> - To build the command tool sqlite3, enter --enable-sql_compat as an argument to configure. Sqlite3 is a command line tool that enables you to manually enter and execute SQL -commands. It is identical to the dbsql executable but named so that existing scripts for SQLite can easily work with Berkeley DB. See - <a class="xref" href="build_unix_sql.html" title="Configuring the SQL Interface">Configuring the SQL Interface</a> - for more information. - </p> + <span class="bold"><strong>--enable-sql_compat</strong></span> + </p> + <p> + To build the command tool sqlite3, enter + --enable-sql_compat as an argument to configure. + Sqlite3 is a command line tool that enables you to + manually enter and execute SQL commands. It is + identical to the dbsql executable but named so that + existing scripts for SQLite can easily work with + Berkeley DB. See <a class="xref" href="build_unix_sql.html" title="Configuring the SQL Interface">Configuring the SQL + Interface</a> for more + information. + </p> </li> <li> <p> - <span class="bold"><strong>--enable-sql_codegen</strong></span> - </p> - <p> - To build the command line tool db_sql_codegen, enter --enable-sql_codegen as an argument to configure. - The db_sql_codegen utility translates a schema description written in a SQL Data Definition Language dialect into C code that implements the schema using Berkeley DB. - </p> + <span class="bold"><strong>--enable-sql_codegen</strong></span> + </p> + <p> + To build the command line tool db_sql_codegen, + enter --enable-sql_codegen as an argument to + configure. The db_sql_codegen utility translates a + schema description written in a SQL Data Definition + Language dialect into C code that implements the + schema using Berkeley DB. + </p> </li> <li> <p> - <span class="bold"><strong>--enable-smallbuild</strong></span> - </p> - <p> - To build a small memory footprint version of the Berkeley DB - library, enter --enable-smallbuild as an argument to configure. - The --enable-smallbuild argument is equivalent to individually - specifying --with-cryptography=no, --disable-hash, - --disable-queue, --disable-replication, --disable-statistics - and --disable-verify, turning off cryptography support, the - Hash and Queue access methods, database environment replication - support and database and log verification support. See - <a class="xref" href="build_unix_small.html" title="Building a small memory footprint library">Building a small memory footprint library</a> - for more information. - </p> + <span class="bold"><strong>--enable-smallbuild</strong></span> + </p> + <p> + To build a small memory footprint version of the + Berkeley DB library, enter --enable-smallbuild as an + argument to configure. The --enable-smallbuild + argument is equivalent to individually specifying + --with-cryptography=no, --disable-hash, + --disable-heap, --disable-queue, + --disable-replication, --disable-statistics and + --disable-verify, turning off cryptography support, + the Hash, Heap and Queue access methods, database + environment replication support and database and log + verification support. See <a class="xref" href="build_unix_small.html" title="Building a small memory footprint library">Building a small memory footprint library</a> for more + information. + </p> </li> <li> <p> - <span class="bold"><strong>--enable-stl</strong></span> - </p> - <p> - To build the Berkeley DB C++ STL API, enter --enable-stl as an - argument to configure. Setting this argument implies that --enable-cxx is set, - and the Berkeley DB C++ API will be built too. - - </p> - <p> - There will be a libdb_stl-X.X.a and libdb_stl-X.X.so - built, which are the static and shared library you should link your application with in order to - make use of Berkeley DB via its STL API. - - </p> - <p> - If your compiler is not ISO C++ compliant, the configure may fail with this argument - specified because the STL API requires standard C++ template features. In this case, - you will need a standard C++ compiler. So far gcc is the best choice, we have tested and found - that gcc-3.4.4 and all its newer versions can build the Berkeley DB C++ STL API successfully. - </p> - <p>For information on db_stl supported compilers, see the <a href="../programmer_reference/stl.html#stl_intro_portability" class="olink">Portability section</a> in the <span class="emphasis"><em>Programmer's Reference Guide</em></span>.</p> - <p> -And you need to include the STL API header files in your application code. -If you are using the Berkeley DB source tree, the header files are in <Berkeley DB Source Root >/stl directory; -If you -are using the installed version, these header files are in < Berkeley DB Installed Directory>/include, as well as the -db.h and db_cxx.h header files. -</p> + <span class="bold"><strong>--enable-stl</strong></span> + </p> + <p> + To build the Berkeley DB C++ STL API, enter + --enable-stl as an argument to configure. Setting this + argument implies that --enable-cxx is set, and the + Berkeley DB C++ API will be built too. + </p> + <p> + There will be a libdb_stl-X.X.a and + libdb_stl-X.X.so built, which are the static and + shared library you should link your application with + in order to make use of Berkeley DB via its STL API. + </p> + <p> + If your compiler is not ISO C++ compliant, the + configure may fail with this argument specified + because the STL API requires standard C++ template + features. In this case, you will need a standard C++ + compiler. So far gcc is the best choice, we have + tested and found that gcc-3.4.4 and all its newer + versions can build the Berkeley DB C++ STL API + successfully. + </p> + <p> + For information on db_stl supported compilers, see + the <a href="../programmer_reference/stl.html#stl_intro_portability" class="olink">Portability + section</a> in the <span class="emphasis"><em>Programmer's + Reference Guide</em></span>. + </p> + <p> + And you need to include the STL API header files in + your application code. If you are using the Berkeley + DB source tree, the header files are in <Berkeley + DB Source Root >/stl directory; If you are using + the installed version, these header files are in < + Berkeley DB Installed Directory>/include, as well + as the db.h and db_cxx.h header files. + </p> </li> <li> <p> - <span class="bold"><strong>--enable-tcl</strong></span> - </p> - <p> - To build the Berkeley DB Tcl API, enter --enable-tcl as an - argument to configure. This configuration argument expects to - find Tcl's tclConfig.sh file in the - <code class="filename">/usr/local/lib</code> directory. See the - --with-tcl argument for instructions on specifying a - non-standard location for the Tcl installation. See - <a href="../programmer_reference/tcl.html#tcl_intro" class="olink">Loading Berkeley DB with Tcl</a> for information on sites from which you can - download Tcl and which Tcl versions are compatible with - Berkeley DB. To build Tcl, you must also build with shared - libraries. - </p> + <span class="bold"><strong>--enable-tcl</strong></span> + </p> + <p> + To build the Berkeley DB Tcl API, enter + --enable-tcl as an argument to configure. This + configuration argument expects to find Tcl's + tclConfig.sh file in the + <code class="filename">/usr/local/lib</code> directory. See + the --with-tcl argument for instructions on specifying + a non-standard location for the Tcl installation. See + <a href="../programmer_reference/tcl.html#tcl_intro" class="olink">Loading Berkeley DB with Tcl</a> for information on sites from which you + can download Tcl and which Tcl versions are compatible + with Berkeley DB. To build Tcl, you must also build + with shared libraries. + </p> </li> <li> <p><a id="build_unix_conf.--enable-test"></a> - <span class="bold"><strong>--enable-test</strong></span> - </p> - <p> - To build the Berkeley DB test suite, enter --enable-test as an - argument to configure. To run the Berkeley DB test suite, you - must also build the Tcl API. This argument should not be - specified when configuring to build production binaries. - </p> + <span class="bold"><strong>--enable-test</strong></span> + </p> + <p> + To build the Berkeley DB test suite, enter + --enable-test as an argument to configure. To run the + Berkeley DB test suite, you must also build the Tcl + API. This argument should not be specified when + configuring to build production binaries. + </p> </li> <li> <p><a id="build_unix_conf.--enable-uimutexes"></a> - <span class="bold"><strong>--enable-uimutexes</strong></span> - </p> - <p> - To force Berkeley DB to use the UNIX International (UI) mutex - interfaces for underlying mutex support, enter - --enable-uimutexes as an argument to configure. This is rarely - necessary: UI mutexes will be selected automatically on systems - where they are the preferred implementation. - </p> - <p> - The --enable-uimutexes configuration argument is normally used - when there are multiple mutex implementations available and the - UI mutex implementation is not the preferred one (for example, - on Solaris where the LWP mutexes are used by default). - </p> - <p> - Specifying the --enable-uimutexes configuration argument may - require that applications and Berkeley DB be linked with the - -lthread library. - </p> + <span class="bold"><strong>--enable-uimutexes</strong></span> + </p> + <p> + To force Berkeley DB to use the UNIX International + (UI) mutex interfaces for underlying mutex support, + enter --enable-uimutexes as an argument to configure. + This is rarely necessary: UI mutexes will be selected + automatically on systems where they are the preferred + implementation. + </p> + <p> + The --enable-uimutexes configuration argument is + normally used when there are multiple mutex + implementations available and the UI mutex + implementation is not the preferred one (for example, + on Solaris where the LWP mutexes are used by default). + </p> + <p> + Specifying the --enable-uimutexes configuration + argument may require that applications and Berkeley DB + be linked with the -lthread library. + </p> </li> <li> <p><a id="build_unix_conf.--enable-umrw"></a> - <span class="bold"><strong>--enable-umrw</strong></span> - </p> - <p> - Rational Software's Purify product and other run-time tools - complain about uninitialized reads/writes of structure fields - whose only purpose is padding, as well as when heap memory that - was never initialized is written to disk. Specify the - --enable-umrw argument during configuration to mask these - errors. This argument should not be specified when configuring - to build production binaries. - </p> + <span class="bold"><strong>--enable-umrw</strong></span> + </p> + <p> + Rational Software's Purify product and other + run-time tools complain about uninitialized + reads/writes of structure fields whose only purpose is + padding, as well as when heap memory that was never + initialized is written to disk. Specify the + --enable-umrw argument during configuration to mask + these errors. This argument should not be specified + when configuring to build production binaries. + </p> </li> <li> <p><a id="build_unix_conf.--enable-dtrace"></a> - <span class="bold"><strong>--enable-dtrace</strong></span> - [<span class="bold"><strong>--enable-perfmon-statistics</strong></span>] - </p> - <p> - To build Berkeley DB with performance event monitoring probes - add --enable-dtrace to the configuration options. Both native - DTrace (on Solaris and Mac OS X) and the - Statically Defined Tracing compatibility layer - in Linux SystemTap version 1.1 or better are supported. - That compatibility package may be called systemtap-sdt-devel; - it includes <code class="filename">sys/sdt.h</code>. - </p> - <p> - If --enable-perfmon-statistics is combined with --enable-dtrace - then additional probes are defined for the tracking variables - from which DB's statistics are obtained. - They allow DTrace and SystemTap access to these values when - they are updated, are the basis of the statistics - as displayed db_stat and the API functions that return statistics. - </p> - <p> - The --enable-dtrace option may not be specified at the same time - as --disable-statistics. - </p> - <p> - For information on Berkeley DB Performance Event Monitoring, - see the - <a href="../programmer_reference/program_perfmon.html" class="olink">Performance Event Monitoring</a> - section in the - <span class="emphasis"><em>Programmer's Reference Guide</em></span>. - </p> + <span class="bold"><strong>--enable-dtrace</strong></span> + [<span class="bold"><strong>--enable-perfmon-statistics</strong></span>] + </p> + <p> + To build Berkeley DB with performance event + monitoring probes add --enable-dtrace to the + configuration options. Both native DTrace (on Solaris + and Mac OS X) and the Statically Defined Tracing + compatibility layer in Linux SystemTap version 1.1 or + better are supported. That compatibility package may + be called systemtap-sdt-devel; it includes + <code class="filename">sys/sdt.h</code>. + </p> + <p> + If --enable-perfmon-statistics is combined with + --enable-dtrace then additional probes are defined for + the tracking variables from which DB's statistics are + obtained. They allow DTrace and SystemTap access to + these values when they are updated, are the basis of + the statistics as displayed db_stat and the API + functions that return statistics. + </p> + <p> + The --enable-dtrace option may not be specified at + the same time as --disable-statistics. + </p> + <p> + For information on Berkeley DB Performance Event + Monitoring, see the <a href="../programmer_reference/program_perfmon.html" class="olink">Performance Event + Monitoring</a> section in the + <span class="emphasis"><em>Programmer's Reference Guide</em></span>. + </p> </li> <li> <p><a id="build_unix_conf.--enable-localization"></a> - <span class="bold"><strong>--enable-localization</strong></span> - </p> - <p> - Enable localized error message text, if available. - This option should not be used when - <code class="literal">--enable-stripped_messages</code> - is in use. - </p> + <span class="bold"><strong>--enable-localization</strong></span> + </p> + <p> + Enable localized error message text, if available. + This option should not be used when + <code class="literal">--enable-stripped_messages</code> is + in use. + </p> </li> <li> <p><a id="build_unix_conf.--enable-stripped_messages"></a> - <span class="bold"><strong>--enable-stripped_messages</strong></span> - </p> - <p> - Causes all error messages to be stripped of their textual - information. Instead, only error return codes are used. This - option should not be used when - <code class="literal">--enable-localization</code> - is in use. Use of this build option can reduce your library - foot print by up to 44KB (.so) or 50KB (.a). - </p> - <p> - If you use this configuration option, you can get an idea of - what text should be issued for a given error message by using - the <a href="../articles/mssgtxt/index.html" class="olink">Message - Reference for Stripped Libraries</a> guide. - </p> + <span class="bold"><strong>--enable-stripped_messages</strong></span> + </p> + <p> + Causes all error messages to be stripped of their + textual information. Instead, only error return codes + are used. This option should not be used when + <code class="literal">--enable-localization</code> is in + use. Use of this build option can reduce your library + foot print by up to 44KB (.so) or 50KB (.a). + </p> + <p> + If you use this configuration option, you can get + an idea of what text should be issued for a given + error message by using the <a href="../articles/mssgtxt/index.html" class="olink">Berkeley DB Message Reference Guide</a>. + </p> </li> <li> <p><a id="build_unix_conf.--with-cryptography"></a> - <span class="bold"><strong>--with-cryptography</strong></span> - </p> - <p> - To build Berkeley DB with support for cryptography, enter --with-cryptography=yes as an argument to configure. - </p> - <p>To build Berkeley DB without support for cryptography, enter --with-cryptography=no as an argument to configure. - </p> - <p>To build Berkeley DB with support for cryptography using Intel's Performance Primitive (IPP) library, enter --with-cryptography=ipp as an argument to configure. Additionally, set the following arguments:</p> - <p>-L/path/to/ipp/sharedlib to LDFLAGS</p> - <p>-I/path/to/ipp/include to CPPFLAGS</p> - <p>-lippcpem64t -lpthread to LIBS</p> - <p> An example configuration command for IPP encryption is as follows:</p> - <p></p> + <span class="bold"><strong>--with-cryptography</strong></span> + </p> + <p> + Enter <code class="literal">--with-cryptography=yes|no</code> + to build Berkeley DB libraries with or without + cryptography support. By default, cryptography is + enabled for Berkeley DB base libraries, and disabled + when building the optional Berkeley DB SQL and JDBC + libraries. + </p> + <p> + To build Berkeley DB with support for cryptography + using Intel's Performance Primitive (IPP) library, + enter <code class="literal">--with-cryptography=ipp</code> as an + argument to configure. Additionally, set the following + arguments: + </p> + <div class="itemizedlist"> + <ul type="circle"> + <li> + <p> + -L/path/to/ipp/sharedlib to LDFLAGS + </p> + </li> + <li> + <p> + -I/path/to/ipp/include to CPPFLAGS + </p> + </li> + <li> + <p> + -lippcpem64t -lpthread to LIBS + </p> + </li> + </ul> + </div> + <p> + An example configuration command for IPP encryption + is as follows: + </p> <pre class="programlisting"> ../dist/configure -with-cryptography=ipp CPPFLAGS="-I/opt/intel/ipp/6.1.3.055/em64t/include" LDFLAGS="-L/opt/intel/ipp/6.1.3.055/em64t/sharedlib" LIBS="-lippcpem64t -lpthread"</pre> - <p>See the<a class="ulink" href="http://software.intel.com/en-us/articles/intel-integrated-performance-primitives-documentation/" target="_top"> Intel Documenation</a> for specific instructions on configuring environment variables.</p> - <p>Note: The --with-cryptography=ipp argument works only on Linux.</p> + <p> + See the <a class="ulink" href="https://software.intel.com/en-us/articles/intel-integrated-performance-primitives-documentation/" target="_top"> + Intel Documentation</a> for specific + instructions on configuring environment variables. + </p> + <p> + Note: The <code class="literal">--with-cryptography=ipp</code> + argument works only on Linux. + </p> </li> <li> <p><a id="build_unix_conf.--with-mutex"></a> - <span class="bold"><strong>--with-mutex=MUTEX</strong></span> - </p> - <p> - To force Berkeley DB to use a specific mutex implementation, - configure with --with-mutex=MUTEX, where MUTEX is the mutex - implementation you want. For example, - --with-mutex=x86/gcc-assembly will configure Berkeley DB to use - the x86 GNU gcc compiler based test-and-set assembly mutexes. - This is rarely necessary and should be done only when the - default configuration selects the wrong mutex implementation. - A list of available mutex implementations can be found in the - distribution file <code class="filename">dist/aclocal/mutex.m4</code>. - </p> + <span class="bold"><strong>--with-mutex=MUTEX</strong></span> + </p> + <p> + To force Berkeley DB to use a specific mutex + implementation, configure with --with-mutex=MUTEX, + where MUTEX is the mutex implementation you want. For + example, --with-mutex=x86/gcc-assembly will configure + Berkeley DB to use the x86 GNU gcc compiler based + test-and-set assembly mutexes. This is rarely + necessary and should be done only when the default + configuration selects the wrong mutex implementation. + A list of available mutex implementations can be found + in the distribution file + <code class="filename">dist/aclocal/mutex.m4</code>. + </p> </li> <li> <p> - <span class="bold"><strong>--with-tcl=DIR</strong></span> - </p> - <p> - To build the Berkeley DB Tcl API, enter --with-tcl=DIR, - replacing DIR with the directory in which the Tcl tclConfig.sh - file may be found. See <a href="../programmer_reference/tcl.html#tcl_intro" class="olink">Loading Berkeley DB with Tcl</a> for information on sites from - which you can download Tcl and which Tcl versions are - compatible with Berkeley DB. To build Tcl, you must also build - with shared libraries. - </p> + <span class="bold"><strong>--with-tcl=DIR</strong></span> + </p> + <p> + To build the Berkeley DB Tcl API, enter + --with-tcl=DIR, replacing DIR with the directory in + which the Tcl tclConfig.sh file may be found. See + <a href="../programmer_reference/tcl.html#tcl_intro" class="olink">Loading Berkeley DB with Tcl</a> for information on sites from which you + can download Tcl and which Tcl versions are compatible + with Berkeley DB. To build Tcl, you must also build + with shared libraries. + </p> </li> <li> <p><a id="build_unix_conf.--with-uniquename=NAME"></a> - <span class="bold"><strong>--with-uniquename=NAME</strong></span> - </p> - <p> - To build Berkeley DB with unique symbol names (in order to - avoid conflicts with other application modules or libraries), - enter --with-uniquename=NAME, replacing NAME with a string that - to be appended to every Berkeley DB symbol. If "=NAME" is not - specified, a default value of "_MAJORMINOR" is used, where - MAJORMINOR is the major and minor release numbers of the - Berkeley DB release. See <a class="xref" href="install_multiple.html" title="Building with multiple versions of Berkeley DB">Building with multiple versions of Berkeley DB</a> for more information. - </p> + <span class="bold"><strong>--with-uniquename=NAME</strong></span> + </p> + <p> + To build Berkeley DB with unique symbol names (in + order to avoid conflicts with other application + modules or libraries), enter --with-uniquename=NAME, + replacing NAME with a string that to be appended to + every Berkeley DB symbol. If "=NAME" is not specified, + a default value of "_MAJORMINOR" is used, where + MAJORMINOR is the major and minor release numbers of + the Berkeley DB release. See <a class="xref" href="install_multiple.html" title="Building with multiple versions of Berkeley DB">Building with multiple versions of Berkeley DB</a> for more + information. + </p> </li> </ul> </div> @@ -542,13 +680,13 @@ db.h and db_cxx.h header files. <td width="40%" align="right"> <a accesskey="n" href="build_unix_sql.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </td> + <td width="40%" align="left" valign="top">Chapter 7. Building Berkeley DB for UNIX/POSIX + </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Configuring the SQL Interface</td> + <td width="40%" align="right" valign="top"> Configuring the SQL + Interface</td> </tr> </table> </div> diff --git a/docs/installation/build_unix_db_nosync.html b/docs/installation/build_unix_db_nosync.html index 74990a81..62743e48 100644 --- a/docs/installation/build_unix_db_nosync.html +++ b/docs/installation/build_unix_db_nosync.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> <link rel="prev" href="build_unix_encrypt.html" title="Cryptography Support" /> <link rel="next" href="upgrade_11gr2_remsupp.html" title="Dropped Support" /> </head> <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="build_unix_encrypt.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </th> + <th width="60%" align="center">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_remsupp.html">Next</a></td> </tr> </table> @@ -38,12 +36,23 @@ </div> </div> </div> - <p>Applications must now pass the DB_NOSYNC flag to the methods - <code class="literal">DB->remove</code>, <code class="literal">DB->rename</code>, <code class="literal">DB_ENV->dbremove</code>, and <code class="literal">DB_ENV->dbrename</code>, to avoid a multi-database file to be flushed from cache. -This flag is applicable if you have created the database handle in a non-transactional environment. -</p> - <p>By default, all non-transactional database remove/rename operations cause data to be synced to disk. -This can now be overridden using the DB_NOSYNC flag so that files can be accessed outside the environment after the database handles are closed. -</p> + <p> + Applications must now pass the DB_NOSYNC flag to the methods + - <code class="literal">DB->remove</code>, + <code class="literal">DB->rename</code>, + <code class="literal">DB_ENV->dbremove</code>, and + <code class="literal">DB_ENV->dbrename</code>, to avoid a + multi-database file to be flushed from cache. This flag is + applicable if you have created the database handle in a + non-transactional environment. + </p> + <p> + By default, all non-transactional database remove/rename + operations cause data to be synced to disk. This can now be + overridden using the DB_NOSYNC flag so that files can be + accessed outside the environment after the database handles + are closed. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/build_unix_encrypt.html b/docs/installation/build_unix_encrypt.html index 196881fd..500163fb 100644 --- a/docs/installation/build_unix_encrypt.html +++ b/docs/installation/build_unix_encrypt.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> <link rel="prev" href="upgrade_11gr2_repmgr.html" title="Support for Multiple Client-to-Client Peers" /> <link rel="next" href="build_unix_db_nosync.html" title="DB_NOSYNC Flag to Flush Files" /> </head> <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="upgrade_11gr2_repmgr.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </th> + <th width="60%" align="center">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_db_nosync.html">Next</a></td> </tr> </table> @@ -38,15 +36,34 @@ </div> </div> </div> - <p>In this release, the configuration options, --disable-cryptography and --enable-cryptography are deprecated. --disable-cryptography is replaced by --with-cryptography=no and --enable-cryptography is replaced by --with-cryptography=yes. -</p> - <p>To build Berkeley DB with support for cryptography, enter --with-cryptography=yes as an argument to configure instead of --enable-cryptography. -</p> - <p> To build Berkeley DB without support for cryptography, enter --with-cryptography=no as an argument to configure instead of --disable-cryptography. -</p> - <p>Berkeley DB now supports encryption using Intel's Performance Primitive (IPP) on Linux. To build Berkeley DB with support for cryptography using Intel's Performance Primitive (IPP) library, enter --with-cryptography=ipp as an argument to configure. -</p> - <p>Note: The --with-cryptography=ipp argument works only on Linux.</p> + <p> + In this release, the configuration options, + --disable-cryptography and --enable-cryptography are + deprecated. --disable-cryptography is replaced by + --with-cryptography=no and --enable-cryptography is replaced + by --with-cryptography=yes. + </p> + <p> + To build Berkeley DB with support for cryptography, enter + --with-cryptography=yes as an argument to configure instead of + --enable-cryptography. + </p> + <p> + To build Berkeley DB without support for cryptography, + enter --with-cryptography=no as an argument to configure + instead of --disable-cryptography. + </p> + <p> + Berkeley DB now supports encryption using Intel's + Performance Primitive (IPP) on Linux. To build Berkeley DB + with support for cryptography using Intel's Performance + Primitive (IPP) library, enter --with-cryptography=ipp as an + argument to configure. + </p> + <p> + Note: The --with-cryptography=ipp argument works only on + Linux. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/build_unix_flags.html b/docs/installation/build_unix_flags.html index 974dc7b4..6f08e9ac 100644 --- a/docs/installation/build_unix_flags.html +++ b/docs/installation/build_unix_flags.html @@ -14,17 +14,17 @@ <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">Changing compile or load options</th> + <th colspan="3" align="center">Changing compile or load + options</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_small.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="cross_compile_unix.html">Next</a></td> </tr> </table> @@ -34,49 +34,79 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_unix_flags"></a>Changing compile or load options</h2> + <h2 class="title" style="clear: both"><a id="build_unix_flags"></a>Changing compile or load + options</h2> </div> </div> </div> - <p>You can specify compiler and/or compile and load time flags by using -environment variables during Berkeley DB configuration. For -example, if you want to use a specific compiler, specify the CC -environment variable before running configure:</p> + <p> + You can specify compiler and/or compile and load time flags + by using environment variables during Berkeley DB + configuration. For example, if you want to use a specific + compiler, specify the CC environment variable before running + configure: + </p> <pre class="programlisting">prompt: env CC=gcc ../dist/configure</pre> - <p>Using anything other than the native compiler will almost certainly mean -that you'll want to check the flags specified to the compiler and -loader, too.</p> - <p>To specify debugging and optimization options for the C compiler, -use the CFLAGS environment variable:</p> + <p> + Using anything other than the native compiler will almost + certainly mean that you'll want to check the flags specified + to the compiler and loader, too. + </p> + <p> + To specify debugging and optimization options for the C + compiler, use the CFLAGS environment variable: + </p> <pre class="programlisting">prompt: env CFLAGS=-O2 ../dist/configure</pre> - <p>To specify header file search directories and other miscellaneous options -for the C preprocessor and compiler, use the CPPFLAGS environment variable:</p> + <p> + To specify header file search directories and other + miscellaneous options for the C preprocessor and compiler, use + the CPPFLAGS environment variable: + </p> <pre class="programlisting">prompt: env CPPFLAGS=-I/usr/contrib/include ../dist/configure</pre> - <p>To specify debugging and optimization options for the C++ compiler, -use the CXXFLAGS environment variable:</p> + <p> + To specify debugging and optimization options for the C++ + compiler, use the CXXFLAGS environment variable: + </p> <pre class="programlisting">prompt: env CXXFLAGS=-Woverloaded-virtual ../dist/configure</pre> - <p>To specify miscellaneous options or additional library directories for -the linker, use the LDFLAGS environment variable:</p> + <p> + To specify miscellaneous options or additional library + directories for the linker, use the LDFLAGS environment + variable: + </p> <pre class="programlisting">prompt: env LDFLAGS="-N32 -L/usr/local/lib" ../dist/configure</pre> - <p>If you want to specify additional libraries, set the LIBS environment -variable before running configure. For example, the following would -specify two additional libraries to load, "posix" and "socket":</p> + <p> + If you want to specify additional libraries, set the LIBS + environment variable before running configure. For example, + the following would specify two additional libraries to load, + "posix" and "socket": + </p> <pre class="programlisting">prompt: env LIBS="-lposix -lsocket" ../dist/configure</pre> - <p>Make sure that you prepend -L to any library directory names and that you -prepend -I to any include file directory names! Also, if the arguments -you specify contain blank or tab characters, be sure to quote them as -shown previously; that is with single or double quotes around the values -you are specifying for LIBS.</p> - <p>The env command, which is available on most systems, simply sets one or -more environment variables before running a command. If the env command -is not available to you, you can set the environment variables in your -shell before running configure. For example, in sh or ksh, you could -do the following:</p> + <p> + Make sure that you prepend -L to any library directory + names and that you prepend -I to any include file directory + names! Also, if the arguments you specify contain blank or tab + characters, be sure to quote them as shown previously; that is + with single or double quotes around the values you are + specifying for LIBS. + </p> + <p> + The env command, which is available on most systems, simply + sets one or more environment variables before running a + command. If the env command is not available to you, you can + set the environment variables in your shell before running + configure. For example, in sh or ksh, you could do the + following: + </p> <pre class="programlisting">prompt: LIBS="-lposix -lsocket" ../dist/configure</pre> - <p>In csh or tcsh, you could do the following:</p> + <p> + In csh or tcsh, you could do the following: + </p> <pre class="programlisting">prompt: setenv LIBS "-lposix -lsocket" prompt: ../dist/configure</pre> - <p>See your command shell's manual page for further information.</p> + <p> + See your command shell's manual page for further + information. + </p> </div> <div class="navfooter"> <hr /> @@ -93,7 +123,8 @@ prompt: ../dist/configure</pre> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Cross-Compiling on Unix</td> + <td width="40%" align="right" valign="top"> Cross-Compiling on + Unix</td> </tr> </table> </div> diff --git a/docs/installation/build_unix_freebsd.html b/docs/installation/build_unix_freebsd.html index 191d36cb..59ce6abf 100644 --- a/docs/installation/build_unix_freebsd.html +++ b/docs/installation/build_unix_freebsd.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_aix.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_iphone.html">Next</a></td> </tr> </table> @@ -42,23 +41,35 @@ <ol type="1"> <li> <span class="bold"> - <strong>I can't compile and run multithreaded applications.</strong> + <strong>I can't compile and run + multithreaded applications.</strong> </span> - <p>Special compile-time flags are required when compiling threaded -applications on FreeBSD. If you are compiling a threaded application, -you must compile with the _THREAD_SAFE and -pthread flags:</p> + <p> + Special compile-time flags are required when + compiling threaded applications on FreeBSD. If you are + compiling a threaded application, you must compile + with the _THREAD_SAFE and -pthread flags: + </p> <pre class="programlisting">cc -D_THREAD_SAFE -pthread ...</pre> - <p>The Berkeley DB library will automatically build with the correct options.</p> + <p> + The Berkeley DB library will automatically build + with the correct options. + </p> </li> <li> <span class="bold"> - <strong>I see fsync and close system call failures when accessing -databases or log files on NFS-mounted filesystems.</strong> + <strong>I see fsync and close system call + failures when accessing databases or log files on + NFS-mounted filesystems.</strong> </span> - <p>Some FreeBSD releases are known to return ENOLCK from fsync and close -calls on NFS-mounted filesystems, even though the call has succeeded. -The Berkeley DB code should be modified to ignore ENOLCK errors, or no Berkeley DB -files should be placed on NFS-mounted filesystems on these systems.</p> + <p> + Some FreeBSD releases are known to return ENOLCK + from fsync and close calls on NFS-mounted filesystems, + even though the call has succeeded. The Berkeley DB + code should be modified to ignore ENOLCK errors, or no + Berkeley DB files should be placed on NFS-mounted + filesystems on these systems. + </p> </li> </ol> </div> diff --git a/docs/installation/build_unix_install.html b/docs/installation/build_unix_install.html index b623e8c1..e0893529 100644 --- a/docs/installation/build_unix_install.html +++ b/docs/installation/build_unix_install.html @@ -14,17 +14,17 @@ <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">Installing Berkeley DB</th> + <th colspan="3" align="center">Installing Berkeley + DB</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="cross_compile_unix.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_shlib.html">Next</a></td> </tr> </table> @@ -34,12 +34,15 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_unix_install"></a>Installing Berkeley DB</h2> + <h2 class="title" style="clear: both"><a id="build_unix_install"></a>Installing Berkeley + DB</h2> </div> </div> </div> - <p>Berkeley DB installs the following files into the following locations, -with the following default values:</p> + <p> + Berkeley DB installs the following files into the following + locations, with the following default values: + </p> <div class="informaltable"> <table border="1" width="80%"> <colgroup> @@ -112,33 +115,51 @@ with the following default values:</p> </tbody> </table> </div> - <p>With one exception, this follows the GNU Autoconf and GNU Coding -Standards installation guidelines; please see that documentation for -more information and rationale.</p> - <p>The single exception is the Berkeley DB documentation. The -Berkeley DB documentation is provided in HTML format, not in -UNIX-style man or GNU info format. For this reason, Berkeley DB -configuration does not support <span class="bold"><strong>--infodir</strong></span> or <span class="bold"><strong>--mandir</strong></span>. -To change the default installation location for the Berkeley DB -documentation, modify the Makefile variable, <span class="bold"><strong>docdir</strong></span>.</p> - <p>When installing Berkeley DB on filesystems shared by machines of -different architectures, please note that although Berkeley DB -include files are installed based on the value of $(prefix), rather than -$(exec_prefix), the Berkeley DB include files are not always -architecture independent.</p> - <p>To move the entire installation tree to somewhere besides -<span class="bold"><strong>/usr/local</strong></span>, change the value of <span class="bold"><strong>prefix</strong></span>.</p> - <p>To move the binaries and libraries to a different location, change the -value of <span class="bold"><strong>exec_prefix</strong></span>. The values of <span class="bold"><strong>includedir</strong></span> and -<span class="bold"><strong>libdir</strong></span> may be similarly changed.</p> - <p>Any of these values except for <span class="bold"><strong>docdir</strong></span> may be set as part of -the configuration:</p> + <p> + With one exception, this follows the GNU Autoconf and GNU + Coding Standards installation guidelines; please see that + documentation for more information and rationale. + </p> + <p> + The single exception is the Berkeley DB documentation. The + Berkeley DB documentation is provided in HTML format, not in + UNIX-style man or GNU info format. For this reason, Berkeley + DB configuration does not support <span class="bold"><strong>--infodir</strong></span> + or <span class="bold"><strong>--mandir</strong></span>. To change the default installation + location for the Berkeley DB documentation, modify the + Makefile variable, <span class="bold"><strong>docdir</strong></span>. + </p> + <p> + When installing Berkeley DB on filesystems shared by + machines of different architectures, please note that although + Berkeley DB include files are installed based on the value of + $(prefix), rather than $(exec_prefix), the Berkeley DB include + files are not always architecture independent. + </p> + <p> + To move the entire installation tree to somewhere besides + <span class="bold"><strong>/usr/local</strong></span>, change the + value of <span class="bold"><strong>prefix</strong></span>. + </p> + <p> + To move the binaries and libraries to a different location, + change the value of <span class="bold"><strong>exec_prefix</strong></span>. The + values of <span class="bold"><strong>includedir</strong></span> and <span class="bold"><strong>libdir</strong></span> may be similarly changed. + </p> + <p> + Any of these values except for <span class="bold"><strong>docdir</strong></span> + may be set as part of the configuration: + </p> <pre class="programlisting">prompt: ../dist/configure --bindir=/usr/local/bin</pre> - <p>Any of these values, including <span class="bold"><strong>docdir</strong></span>, may be changed when doing -the install itself:</p> + <p> + Any of these values, including <span class="bold"><strong>docdir</strong></span>, + may be changed when doing the install itself: + </p> <pre class="programlisting">prompt: make prefix=/usr/contrib/bdb install</pre> - <p>The Berkeley DB installation process will attempt to create any -directories that do not already exist on the system.</p> + <p> + The Berkeley DB installation process will attempt to create + any directories that do not already exist on the system. + </p> </div> <div class="navfooter"> <hr /> @@ -151,7 +172,8 @@ directories that do not already exist on the system.</p> <td width="40%" align="right"> <a accesskey="n" href="build_unix_shlib.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Cross-Compiling on Unix </td> + <td width="40%" align="left" valign="top">Cross-Compiling on + Unix </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/build_unix_iphone.html b/docs/installation/build_unix_iphone.html index c7c8f303..cb237dc3 100644 --- a/docs/installation/build_unix_iphone.html +++ b/docs/installation/build_unix_iphone.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_freebsd.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_irix.html">Next</a></td> </tr> </table> @@ -38,27 +37,29 @@ </div> </div> </div> - <p> - Building Berkeley DB in Apple iOS (known as iPhone OS previously) - is the same as building for a conventional UNIX platform. This - section lists the commands for building Berkeley DB in both the - iPhone simulator (a software simulator included in the iPhone SDK - that you can use to test your application without using the - iPhone/iPod Touch) and the iPhone device. + <p> + Building Berkeley DB in Apple iOS (known as iPhone OS + previously) is the same as building for a conventional UNIX + platform. This section lists the commands for building + Berkeley DB in both the iPhone simulator (a software simulator + included in the iPhone SDK that you can use to test your + application without using the iPhone/iPod Touch) and the + iPhone device. </p> <p> - Prior to building BDB in an iPhone simulator/iPhone device, set the - required environment variables for iOS (iPhone OS). For a - simulator/iPhone version 4.2 or older, set the LDFLAGS variable as - follows: + Prior to building BDB in an iPhone simulator/iPhone device, + set the required environment variables for iOS (iPhone OS). + For a simulator/iPhone version 4.2 or older, set the LDFLAGS + variable as follows: </p> <pre class="programlisting">export LDFLAGS="-L$SDKROOT/usr/lib/"</pre> <p> Otherwise, set LDFLAGS as follows: </p> <pre class="programlisting">export LDFLAGS="-L$SDKROOT/usr/lib/system/"</pre> - <p> - The steps to build BDB in an iPhone simulator are as follows: + <p> + The steps to build BDB in an iPhone simulator are as + follows: </p> <pre class="programlisting">export CFLAGS="-arch i386 -pipe -no-cpp-precomp --sysroot=$SDKROOT" export CXXFLAGS="-arch i386 -pipe -no-cpp-precomp --sysroot=$SDKROOT" @@ -66,7 +67,7 @@ cd $BDB_HOME/build_unix ../dist/configure --host=i386-apple-darwin\ --prefix=$SDKROOT ... make</pre> - <p> + <p> The steps to build BDB in an iPhone device are as follows: </p> <pre class="programlisting">export CFLAGS="-arch armv6 -pipe -Os -gdwarf-2\ @@ -77,10 +78,12 @@ cd $BDB_HOME/build_unix ../dist/configure --host=arm-apple-darwin9\ --prefix=$SDKROOT ... make</pre> - <p> + <p> Both sets of commands create the BDB dynamic library - - libdb-5.3.dylib. To build the static library, libdb-5.3.a, add the - <code class="literal">--enable-shared=no</code> option while configuring. + libdb-6.1.dylib. To build the static library, + libdb-6.1.a, add the + <code class="literal">--enable-shared=no</code> option while + configuring. </p> </div> <div class="navfooter"> diff --git a/docs/installation/build_unix_irix.html b/docs/installation/build_unix_irix.html index 5a435f4a..d26c9c79 100644 --- a/docs/installation/build_unix_irix.html +++ b/docs/installation/build_unix_irix.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_iphone.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_linux.html">Next</a></td> </tr> </table> @@ -42,13 +41,20 @@ <ol type="1"> <li> <span class="bold"> - <strong>I can't compile and run multithreaded applications.</strong> + <strong>I can't compile and run + multithreaded applications.</strong> </span> - <p>Special compile-time flags are required when compiling threaded -applications on IRIX. If you are compiling a threaded application, you -must compile with the _SGI_MP_SOURCE flag:</p> + <p> + Special compile-time flags are required when + compiling threaded applications on IRIX. If you are + compiling a threaded application, you must compile + with the _SGI_MP_SOURCE flag: + </p> <pre class="programlisting">cc -D_SGI_MP_SOURCE ...</pre> - <p>The Berkeley DB library will automatically build with the correct options.</p> + <p> + The Berkeley DB library will automatically build + with the correct options. + </p> </li> </ol> </div> diff --git a/docs/installation/build_unix_linux.html b/docs/installation/build_unix_linux.html index 60fee2df..870319d9 100644 --- a/docs/installation/build_unix_linux.html +++ b/docs/installation/build_unix_linux.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_irix.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_macosx.html">Next</a></td> </tr> </table> @@ -42,32 +41,48 @@ <ol type="1"> <li> <span class="bold"> - <strong>I can't compile and run multithreaded applications.</strong> + <strong>I can't compile and run + multithreaded applications.</strong> </span> - <p>Special compile-time flags are required when compiling threaded -applications on Linux. If you are compiling a threaded application, you -must compile with the _REENTRANT flag:</p> + <p> + Special compile-time flags are required when + compiling threaded applications on Linux. If you are + compiling a threaded application, you must compile + with the _REENTRANT flag: + </p> <pre class="programlisting">cc -D_REENTRANT ...</pre> - <p>The Berkeley DB library will automatically build with the correct options.</p> + <p> + The Berkeley DB library will automatically build + with the correct options. + </p> </li> <li> <span class="bold"> - <strong>I see database corruption when accessing databases.</strong> + <strong>I see database corruption when + accessing databases.</strong> </span> - <p>Some Linux filesystems do not support POSIX filesystem semantics. -Specifically, ext2 and early releases of ReiserFS, and ext3 in some -configurations, do not support "ordered data mode" and may insert random -data into database or log files when systems crash. Berkeley DB files should -not be placed on a filesystem that does not support, or is not -configured to support, POSIX semantics.</p> + <p> + Some Linux filesystems do not support POSIX + filesystem semantics. Specifically, ext2 and early + releases of ReiserFS, and ext3 in some configurations, + do not support "ordered data mode" and may insert + random data into database or log files when systems + crash. Berkeley DB files should not be placed on a + filesystem that does not support, or is not configured + to support, POSIX semantics. + </p> </li> <li> <span class="bold"> - <strong>What scheduler should I use?</strong> + <strong>What scheduler should I + use?</strong> </span> - <p>In some Linux kernels you can select schedulers, and the default is the -"anticipatory" scheduler. We recommend not using the "anticipatory" -scheduler for transaction processing workloads.</p> + <p> + In some Linux kernels you can select schedulers, + and the default is the "anticipatory" scheduler. We + recommend not using the "anticipatory" scheduler for + transaction processing workloads. + </p> </li> </ol> </div> diff --git a/docs/installation/build_unix_macosx.html b/docs/installation/build_unix_macosx.html index 95f9e868..b600cf5c 100644 --- a/docs/installation/build_unix_macosx.html +++ b/docs/installation/build_unix_macosx.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_linux.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_qnx.html">Next</a></td> </tr> </table> @@ -42,52 +41,71 @@ <ol type="1"> <li> <span class="bold"> - <strong>When trying to link multiple Berkeley DB language interfaces (for -example, Tcl, C++, Java, Python) into a single process, I get "multiple -definitions" errors from dyld.</strong> + <strong>When trying to link multiple + Berkeley DB language interfaces (for example, Tcl, + C++, Java, Python) into a single process, I get + "multiple definitions" errors from dyld.</strong> </span> - <p>To fix this problem, set the environment variable MACOSX_DEPLOYMENT_TARGET -to 10.3 (or your current version of OS X), and reconfigure and rebuild -Berkeley DB from scratch. See the OS X ld(1) and dyld(1) man pages for information -about how OS X handles symbol namespaces, as well as undefined and -multiply-defined symbols.</p> + <p> + To fix this problem, set the environment variable + MACOSX_DEPLOYMENT_TARGET to 10.3 (or your current + version of OS X), and reconfigure and rebuild Berkeley + DB from scratch. See the OS X ld(1) and dyld(1) man + pages for information about how OS X handles symbol + namespaces, as well as undefined and multiply-defined + symbols. + </p> </li> <li> <span class="bold"> - <strong>When trying to use system-backed shared memory on OS X I see -failures about "too many open files".</strong> + <strong>When trying to use system-backed + shared memory on OS X I see failures about "too many + open files".</strong> </span> - <p>The default number of shared memory segments on OS X is too low. To fix -this problem, edit the file /etc/rc, changing the kern.sysv.shmmax and -kern.sysv.shmseg values as follows:</p> - <pre class="programlisting">*** /etc/rc.orig Fri Dec 19 09:34:09 2003 ---- /etc/rc Fri Dec 19 09:33:53 2003 -*************** -*** 84,93 **** - # System tuning - sysctl -w kern.maxvnodes=$(echo $(sysctl -n hw.physmem) '33554432 / -512 * 1024 +p'|dc) -! sysctl -w kern.sysv.shmmax=4194304 - sysctl -w kern.sysv.shmmin=1 - sysctl -w kern.sysv.shmmni=32 -! sysctl -w kern.sysv.shmseg=8 - sysctl -w kern.sysv.shmall=1024 - if [ -f /etc/sysctl-macosxserver.conf ]; then - awk '{ if (!-1 && -1) print $1 }' < -/etc/sysctl-macosxserver.conf | while read ---- 84,93 ---- - # System tuning - sysctl -w kern.maxvnodes=$(echo $(sysctl -n hw.physmem) '33554432 / -512 * 1024 +p'|dc) -! sysctl -w kern.sysv.shmmax=134217728 - sysctl -w kern.sysv.shmmin=1 - sysctl -w kern.sysv.shmmni=32 -! sysctl -w kern.sysv.shmseg=32 - sysctl -w kern.sysv.shmall=1024 - if [ -f /etc/sysctl-macosxserver.conf ]; then - awk '{ if (!-1 && -1) print $1 }' < - /etc/sysctl-macosxserver.conf | while read</pre> - <p>and then reboot the system.</p> + <p> + The default number of shared memory segments on OS + X is too low. To fix this problem, create a file named + <code class="literal">/etc/sysctl.conf</code>, containing the + variable assignments: + </p> + <pre class="programlisting">kern.sysv.shmmax=134217728 +kern.sysv.shmmin=1 +kern.sysv.shmmni=32 +kern.sysv.shmseg=32 +kern.sysv.shmall=1024</pre> + <p> + and then reboot the system. + </p> + <p> + Check the version of OS X carefully because some + versions require all five parameters to be set. + </p> + <p> + The <code class="literal">SHMMAX</code> variable should be set to a value + that is an exact multiple of 4096. Some versions of + OS X ignore the value if it is not an exact multiple. + </p> + <p> + Please check and verify with the OS X documentation + on the proper setting of these parameters. In some + cases a reboot is necessary and in others it is possible + to change them dynamically using <code class="literal">sysctl</code>. + </p> + <p> + The <code class="literal">/etc/sysctl.conf</code> file exists in OS X + 10.3.9 and later. If you are running a version of OS X + previous to 10.3.x, edit the <code class="literal">/etc/rc</code> + file and change the values in the following commands: + </p> + <pre class="programlisting">sysctl -w kern.sysv.shmmax=134217728 +sysctl -w kern.sysv.shmseg=32</pre> + <p> + and then reboot the system. + </p> + <p> + OS X system updates will overwrite <code class="literal">/etc/rc</code> + so any changes to the file must be redone after sytem updates. + </p> </li> </ol> </div> diff --git a/docs/installation/build_unix_notes.html b/docs/installation/build_unix_notes.html index cedab171..8ee7bebc 100644 --- a/docs/installation/build_unix_notes.html +++ b/docs/installation/build_unix_notes.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_test.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_aix.html">Next</a></td> </tr> </table> @@ -42,133 +41,212 @@ <ol type="1"> <li> <span class="bold"> - <strong>I have gcc installed, but configure fails to find it.</strong> + <strong>I have gcc installed, but configure + fails to find it.</strong> </span> - <p>Berkeley DB defaults to using the native C compiler if none is specified. -That is usually "cc", but some platforms require a different compiler -to build multithreaded code. To configure Berkeley DB to build with gcc, run -configure as follows:</p> + <p> + Berkeley DB defaults to using the native C compiler + if none is specified. That is usually "cc", but some + platforms require a different compiler to build + multithreaded code. To configure Berkeley DB to build + with gcc, run configure as follows: + </p> <pre class="programlisting">env CC=gcc ../dist/configure ...</pre> </li> <li> <span class="bold"> - <strong>When compiling with gcc, I get unreferenced symbols; for example -the following: -<pre class="programlisting">symbol __muldi3: referenced symbol not found + <strong>When compiling with gcc, I get + unreferenced symbols; for example the following: + <pre class="programlisting">symbol __muldi3: referenced symbol not found symbol __cmpdi2: referenced symbol not found</pre></strong> </span> - <p>Berkeley DB often uses 64-bit integral types on systems supporting large -files, and gcc performs operations on those types by calling library -functions. These unreferenced symbol errors are usually caused by -linking an application by calling "ld" rather than by calling "gcc": -gcc will link in libgcc.a and will resolve the symbols. If that does -not help, another possible workaround is to reconfigure Berkeley DB using the -<a class="link" href="build_unix_conf.html#build_unix_conf.--disable-largefile">--disable-largefile</a> configuration option and then rebuild.</p> + <p> + Berkeley DB often uses 64-bit integral types on + systems supporting large files, and gcc performs + operations on those types by calling library + functions. These unreferenced symbol errors are + usually caused by linking an application by calling + "ld" rather than by calling "gcc": gcc will link in + libgcc.a and will resolve the symbols. If that does + not help, another possible workaround is to + reconfigure Berkeley DB using the <a class="link" href="build_unix_conf.html#build_unix_conf.--disable-largefile">--disable-largefile</a> + configuration option and then rebuild. + </p> </li> <li> <span class="bold"> - <strong>My C++ program traps during a failure in a DB call on my -gcc-based system.</strong> + <strong>My C++ program traps during a + failure in a DB call on my gcc-based + system.</strong> </span> - <p>We believe there are some severe bugs in the implementation of -exceptions for some gcc compilers. Exceptions require some interaction -between compiler, assembler, and runtime libraries. We're not sure -exactly what is at fault, but one failing combination is gcc 2.7.2.3 -running on SuSE Linux 6.0. The problem on this system can be seen with -a rather simple test case of an exception thrown from a shared library -and caught in the main program.</p> - <p>A variation of this problem seems to occur on AIX, although we believe it -does not necessarily involve shared libraries on that platform.</p> - <p>If you see a trap that occurs when an exception might be thrown by the -Berkeley DB runtime, we suggest that you use static libraries instead of -shared libraries. See the documentation for configuration. If this -doesn't work and you have a choice of compilers, try using a more recent -gcc- or a non-gcc based compiler to build Berkeley DB.</p> - <p>Finally, you can disable the use of exceptions in the C++ runtime for -Berkeley DB by using the <a href="../api_reference/CXX/envcreate.html#env_DB_CXX_NO_EXCEPTIONS" class="olink">DB_CXX_NO_EXCEPTIONS</a> flag with the <a href="../api_reference/CXX/env.html" class="olink">DbEnv</a> or <a href="../api_reference/CXX/db.html" class="olink">Db</a> constructors. When this flag is on, all C++ methods fail by returning an error code rather than throwing an exception.</p> + <p> + We believe there are some severe bugs in the + implementation of exceptions for some gcc compilers. + Exceptions require some interaction between compiler, + assembler, and runtime libraries. We're not sure + exactly what is at fault, but one failing combination + is gcc 2.7.2.3 running on SuSE Linux 6.0. The problem + on this system can be seen with a rather simple test + case of an exception thrown from a shared library and + caught in the main program. + </p> + <p> + A variation of this problem seems to occur on AIX, + although we believe it does not necessarily involve + shared libraries on that platform. + </p> + <p> + If you see a trap that occurs when an exception + might be thrown by the Berkeley DB runtime, we suggest + that you use static libraries instead of shared + libraries. See the documentation for configuration. If + this doesn't work and you have a choice of compilers, + try using a more recent gcc- or a non-gcc based + compiler to build Berkeley DB. + </p> + <p> + Finally, you can disable the use of exceptions in + the C++ runtime for Berkeley DB by using the + <a href="../api_reference/CXX/envcreate.html#env_DB_CXX_NO_EXCEPTIONS" class="olink">DB_CXX_NO_EXCEPTIONS</a> flag with the <a href="../api_reference/CXX/env.html" class="olink">DbEnv</a> + or <a href="../api_reference/CXX/db.html" class="olink">Db</a> constructors. When this flag is on, + all C++ methods fail by returning an error code rather + than throwing an exception. + </p> </li> <li> <span class="bold"> - <strong>I get unexpected results and database corruption when running threaded programs.</strong> + <strong>I get unexpected results and + database corruption when running threaded + programs.</strong> </span> <p> - <span class="bold"> - <strong>I get error messages that mutex (for example, pthread_mutex_XXX or mutex_XXX) functions are undefined when linking applications with Berkeley DB.</strong> - </span> + <span class="bold"><strong>I get error messages that mutex + (for example, pthread_mutex_XXX or mutex_XXX) + functions are undefined when linking applications + with Berkeley DB.</strong></span> + </p> + <p> + On some architectures, the Berkeley DB library uses + the ISO POSIX standard pthreads and UNIX International + (UI) threads interfaces for underlying mutex support; + Solaris is an example. You can specify compilers or + compiler flags, or link with the appropriate thread + library when loading your application to resolve the + undefined references: </p> - <p>On some architectures, the Berkeley DB library uses the ISO POSIX standard pthreads and UNIX International (UI) threads interfaces for underlying mutex support; Solaris is an example. You can specify compilers or compiler flags, or link with the appropriate thread library when loading your application to resolve the undefined references:</p> <pre class="programlisting">cc ... -lpthread ... cc ... -lthread ... xlc_r ... cc ... -mt ...</pre> - <p>See the appropriate architecture-specific Reference Guide pages for more -information.</p> - <p>On systems where more than one type of mutex is available, it may be -necessary for applications to use the same threads package from which -Berkeley DB draws its mutexes. For example, if Berkeley DB was built to use the -POSIX pthreads mutex calls for mutex support, the application may need -to be written to use the POSIX pthreads interfaces for its threading -model. This is only conjecture at this time, and although we know of -no systems that actually have this requirement, it's not unlikely that -some exist.</p> - <p>In a few cases, Berkeley DB can be configured to use specific underlying mutex -interfaces. You can use the <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-posixmutexes">--enable-posixmutexes</a> and -<a class="link" href="build_unix_conf.html#build_unix_conf.--enable-uimutexes">--enable-uimutexes</a> configuration options to specify the POSIX and Unix -International (UI) threads packages. This should not, however, be -necessary in most cases.</p> - <p>In some cases, it is vitally important to make sure that you load the -correct library. For example, on Solaris systems, there are POSIX -pthread interfaces in the C library, so applications can link Berkeley DB -using only C library and not see any undefined symbols. However, the -C library POSIX pthread mutex support is insufficient for Berkeley DB, and -Berkeley DB cannot detect that fact. Similar errors can arise when -applications (for example, tclsh) use dlopen to dynamically load Berkeley DB -as a library.</p> - <p>If you are seeing problems in this area after you confirm that you're -linking with the correct libraries, there are two other things you can -try. First, if your platform supports interlibrary dependencies, we -recommend that you change the Berkeley DB Makefile to specify the appropriate -threads library when creating the Berkeley DB shared library, as an -interlibrary dependency. Second, if your application is using dlopen -to dynamically load Berkeley DB, specify the appropriate thread library on -the link line when you load the application itself.</p> + <p> + See the appropriate architecture-specific Reference + Guide pages for more information. + </p> + <p> + On systems where more than one type of mutex is + available, it may be necessary for applications to use + the same threads package from which Berkeley DB draws + its mutexes. For example, if Berkeley DB was built to + use the POSIX pthreads mutex calls for mutex support, + the application may need to be written to use the + POSIX pthreads interfaces for its threading model. + This is only conjecture at this time, and although we + know of no systems that actually have this + requirement, it's not unlikely that some exist. + </p> + <p> + In a few cases, Berkeley DB can be configured to + use specific underlying mutex interfaces. You can use + the <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-posixmutexes"> + --enable-posixmutexes</a> and <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-uimutexes">--enable-uimutexes</a> + configuration options to specify the POSIX and Unix International (UI) + threads packages. This should not, however, be + necessary in most cases. + </p> + <p> + In some cases, it is vitally important to make sure + that you load the correct library. For example, on + Solaris systems, there are POSIX pthread interfaces in + the C library, so applications can link Berkeley DB + using only C library and not see any undefined + symbols. However, the C library POSIX pthread mutex + support is insufficient for Berkeley DB, and Berkeley + DB cannot detect that fact. Similar errors can arise + when applications (for example, tclsh) use dlopen to + dynamically load Berkeley DB as a library. + </p> + <p> + If you are seeing problems in this area after you + confirm that you're linking with the correct + libraries, there are two other things you can try. + First, if your platform supports interlibrary + dependencies, we recommend that you change the + Berkeley DB Makefile to specify the appropriate + threads library when creating the Berkeley DB shared + library, as an interlibrary dependency. Second, if + your application is using dlopen to dynamically load + Berkeley DB, specify the appropriate thread library on + the link line when you load the application itself. + </p> </li> <li> <span class="bold"> - <strong>I get core dumps when running programs that fork children.</strong> + <strong>I get core dumps when running + programs that fork children.</strong> </span> - <p>Berkeley DB handles should not be shared across process forks, each forked -child should acquire its own Berkeley DB handles.</p> + <p> + Berkeley DB handles should not be shared across + process forks, each forked child should acquire its + own Berkeley DB handles. + </p> </li> <li> <span class="bold"> - <strong>I get reports of uninitialized memory reads and writes when -running software analysis tools (for example, Rational Software Corp.'s -Purify tool).</strong> + <strong>I get reports of uninitialized + memory reads and writes when running software analysis + tools (for example, Rational Software Corp.'s Purify + tool).</strong> </span> - <p>For performance reasons, Berkeley DB does not write the unused portions of -database pages or fill in unused structure fields. To turn off these -errors when running software analysis tools, build with the -<a class="link" href="build_unix_conf.html#build_unix_conf.--enable-umrw">--enable-umrw</a> -configuration option.</p> + <p> + For performance reasons, Berkeley DB does not write + the unused portions of database pages or fill in + unused structure fields. To turn off these errors when + running software analysis tools, build with the <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-umrw">--enable-umrw</a> + configuration option. + </p> </li> <li> <span class="bold"> - <strong>Berkeley DB programs or the test suite fail unexpectedly.</strong> + <strong>Berkeley DB programs or the test + suite fail unexpectedly.</strong> </span> - <p>The Berkeley DB architecture does not support placing the shared memory -regions on remote filesystems -- for example, the Network File System -(NFS) or the Andrew File System (AFS). For this reason, the shared -memory regions (normally located in the database home directory) must -reside on a local filesystem. See <a href="../programmer_reference/env_region.html" class="olink">Shared memory region</a> for more information.</p> - <p>With respect to running the test suite, always check to make sure that -TESTDIR is not on a remote mounted filesystem.</p> + <p> + The Berkeley DB architecture does not support + placing the shared memory regions on remote + filesystems -- for example, the Network File System + (NFS) or the Andrew File System (AFS). For this + reason, the shared memory regions (normally located in + the database home directory) must reside on a local + filesystem. See <a href="../programmer_reference/env_region.html" class="olink">Shared memory region</a> for more information. + </p> + <p> + With respect to running the test suite, always + check to make sure that TESTDIR is not on a remote + mounted filesystem. + </p> </li> <li> <span class="bold"> <strong>The <a href="../api_reference/C/db_dump.html" class="olink">db_dump</a> utility fails to build.</strong> </span> - <p>The <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility is the utility that supports the conversion of Berkeley DB 1.85 and earlier databases to current database formats. If the build errors look something like the following, it means the db.h include file being loaded is not a Berkeley DB 1.85 version include file:</p> + <p> + The <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility is the utility that supports the + conversion of Berkeley DB 1.85 and earlier databases + to current database formats. If the build errors look + something like the following, it means the db.h + include file being loaded is not a Berkeley DB 1.85 + version include file: + </p> <pre class="programlisting">db_dump185.c: In function `main': db_dump185.c:210: warning: assignment makes pointer from integer without a cast @@ -176,21 +254,30 @@ db_dump185.c:212: warning: assignment makes pointer from integer without a cast db_dump185.c:227: structure has no member named `seq' db_dump185.c:227: `R_NEXT' undeclared (first use in this function)</pre> - <p>If the build errors look something like the following, it means that -the Berkeley DB 1.85 code was not found in the standard libraries:</p> + <p> + If the build errors look something like the + following, it means that the Berkeley DB 1.85 code was + not found in the standard libraries: + </p> <pre class="programlisting">cc -o db_dump185 db_dump185.o ld: Unresolved: dbopen</pre> - <p>To build the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility, the Berkeley DB version 1.85 code must already -been built and available on the system. If the Berkeley DB 1.85 header file -is not found in a standard place, or if the library is not part of the -standard libraries used for loading, you will need to edit your -Makefile, and change the following lines:</p> + <p> + To build the <a href="../api_reference/C/db_dump.html" class="olink">db_dump185</a> utility, the Berkeley DB version + 1.85 code must already been built and available on the + system. If the Berkeley DB 1.85 header file is not + found in a standard place, or if the library is not + part of the standard libraries used for loading, you + will need to edit your Makefile, and change the + following lines: + </p> <pre class="programlisting">DB185INC= DB185LIB=</pre> - <p>So that the system Berkeley DB 1.85 header file and library are found; for -example:</p> + <p> + So that the system Berkeley DB 1.85 header file and + library are found; for example: + </p> <pre class="programlisting">DB185INC=/usr/local/include DB185LIB=-ldb185</pre> </li> @@ -208,7 +295,8 @@ DB185LIB=-ldb185</pre> <td width="40%" align="right"> <a accesskey="n" href="build_unix_aix.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Running the test suite under UNIX </td> + <td width="40%" align="left" valign="top">Running the test suite under + UNIX </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/build_unix_qnx.html b/docs/installation/build_unix_qnx.html index bc574798..086426cf 100644 --- a/docs/installation/build_unix_qnx.html +++ b/docs/installation/build_unix_qnx.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_macosx.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_sco.html">Next</a></td> </tr> </table> @@ -44,73 +43,111 @@ <span class="bold"> <strong>To what versions of QNX has DB been ported?</strong> </span> - <p>Berkeley DB has been ported to the QNX Neutrino technology which is commonly -referred to as QNX RTP (Real-Time Platform). Berkeley DB has not been -ported to earlier versions of QNX, such as QNX 4.25.</p> + <p> + Berkeley DB has been ported to the QNX Neutrino + technology which is commonly referred to as QNX RTP + (Real-Time Platform). Berkeley DB has not been ported + to earlier versions of QNX, such as QNX 4.25. + </p> </li> <li> <span class="bold"> - <strong>Building Berkeley DB shared libraries fails.</strong> + <strong>Building Berkeley DB shared + libraries fails.</strong> </span> - <p>The <code class="filename">/bin/sh</code> utility distributed with some QNX releases drops -core when running the GNU libtool script (which is used to build Berkeley DB -shared libraries). There are two workarounds for this problem: First, -only build static libraries. You can disable building shared libraries -by specifying the configuration flag when -configuring Berkeley DB.</p> - <p>Second, build Berkeley DB using an alternate shell. QNX distributions include -an accessories disk with additional tools. One of the included tools -is the GNU bash shell, which is able to run the libtool script. To -build Berkeley DB using an alternate shell, move <code class="filename">/bin/sh</code> aside, link -or copy the alternate shell into that location, configure, build and -install Berkeley DB, and then replace the original shell utility.</p> + <p> + The <code class="filename">/bin/sh</code> utility + distributed with some QNX releases drops core when + running the GNU libtool script (which is used to build + Berkeley DB shared libraries). There are two + workarounds for this problem: First, only build static + libraries. You can disable building shared libraries + by specifying the configuration flag when configuring + Berkeley DB. + </p> + <p> + Second, build Berkeley DB using an alternate shell. + QNX distributions include an accessories disk with + additional tools. One of the included tools is the GNU + bash shell, which is able to run the libtool script. + To build Berkeley DB using an alternate shell, move + <code class="filename">/bin/sh</code> aside, link or copy + the alternate shell into that location, configure, + build and install Berkeley DB, and then replace the + original shell utility. + </p> </li> <li> <span class="bold"> - <strong>Are there any QNX filesystem issues?</strong> + <strong>Are there any QNX filesystem + issues?</strong> </span> - <p>Berkeley DB generates temporary files for use in transactionally -protected file system operations. Due to the filename length limit of -48 characters in the QNX filesystem, applications that are using -transactions should specify a database name that is at most 43 characters.</p> + <p> + Berkeley DB generates temporary files for use in + transactionally protected file system operations. Due + to the filename length limit of 48 characters in the + QNX filesystem, applications that are using + transactions should specify a database name that is at + most 43 characters. + </p> </li> <li> <span class="bold"> - <strong>What are the implications of QNX's requirement to use -<code class="literal">shm_open</code>(2) in order to use <code class="literal">mmap</code>(2)?</strong> + <strong>What are the implications of QNX's + requirement to use <code class="literal">shm_open</code>(2) in + order to use <code class="literal">mmap</code>(2)?</strong> </span> - <p>QNX requires that files mapped with <code class="literal">mmap</code>(2) be opened using -<code class="literal">shm_open</code>(2). There are other places in addition to the -environment shared memory regions, where Berkeley DB tries to memory map files -if it can.</p> - <p>The memory pool subsystem normally attempts to use <code class="literal">mmap</code>(2) -even when using private memory, as indicated by the <a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag -to <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a>. In the case of QNX, if an application is -using private memory, Berkeley DB will not attempt to map the memory and will -instead use the local cache.</p> + <p> + QNX requires that files mapped with + <code class="literal">mmap</code>(2) be opened using + <code class="literal">shm_open</code>(2). There are other + places in addition to the environment shared memory + regions, where Berkeley DB tries to memory map files + if it can. + </p> + <p> + The memory pool subsystem normally attempts to use + <code class="literal">mmap</code>(2) even when using private + memory, as indicated by the <a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag to + <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a>. In the case of QNX, if an application is + using private memory, Berkeley DB will not attempt to + map the memory and will instead use the local cache. + </p> </li> <li> <span class="bold"> - <strong>What are the implications of QNX's mutex implementation using -microkernel resources?</strong> + <strong>What are the implications of QNX's + mutex implementation using microkernel + resources?</strong> </span> - <p>On QNX, the primitives implementing mutexes consume system resources. -Therefore, if an application unexpectedly fails, those resources could -leak. Berkeley DB solves this problem by always allocating mutexes in the -persistent shared memory regions. Then, if an application fails, -running recovery or explicitly removing the database environment by -calling the <a href="../api_reference/C/envremove.html" class="olink">DB_ENV->remove()</a> method will allow Berkeley DB to release those -previously held mutex resources. If an application specifies the -<a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag (choosing not to use persistent shared memory), -and then fails, mutexes allocated in that private memory may leak their -underlying system resources. Therefore, the <a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag -should be used with caution on QNX.</p> + <p> + On QNX, the primitives implementing mutexes consume + system resources. Therefore, if an application + unexpectedly fails, those resources could leak. + Berkeley DB solves this problem by always allocating + mutexes in the persistent shared memory regions. Then, + if an application fails, running recovery or + explicitly removing the database environment by + calling the <a href="../api_reference/C/envremove.html" class="olink">DB_ENV->remove()</a> method will allow Berkeley DB + to release those previously held mutex resources. If + an application specifies the <a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag + (choosing not to use persistent shared memory), and + then fails, mutexes allocated in that private memory + may leak their underlying system resources. Therefore, + the <a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag should be used with caution on + QNX. + </p> </li> <li> <span class="bold"> - <strong>The make clean command fails to execute when building the Berkeley DB SQL interface.</strong> + <strong>The make clean command fails to + execute when building the Berkeley DB SQL + interface.</strong> </span> - <p>Remove the build directory manually to clean up and proceed. </p> + <p> + Remove the build directory manually to clean up and + proceed. + </p> </li> </ol> </div> diff --git a/docs/installation/build_unix_sco.html b/docs/installation/build_unix_sco.html index 031d38e5..4f3497c8 100644 --- a/docs/installation/build_unix_sco.html +++ b/docs/installation/build_unix_sco.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_qnx.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_solaris.html">Next</a></td> </tr> </table> @@ -42,12 +41,15 @@ <ol type="1"> <li> <span class="bold"> - <strong>If I build with gcc, programs such as db_dump and db_stat core dump -immediately when invoked.</strong> + <strong>If I build with gcc, programs such + as db_dump and db_stat core dump immediately when + invoked.</strong> </span> - <p>We suspect gcc or the runtime loader may have a bug, but we haven't -tracked it down. If you want to use gcc, we suggest building static -libraries.</p> + <p> + We suspect gcc or the runtime loader may have a + bug, but we haven't tracked it down. If you want to + use gcc, we suggest building static libraries. + </p> </li> </ol> </div> diff --git a/docs/installation/build_unix_shlib.html b/docs/installation/build_unix_shlib.html index da9d5d92..8e3e64fb 100644 --- a/docs/installation/build_unix_shlib.html +++ b/docs/installation/build_unix_shlib.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_install.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_test.html">Next</a></td> </tr> </table> @@ -38,87 +37,125 @@ </div> </div> </div> - <p><span class="bold"><strong>Warning</strong></span>: the following information is intended to be generic and -is likely to be correct for most UNIX systems. Unfortunately, dynamic -shared libraries are not standard between UNIX systems, so there may be -information here that is not correct for your system. If you have -problems, consult your compiler and linker manual pages, or your system -administrator.</p> - <p>The Berkeley DB dynamic shared libraries are created with the name -libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so, where <span class="bold"><strong>major</strong></span> is -the major version number and <span class="bold"><strong>minor</strong></span> is the minor version number. -Other shared libraries are created if Java and Tcl support are enabled: -specifically, libdb_java-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so -and libdb_tcl-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so.</p> - <p>On most UNIX systems, when any shared library is created, the linker -stamps it with a "SONAME". In the case of Berkeley DB, the SONAME -is libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so. It is important to -realize that applications linked against a shared library remember the -SONAMEs of the libraries they use and not the underlying names in the -filesystem.</p> - <p>When the Berkeley DB shared library is installed, links are -created in the install lib directory so that -libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so, -libdb-<span class="bold"><strong>major</strong></span>.so, and libdb.so all refer to the -same library. This library will have an SONAME of -libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so.</p> - <p>Any previous versions of the Berkeley DB libraries that are -present in the install directory (such as libdb-2.7.so or -libdb-2.so) are left unchanged. (Removing or moving old shared -libraries is one drastic way to identify applications that have been -linked against those vintage releases.)</p> - <p>Once you have installed the Berkeley DB libraries, unless they are -installed in a directory where the linker normally looks for shared -libraries, you will need to specify the installation directory as part -of compiling and linking against Berkeley DB. Consult your system -manuals or system administrator for ways to specify a shared library -directory when compiling and linking applications with the -Berkeley DB libraries. Many systems support environment variables -(for example, LD_LIBRARY_PATH or LD_RUN_PATH), or system configuration -files (for example, /etc/ld.so.conf) for this purpose.</p> - <p><span class="bold"><strong>Warning</strong></span>: some UNIX installations may have an already existing -<code class="filename">/usr/lib/libdb.so</code>, and this library may be an incompatible -version of Berkeley DB.</p> - <p>We recommend that applications link against libdb.so (for example, -using -ldb). Even though the linker uses the file named -libdb.so, the executable file for the application remembers the -library's SONAME (libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so). This -has the effect of marking the applications with the versions they need -at link time. Because applications locate their needed SONAMEs when -they are executed, all previously linked applications will continue to -run using the library they were linked with, even when a new version of -Berkeley DB is installed and the file <code class="filename">libdb.so</code> -is replaced with a new version.</p> - <p>Applications that know they are using features specific to a particular -Berkeley DB release can be linked to that release. For example, an -application wanting to link to Berkeley DB major release "3" can link -using -ldb-3, and applications that know about a particular -minor release number can specify both major and minor release numbers; -for example, -ldb-3.5.</p> - <p>If you want to link with Berkeley DB before performing library -installation, the "make" command will have created a shared library -object in the <code class="filename">.libs</code> subdirectory of the build directory, such -as <code class="filename">build_unix/.libs/libdb-major.minor.so</code>. If you want -to link a file against this library, with, for example, a major number -of "3" and a minor number of "5", you should be able to do something -like the following:</p> + <p> + <span class="bold"><strong>Warning</strong></span>: the following + information is intended to be generic and is likely to be + correct for most UNIX systems. Unfortunately, dynamic shared + libraries are not standard between UNIX systems, so there may + be information here that is not correct for your system. If + you have problems, consult your compiler and linker manual + pages, or your system administrator. + </p> + <p> + The Berkeley DB dynamic shared libraries are created with + the name libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>. + so, where <span class="bold"><strong>major</strong></span> is the major version number and + <span class="bold"><strong>minor</strong></span> is the minor + version number. Other shared libraries are created if Java and + Tcl support are enabled: specifically, libdb_java-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so + and libdb_tcl-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so. + </p> + <p> + On most UNIX systems, when any shared library is created, + the linker stamps it with a "SONAME". In the case of Berkeley + DB, the SONAME is libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so. + It is important to realize that applications linked against a shared + library remember the SONAMEs of the libraries they use and not the + underlying names in the filesystem. + </p> + <p> + When the Berkeley DB shared library is installed, links are + created in the install lib directory so that libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so, + libdb-<span class="bold"><strong>major</strong></span>.so, and libdb.so all refer to the same + library. This library will have an SONAME of libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so. + </p> + <p> + Any previous versions of the Berkeley DB libraries that are + present in the install directory (such as libdb-2.7.so or + libdb-2.so) are left unchanged. (Removing or moving old shared + libraries is one drastic way to identify applications that + have been linked against those vintage releases.) + </p> + <p> + Once you have installed the Berkeley DB libraries, unless + they are installed in a directory where the linker normally + looks for shared libraries, you will need to specify the + installation directory as part of compiling and linking + against Berkeley DB. Consult your system manuals or system + administrator for ways to specify a shared library directory + when compiling and linking applications with the Berkeley DB + libraries. Many systems support environment variables (for + example, LD_LIBRARY_PATH or LD_RUN_PATH), or system + configuration files (for example, /etc/ld.so.conf) for this + purpose. + </p> + <p> + <span class="bold"><strong>Warning</strong></span>: some UNIX + installations may have an already existing + <code class="filename">/usr/lib/libdb.so</code>, and this library + may be an incompatible version of Berkeley DB. + </p> + <p> + We recommend that applications link against libdb.so (for + example, using -ldb). Even though the linker uses the file + named libdb.so, the executable file for the application + remembers the library's SONAME + (libdb-<span class="bold"><strong>major</strong></span>.<span class="bold"><strong>minor</strong></span>.so). + This has the effect of marking the applications with the versions they + need at link time. Because applications locate their needed SONAMEs when they are + executed, all previously linked applications will continue to + run using the library they were linked with, even when a new + version of Berkeley DB is installed and the file + <code class="filename">libdb.so</code> is replaced with a new + version. + </p> + <p> + Applications that know they are using features specific to + a particular Berkeley DB release can be linked to that + release. For example, an application wanting to link to + Berkeley DB major release "3" can link using -ldb-3, and + applications that know about a particular minor release number + can specify both major and minor release numbers; for example, + -ldb-3.5. + </p> + <p> + If you want to link with Berkeley DB before performing + library installation, the "make" command will have created a + shared library object in the <code class="filename">.libs</code> + subdirectory of the build directory, such as + <code class="filename">build_unix/.libs/libdb-major.minor.so</code>. + If you want to link a file against this library, with, for + example, a major number of "3" and a minor number of "5", you + should be able to do something like the following: + </p> <pre class="programlisting">cc -L BUILD_DIRECTORY/.libs -o testprog testprog.o -ldb-3.5 env LD_LIBRARY_PATH="BUILD_DIRECTORY/.libs:$LD_LIBRARY_PATH" ./testprog</pre> - <p>where <span class="bold"><strong>BUILD_DIRECTORY</strong></span> is the full directory path to the directory -where you built Berkeley DB.</p> - <p>The libtool program (which is configured in the build directory) can be -used to set the shared library path and run a program. For example, -the following runs the gdb debugger on the db_dump utility after setting -the appropriate paths:</p> + <p> + where <span class="bold"><strong>BUILD_DIRECTORY</strong></span> is + the full directory path to the directory where you built + Berkeley DB. + </p> + <p> + The libtool program (which is configured in the build + directory) can be used to set the shared library path and run + a program. For example, the following runs the gdb debugger on + the db_dump utility after setting the appropriate paths: + </p> <pre class="programlisting">libtool gdb db_dump</pre> - <p>Libtool may not know what to do with arbitrary commands (it is hardwired -to recognize "gdb" and some other commands). If it complains the mode -argument will usually resolve the problem:</p> + <p> + Libtool may not know what to do with arbitrary commands (it + is hardwired to recognize "gdb" and some other commands). If + it complains the mode argument will usually resolve the + problem: + </p> <pre class="programlisting">libtool --mode=execute my_debugger db_dump</pre> - <p>On most systems, using libtool in this way is exactly equivalent to -setting the LD_LIBRARY_PATH environment variable and then executing the -program. On other systems, using libtool has the virtue of knowing about -any other details on systems that don't behave in this typical way.</p> + <p> + On most systems, using libtool in this way is exactly + equivalent to setting the LD_LIBRARY_PATH environment variable + and then executing the program. On other systems, using + libtool has the virtue of knowing about any other details on + systems that don't behave in this typical way. + </p> </div> <div class="navfooter"> <hr /> @@ -131,11 +168,13 @@ any other details on systems that don't behave in this typical way.</p> <td width="40%" align="right"> <a accesskey="n" href="build_unix_test.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Installing Berkeley DB </td> + <td width="40%" align="left" valign="top">Installing Berkeley + DB </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Running the test suite under UNIX</td> + <td width="40%" align="right" valign="top"> Running the test suite under + UNIX</td> </tr> </table> </div> diff --git a/docs/installation/build_unix_small.html b/docs/installation/build_unix_small.html index 7ea6a451..32c30f0c 100644 --- a/docs/installation/build_unix_small.html +++ b/docs/installation/build_unix_small.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_sql.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_flags.html">Next</a></td> </tr> </table> @@ -39,106 +38,110 @@ </div> </div> <p> - There are a set of configuration options to assist you in building - a small memory footprint library. These configuration options turn - off specific functionality in the Berkeley DB library, reducing the - code size. These configuration options include: + There are a set of configuration options to assist you in + building a small memory footprint library. These configuration + options turn off specific functionality in the Berkeley DB + library, reducing the code size. These configuration options + include: </p> <div class="variablelist"> <dl> <dt> <span class="term"> - <code class="literal">--enable-smallbuild</code> + <code class="literal">--enable-smallbuild</code> </span> </dt> <dd> <p> - Equivalent to individually specifying all of the following - configuration options. In addition, when compiling - building with the GNU gcc compiler, this option uses the - <code class="literal">-Os</code> compiler build flag instead of the - default <code class="literal">-O3</code>. + Equivalent to individually specifying all of + the following configuration options. In addition, + when compiling building with the GNU gcc compiler, + this option uses the <code class="literal">-Os</code> + compiler build flag instead of the default + <code class="literal">-O3</code>. </p> <div class="variablelist"> <dl> <dt> <span class="term"> - <code class="literal">--with-cryptography=no</code> - </span> + <code class="literal">--with-cryptography=no</code> + </span> </dt> <dd> - Builds Berkeley DB without support for cryptography. + Builds Berkeley DB without support + for cryptography. </dd> <dt> <span class="term"> - <code class="literal">--disable-hash</code> - </span> + <code class="literal">--disable-hash</code> + </span> </dt> - <dd> - Builds Berkeley DB without support for the Hash access - method. + <dd> + Builds Berkeley DB without support + for the Hash access method. </dd> <dt> <span class="term"> - <code class="literal">--disable-heap</code> - </span> + <code class="literal">--disable-heap</code> + </span> </dt> - <dd> - Builds Berkeley DB without support for the - Heap access method. + <dd> + Builds Berkeley DB without support + for the Heap access method. </dd> <dt> <span class="term"> - <code class="literal">--disable-queue</code> - </span> + <code class="literal">--disable-queue</code> + </span> </dt> - <dd> - Builds Berkeley DB without support for the Queue access - method. + <dd> + Builds Berkeley DB without support + for the Queue access method. </dd> <dt> <span class="term"> - <code class="literal">--disable-replication</code> - </span> + <code class="literal">--disable-replication</code> + </span> </dt> - <dd> - Builds Berkeley DB without support for the database - environment replication. + <dd> + Builds Berkeley DB without support + for the database environment replication. </dd> <dt> <span class="term"> - <code class="literal">--disable-statistics</code> - </span> + <code class="literal">--disable-statistics</code> + </span> </dt> <dd> - Builds Berkeley DB without support for the statistics - interfaces. + Builds Berkeley DB without support + for the statistics interfaces. </dd> <dt> <span class="term"> - <code class="literal">--disable-verify</code> - </span> + <code class="literal">--disable-verify</code> + </span> </dt> - <dd> - Builds Berkeley DB without support for database - verification. + <dd> + Builds Berkeley DB without support + for database verification. </dd> <dt> <span class="term"> - <code class="literal">--enable-stripped_messages</code> - </span> + <code class="literal">--enable-stripped_messages</code> + </span> </dt> <dd> - <p> - Strips message text from the error messages issued by - Berkeley DB. This can reduce the size of the library by + <p> + Strips message text from the error + messages issued by Berkeley DB. This + can reduce the size of the library by roughly another 22KB. </p> - <p> - If your library has stripped messages, you can get an idea of - what text should be issued for a given error message by using - the <a href="../articles/mssgtxt/index.html" class="olink">Message - Reference for Stripped Libraries</a> guide. + <p> + If your library has stripped + messages, you can get an idea of what + text should be issued for a given + error message by using the <a href="../articles/mssgtxt/index.html" class="olink">Berkeley DB Message Reference Guide</a>. </p> </dd> </dl> @@ -149,18 +152,17 @@ <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p> - <code class="literal">--disable-cryptography</code> and + <code class="literal">--disable-cryptography</code> and <code class="literal">--enable-cryptography</code> are - deprecated in the Berkeley DB 11gR2 release. - Use <code class="literal">--with-cryptography=no</code> - and <code class="literal">--with-cryptography=yes</code> - instead. + deprecated in the Berkeley DB 11gR2 release. Use + <code class="literal">--with-cryptography=no</code> and + <code class="literal">--with-cryptography=yes</code> instead. </p> </div> - <p> - The following configuration options will increase the size of the - Berkeley DB library dramatically and are only useful when debugging - applications: + <p> + The following configuration options will increase the size + of the Berkeley DB library dramatically and are only useful + when debugging applications: </p> <div class="variablelist"> <dl> @@ -169,47 +171,57 @@ <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-debug">--enable-debug</a> </span> </dt> - <dd>Build Berkeley DB with symbols for debugging.</dd> + <dd> + Build Berkeley DB with symbols for + debugging. + </dd> <dt> <span class="term"> <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-debug_rop">--enable-debug_rop</a> </span> </dt> - <dd>Build Berkeley DB with read-operation logging.</dd> + <dd> + Build Berkeley DB with read-operation + logging. + </dd> <dt> <span class="term"> <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-debug_wop">--enable-debug_wop</a> </span> </dt> - <dd>Build Berkeley DB with write-operation logging.</dd> + <dd> + Build Berkeley DB with write-operation + logging. + </dd> <dt> <span class="term"> <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-diagnostic">--enable-diagnostic</a> </span> </dt> - <dd>Build Berkeley DB with run-time debugging checks.</dd> + <dd> + Build Berkeley DB with run-time debugging + checks. + </dd> </dl> </div> <p> - In addition, static libraries are usually smaller than shared - libraries. By default Berkeley DB will build both shared and - static libraries. To build only a static library, configure - Berkeley DB with the - <a class="xref" href="build_unix_conf.html" title="Configuring Berkeley DB">Configuring Berkeley DB</a> - option. + In addition, static libraries are usually smaller than + shared libraries. By default Berkeley DB will build both + shared and static libraries. To build only a static library, + configure Berkeley DB with the <a class="xref" href="build_unix_conf.html" title="Configuring Berkeley DB">Configuring Berkeley DB</a> option. </p> <p> The size of the Berkeley DB library varies depending on the - compiler, machine architecture, and configuration options. As an - estimate, production Berkeley DB libraries built with GNU gcc - version 4.X compilers have footprints in the range of 600KB to - 1.4MB on 32-bit x86 architectures, and in the range of 700KB to - 1.6MB on 64-bit x86 architectures. + compiler, machine architecture, and configuration options. As + an estimate, production Berkeley DB libraries built with GNU + gcc version 4.X compilers have footprints in the range of + 600KB to 1.4MB on 32-bit x86 architectures, and in the range + of 700KB to 1.6MB on 64-bit x86 architectures. </p> - <p> - For assistance in further reducing the size of the Berkeley DB - library, or in building small memory footprint libraries on other - systems, please contact Berkeley DB support. + <p> + For assistance in further reducing the size of the Berkeley + DB library, or in building small memory footprint libraries on + other systems, please contact Berkeley DB support. </p> </div> <div class="navfooter"> @@ -223,11 +235,13 @@ <td width="40%" align="right"> <a accesskey="n" href="build_unix_flags.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Configuring the SQL Interface </td> + <td width="40%" align="left" valign="top">Configuring the SQL + Interface </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Changing compile or load options</td> + <td width="40%" align="right" valign="top"> Changing compile or load + options</td> </tr> </table> </div> diff --git a/docs/installation/build_unix_solaris.html b/docs/installation/build_unix_solaris.html index 2ef6a973..2fdc2eab 100644 --- a/docs/installation/build_unix_solaris.html +++ b/docs/installation/build_unix_solaris.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_sco.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_sunos.html">Next</a></td> </tr> </table> @@ -42,62 +41,94 @@ <ol type="1"> <li> <span class="bold"> - <strong>I can't compile and run multithreaded applications.</strong> + <strong>I can't compile and run + multithreaded applications.</strong> </span> - <p>Special compile-time flags and additional libraries are required when -compiling threaded applications on Solaris. If you are compiling a -threaded application, you must compile with the D_REENTRANT flag and link -with the libpthread.a or libthread.a libraries:</p> + <p> + Special compile-time flags and additional libraries + are required when compiling threaded applications on + Solaris. If you are compiling a threaded application, + you must compile with the D_REENTRANT flag and link + with the libpthread.a or libthread.a libraries: + </p> <pre class="programlisting">cc -mt ... cc -D_REENTRANT ... -lthread cc -D_REENTRANT ... -lpthread</pre> - <p>The Berkeley DB library will automatically build with the correct options.</p> + <p> + The Berkeley DB library will automatically build + with the correct options. + </p> </li> <li> <span class="bold"> - <strong>I've installed gcc on my Solaris system, but configuration -fails because the compiler doesn't work.</strong> + <strong>I've installed gcc on my Solaris + system, but configuration fails because the compiler + doesn't work.</strong> </span> - <p>On some versions of Solaris, there is a cc executable in the user's path, -but all it does is display an error message and fail:</p> + <p> + On some versions of Solaris, there is a cc + executable in the user's path, but all it does is + display an error message and fail: + </p> <pre class="programlisting">% which cc /usr/ucb/cc % cc /usr/ucb/cc: language optional software package not installed</pre> - <p>Because Berkeley DB always uses the native compiler in preference to gcc, this -is a fatal error. If the error message you are seeing is the following, -then this may be the problem:</p> + <p> + Because Berkeley DB always uses the native compiler + in preference to gcc, this is a fatal error. If the + error message you are seeing is the following, then + this may be the problem: + </p> <pre class="programlisting">checking whether the C compiler (cc -O) works... no configure: error: installation or configuration problem: C compiler cannot create executables.</pre> - <p>The simplest workaround is to set your CC environment variable to the -system compiler and reconfigure; for example:</p> + <p> + The simplest workaround is to set your CC + environment variable to the system compiler and + reconfigure; for example: + </p> <pre class="programlisting">env CC=gcc ../dist/configure</pre> - <p>If you are using the --configure-cxx option, you may also want to specify -a C++ compiler, for example the following:</p> + <p> + If you are using the --configure-cxx option, you + may also want to specify a C++ compiler, for example + the following: + </p> <pre class="programlisting">env CC=gcc CCC=g++ ../dist/configure</pre> </li> <li> <span class="bold"> - <strong>I see the error -"libc internal error: _rmutex_unlock: rmutex not held", followed by a core -dump when running threaded or JAVA programs.</strong> + <strong>I see the error "libc internal + error: _rmutex_unlock: rmutex not held", followed by a + core dump when running threaded or JAVA + programs.</strong> </span> - <p>This is a known bug in Solaris 2.5 and it is fixed by Sun patch 103187-25.</p> + <p> + This is a known bug in Solaris 2.5 and it is fixed + by Sun patch 103187-25. + </p> </li> <li> <span class="bold"> - <strong>I see error reports of nonexistent files, corrupted metadata -pages and core dumps.</strong> + <strong>I see error reports of nonexistent + files, corrupted metadata pages and core + dumps.</strong> </span> - <p>Solaris 7 contains a bug in the threading libraries (-lpthread, --lthread), which causes the wrong version of the pwrite routine to be -linked into the application if the thread library is linked in after -the C library. The result will be that the pwrite function is called -rather than the pwrite64. To work around the problem, use an explicit -link order when creating your application.</p> - <p>Sun Microsystems is tracking this problem with Bug Id's 4291109 and 4267207, -and patch 106980-09 to Solaris 7 fixes the problem:</p> + <p> + Solaris 7 contains a bug in the threading libraries + (-lpthread, -lthread), which causes the wrong version + of the pwrite routine to be linked into the + application if the thread library is linked in after + the C library. The result will be that the pwrite + function is called rather than the pwrite64. To work + around the problem, use an explicit link order when + creating your application. + </p> + <p> + Sun Microsystems is tracking this problem with Bug + Id's 4291109 and 4267207, and patch 106980-09 to + Solaris 7 fixes the problem: + </p> <pre class="programlisting">Bug Id: 4291109 Duplicate of: 4267207 Category: library @@ -112,49 +143,87 @@ TI_PWRITE64 row (see near the end).</pre> </li> <li> <span class="bold"> - <strong>I see corrupted databases when doing hot backups or creating -a hot failover archive.</strong> + <strong>I see corrupted databases when doing + hot backups or creating a hot failover + archive.</strong> </span> - <p>The Solaris cp utility is implemented using the mmap system call, and -so writes are not blocked when it reads database pages. See -<a href="../programmer_reference/transapp_reclimit.html" class="olink">Berkeley DB recoverability</a> -for more information.</p> + <p> + The Solaris cp utility is implemented using the + mmap system call, and so writes are not blocked when + it reads database pages. See <a href="../programmer_reference/transapp_reclimit.html" class="olink">Berkeley DB recoverability</a> for + more information. + </p> </li> <li> <span class="bold"> - <strong>Performance is slow and the application is doing a lot of I/O -to the disk on which the database environment's files are stored.</strong> + <strong>Performance is slow and the + application is doing a lot of I/O to the disk on which + the database environment's files are + stored.</strong> </span> - <p>By default, Solaris periodically flushes dirty blocks from memory-mapped -files to the backing filesystem. This includes the Berkeley DB database -environment's shared memory regions and can affect Berkeley DB performance. -Workarounds include creating the shared regions in system shared memory -(<a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a>) or application private memory -(<a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a>), or configuring Solaris to not flush memory-mapped -pages. For more information, see the "Solaris Tunable Parameters -Reference Manual: fsflush and Related Tunables".</p> + <p> + By default, Solaris periodically flushes dirty + blocks from memory-mapped files to the backing + filesystem. This includes the Berkeley DB database + environment's shared memory regions and can affect + Berkeley DB performance. Workarounds include creating + the shared regions in system shared memory + (<a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a>) or application private memory + (<a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a>), or configuring Solaris to not flush + memory-mapped pages. For more information, see the + "Solaris Tunable Parameters Reference Manual: fsflush + and Related Tunables". + </p> </li> <li> <span class="bold"> - <strong>I see errors about "open64" when building Berkeley DB applications.</strong> + <strong>I see errors about "open64" when + building Berkeley DB applications.</strong> </span> - <p>System include files (most commonly fcntl.h) in some releases of AIX -and Solaris redefine "open" when large-file support is enabled -for applications. This causes problems when compiling applications -because "open" is a method in the Berkeley DB APIs. To work around this -problem: -</p> + <p> + System include files (most commonly fcntl.h) in + some releases of AIX and Solaris redefine "open" when + large-file support is enabled for applications. This + causes problems when compiling applications because + "open" is a method in the Berkeley DB APIs. To work + around this problem: </p> <div class="orderedlist"> <ol type="a"> - <li>Avoid including the problematical system include files in source code -files which also include Berkeley DB include files and call into the Berkeley DB -API.</li> - <li>Before building Berkeley DB, modify the generated include file db.h to itself -include the problematical system include files.</li> - <li>Turn off Berkeley DB large-file support by specifying the -<a class="link" href="build_unix_conf.html#build_unix_conf.--disable-largefile">--disable-largefile</a> configuration option and rebuilding.</li> + <li> + Avoid including the problematical + system include files in source code files + which also include Berkeley DB include files + and call into the Berkeley DB API. + </li> + <li> + Before building Berkeley DB, modify the + generated include file db.h to itself include + the problematical system include files. + </li> + <li> + Turn off Berkeley DB large-file support + by specifying the <a class="link" href="build_unix_conf.html#build_unix_conf.--disable-largefile"> + --disable-largefile</a> configuration + option and rebuilding. + </li> </ol> </div> + <p> + </p> + </li> + <li> + <span class="bold"> + <strong> I see that Berkeley DB + automatically uses optimization level '-xO2' for the + Sun Workshop compiler. Can I change this to a higher + level? </strong> + </span> + <p> + We have noticed some test failures when compiling + with level '-xO3' and higher due to overaggressive + compiler optimizations. We do not recommend changing + this setting. + </p> </li> </ol> </div> diff --git a/docs/installation/build_unix_sql.html b/docs/installation/build_unix_sql.html index e48f966f..f0dae3bd 100644 --- a/docs/installation/build_unix_sql.html +++ b/docs/installation/build_unix_sql.html @@ -14,17 +14,17 @@ <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">Configuring the SQL Interface</th> + <th colspan="3" align="center">Configuring the SQL + Interface</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_conf.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_small.html">Next</a></td> </tr> </table> @@ -34,7 +34,8 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_unix_sql"></a>Configuring the SQL Interface</h2> + <h2 class="title" style="clear: both"><a id="build_unix_sql"></a>Configuring the SQL + Interface</h2> </div> </div> </div> @@ -47,7 +48,7 @@ </dt> <dt> <span class="sect2"> - <a href="build_unix_sql.html#idp249752">Enabling Extensions</a> + <a href="build_unix_sql.html#idp698856">Enabling Extensions</a> </span> </dt> <dt> @@ -57,12 +58,12 @@ </dt> <dt> <span class="sect2"> - <a href="build_unix_sql.html#idp327120">Using the JDBC Driver</a> + <a href="build_unix_sql.html#idp704816">Using the JDBC Driver</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_unix_sql.html#idp349152">Building the ODBC Driver</a> + <a href="build_unix_sql.html#idp736952">Building the ODBC Driver</a> </span> </dt> <dt> @@ -72,142 +73,171 @@ </dt> </dl> </div> - <p> - There are a set of options you can provide to - <span class="command"><strong>configure</strong></span> in order to control how the Berkeley DB - SQL interface is built. These configuration options include: -</p> + <p> + There are a set of options you can provide to + <span class="command"><strong>configure</strong></span> in order to control how the + Berkeley DB SQL interface is built. These configuration + options include: + </p> <div class="variablelist"> <dl> <dt> <span class="term">--disable-log-checksum</span> </dt> - <dd> - Disables checksums in log records. This provides a boost to - performance at the risk of log files having undetectable - corruption that could prevent proper data recovery in case of - database corruption. - <p> - Note that while this option is meant for use with the SQL - interface, it will also disable checksum for the non-SQL - interfaces. - </p></dd> + <dd> Disables checksums in log records. This + provides a boost to performance at the risk of log + files having undetectable corruption that could + prevent proper data recovery in case of database + corruption. + <p> + Note that while this option is meant for use + with the SQL interface, it will also disable + checksum for the non-SQL interfaces. + </p></dd> <dt> <span class="term">--enable-sql</span> </dt> <dd> - Causes the <span class="command"><strong>dbsql</strong></span> command line interpreter to - be built. Along with <span class="command"><strong>dbsql</strong></span>, this argument - also builds the libdb_sqlXX.{so|la} library, a C API library - that mirrors the SQLite C API. - </dd> + Causes the <span class="command"><strong>dbsql</strong></span> command + line interpreter to be built. Along with + <span class="command"><strong>dbsql</strong></span>, this argument also + builds the libdb_sqlXX.{so|la} library, a C API + library that mirrors the SQLite C API. + </dd> <dt> <span class="term">--enable-sql_compat</span> </dt> <dd> - <p> - Causes the <span class="command"><strong>sqlite3</strong></span> command line tool to - be built. This tool is identical to the - <span class="command"><strong>dbsql</strong></span> command line tool, except that it - has the same name as the command line tool that comes with - standard SQLite. - </p> - <p> - In addition, the libsqlite3.{so|la} C API library is built - if this option is specified. This library is identical to - the libdb_sqlXX.{so|la} library that is normally built for Berkeley - DB's sql interface, except that it has the same name as the - library which is built for standard SQLite. - </p> - <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"> - <h3 class="title">Warning</h3> - <p> - Use this compatibility option with - <span class="emphasis"><em>extreme</em></span> care. Standard SQLite is - used by many programs and utilities on many different - platforms. Some platforms, such as Mac OS X, come with - standard SQLite built in because default applications for the - platform use that library. + <p> + Causes the <span class="command"><strong>sqlite3</strong></span> command + line tool to be built. This tool is identical to + the <span class="command"><strong>dbsql</strong></span> command line tool, + except that it has the same name as the command + line tool that comes with standard SQLite. </p> - <p> - <span class="bold"><strong>Use of this option on platforms where standard SQLite - is in production use can cause unexpected runtime - errors either for your own application, or for - applications and utilities commonly found on the - platform, depending on which library is found first - in the platform's library search path.</strong></span> + <p> + In addition, the libsqlite3.{so|la} C API + library is built if this option is specified. This + library is identical to the libdb_sqlXX.{so|la} + library that is normally built for Berkeley DB's + sql interface, except that it has the same name as + the library which is built for standard SQLite. </p> + <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"> + <h3 class="title">Warning</h3> + <p> + Use this compatibility option with + <span class="emphasis"><em>extreme</em></span> care. + Standard SQLite is used by many programs and + utilities on many different platforms. Some + platforms, such as Mac OS X, come with + standard SQLite built in because default + applications for the platform use that + library. + </p> <p> - Use this option <span class="emphasis"><em>only</em></span> if you know - exactly what you are doing. - </p> + <span class="bold"><strong>Use of this option on + platforms where standard SQLite is in + production use can cause unexpected + runtime errors either for your own + application, or for applications and + utilities commonly found on the platform, + depending on which library is found first + in the platform's library search + path.</strong></span> + </p> + <p> + Use this option <span class="emphasis"><em>only</em></span> + if you know exactly what you are doing. + </p> </div> <p> - This option is provided so that there is an easy upgrade - path for legacy SQLite tools and scripts that want to use - BDB SQL without rewriting the tool or script. However, - data contained in standard SQLite databases must be - manually migrated from the old database to your BDB SQL - database even if you use this option. See the - <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide for information on - migrating data from standard SQLite to BDB SQL databases. - </p> - <p> - Note that in addition to the renamed command line tool and - library, this option also causes versions of the command - line tool and library to be built that use the normal BDB - SQLite names (<span class="command"><strong>dbsql</strong></span> and libdb_sqlXX.{so|la}). - </p> + This option is provided so that there is an + easy upgrade path for legacy SQLite tools and + scripts that want to use BDB SQL without rewriting + the tool or script. However, data contained in + standard SQLite databases must be manually + migrated from the old database to your BDB SQL + database even if you use this option. See the + <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide for + information on migrating data from standard SQLite + to BDB SQL databases. + </p> + <p> + Note that in addition to the renamed command + line tool and library, this option also causes + versions of the command line tool and library to + be built that use the normal BDB SQLite names + (<span class="command"><strong>dbsql</strong></span> and + libdb_sqlXX.{so|la}). + </p> </dd> <dt> <span class="term">--enable-test</span> </dt> <dd> - Cause the Berkeley DB SQL interface test suite to be built. - This argument can also be used with either - <code class="literal">--enable-sql</code> or - <code class="literal">--enable-sql_compat</code> to build the SQLite Tcl - test runner. - </dd> + Cause the Berkeley DB SQL interface test suite + to be built. This argument can also be used with + either <code class="literal">--enable-sql</code> or + <code class="literal">--enable-sql_compat</code> to build + the SQLite Tcl test runner. + </dd> <dt> <span class="term">--enable-jdbc</span> </dt> <dd> + <p> + Causes the JDBC driver to be built. Setting + this option implies that + <code class="literal">--enable-sql</code> is set, which + means that the Berkeley DB SQL API will be built + too. + </p> + </dd> + <dt> + <span class="term">--with-cryptography</span> + </dt> + <dd> <p> - Causes the JDBC driver to be built. Setting this option - implies that <code class="literal">--enable-sql</code> is set, which - means that the Berkeley DB SQL API will be built too. - </p> + Enables encryption support for the Berkeley DB + SQL interface. See <a href="../bdb-sql/sql_encryption.html" class="olink">SQL Encryption</a> in the + <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide for + usage details. + </p> </dd> </dl> </div> - <p> - The following configuration options are useful when debugging applications: -</p> + <p> + The following configuration options are useful when + debugging applications: + </p> <div class="variablelist"> <dl> <dt> <span class="term"> - <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-debug">--enable-debug</a> - </span> + <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-debug">--enable-debug</a> + </span> </dt> <dd> - Builds the Berkeley DB SQL interface with debug symbols. - </dd> + Builds the Berkeley DB SQL interface with debug + symbols. + </dd> <dt> <span class="term"> - <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-diagnostic">--enable-diagnostic</a> - </span> + <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-diagnostic">--enable-diagnostic</a> + </span> </dt> <dd> - Builds the Berkeley DB SQL interface with run-time debugging checks. - </dd> + Builds the Berkeley DB SQL interface with + run-time debugging checks. + </dd> </dl> </div> - <p> - Any arguments that you can provide to the standard SQLite configure - script can also be supplied when configuring Berkeley DB SQL interface. -</p> + <p> + Any arguments that you can provide to the standard SQLite + configure script can also be supplied when configuring + Berkeley DB SQL interface. + </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> @@ -216,81 +246,133 @@ </div> </div> </div> - <p>There are several configuration options you can specify as an argument to the configure script using the standard environment variable, CFLAGS.</p> + <p> + There are several configuration options you can specify + as an argument to the configure script using the standard + environment variable, CFLAGS. For example, to configure + with the option BDBSQL_FILE_PER_TABLE, do the + following: + </p> + <pre class="programlisting">$ ../dist/configure --enable-sql CFLAGS="-DBDBSQL_FILE_PER_TABLE=1"</pre> <div class="variablelist"> <dl> <dt> <span class="term">BDBSQL_DEFAULT_PAGE_SIZE</span> </dt> - <dd> -To set the default page size when you create a database, specify the BDBSQL_DEFAULT_PAGE_SIZE flag. -The value assigned must be a 0, 512, 1024, 2048, 4096, 8192 16384, 32768, or 65536. The default value is 4096. -If the value is set to zero, Berkeley DB queries the file system to determine the best page size, -and the value of SQLITE_DEFAULT_PAGE_SIZE is used to calculate the cache size, as the cache size is specified as a number of pages. -</dd> + <dd> + To set the default page size when you + create a database, specify the + BDBSQL_DEFAULT_PAGE_SIZE flag. The value assigned + must be a 0, 512, 1024, 2048, 4096, 8192 16384, + 32768, or 65536. The default value is 4096. If the + value is set to zero, Berkeley DB queries the file + system to determine the best page size, and the + value of SQLITE_DEFAULT_PAGE_SIZE is used to + calculate the cache size, as the cache size is + specified as a number of pages. + </dd> <dt> <span class="term">BDBSQL_FILE_PER_TABLE</span> </dt> <dd> -To generate each table in a separate file, rather than as subdatabases in a single file, specify the BDBSQL_FILE_PER_TABLE flag. -When this option is enabled, the SQL database name is used as a directory name. This directory contains one file for the metadata and one file each for every table created by the SQL API. -Note that adding or deleting files from the database directory may corrupt your database. -To backup the metadata (schema), make a copy of the <code class="literal">metadata</code> and <code class="literal">table00001</code> files from the database directory. -Make a new copy whenever the schema is changed. -</dd> + To generate each table in a separate file, + rather than as subdatabases in a single file, + specify the BDBSQL_FILE_PER_TABLE flag. When this + option is enabled, the SQL database name is used + as a directory name. This directory contains one + file for the metadata and one file each for every + table created by the SQL API. Note that adding or + deleting files from the database directory may + corrupt your database. To backup the metadata + (schema), make a copy of the + <code class="literal">metadata</code> and + <code class="literal">table00001</code> files from the + database directory. Make a new copy whenever the + schema is changed. + </dd> <dt> <span class="term">BDBSQL_LOG_REGIONMAX</span> </dt> <dd> -To configure the log region size for the underlying storage engine, specify the BDBSQL_LOG_REGIONMAX flag. For more information, see -<a href="../api_reference/C/envget_lg_regionmax.html" class="olink">DB_ENV->get_lg_regionmax()</a>. - -</dd> + To configure the log region size for the + underlying storage engine, specify the + BDBSQL_LOG_REGIONMAX flag. For more information, + see <a href="../api_reference/C/envget_lg_regionmax.html" class="olink">DB_ENV->get_lg_regionmax()</a>. + </dd> <dt> - <span class="term">BDBSQL_OMIT_LEAKCHECK -</span> + <span class="term">BDBSQL_OMIT_LEAKCHECK </span> </dt> - <dd>For Berkeley DB to use the default system allocation routines rather than the SQLite allocation routines, specify the BDBSQL_OMIT_LEAKCHECK flag. -</dd> + <dd> + For Berkeley DB to use the default system + allocation routines rather than the SQLite + allocation routines, specify the + BDBSQL_OMIT_LEAKCHECK flag. + </dd> <dt> - <span class="term">BDBSQL_OMIT_LOG_REMOVE -</span> + <span class="term">BDBSQL_OMIT_LOG_REMOVE </span> </dt> - <dd>Berkeley DB automatically removes log files that are not required any more, that is, files that are older than the most recent checkpoint. To disable this functionality, specify the BDBSQL_OMIT_LOG_REMOVE flag. It is necessary to provide this flag if you are using replication with Berkeley DB SQL. -</dd> + <dd> + Berkeley DB automatically removes log files + that are not required any more, that is, files + that are older than the most recent checkpoint. To + disable this functionality, specify the + BDBSQL_OMIT_LOG_REMOVE flag. It is necessary to + provide this flag if you are using replication + with Berkeley DB SQL. + </dd> <dt> - <span class="term">BDBSQL_OMIT_SHARING -</span> + <span class="term">BDBSQL_OMIT_SHARING </span> </dt> - <dd>To create a private environment rather than a shared environment, specify the BDBSQL_OMIT_SHARING flag. That is, the cache and other region files will be created in memory rather than using file backed shared memory. For more information, see the DB_PRIVATE flag of <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a>. -</dd> + <dd> + To create a private environment rather than + a shared environment, specify the + BDBSQL_OMIT_SHARING flag. That is, the cache and + other region files will be created in memory + rather than using file backed shared memory. For + more information, see the DB_PRIVATE flag of + <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a>. + </dd> <dt> - <span class="term">BDBSQL_SINGLE_THREAD -</span> + <span class="term">BDBSQL_SINGLE_THREAD </span> </dt> - <dd>To disable locking and thread safe connections, specify the BDBSQL_SINGLE_THREAD flag. If an application is going to use Berkeley DB from a single thread and a single process, enabling this flag can deliver significant performance advantages. -</dd> + <dd> + To disable locking and thread safe + connections, specify the BDBSQL_SINGLE_THREAD + flag. If an application is going to use Berkeley + DB from a single thread and a single process, + enabling this flag can deliver significant + performance advantages. + </dd> <dt> - <span class="term">SQLITE_DEFAULT_CACHE_SIZE -</span> + <span class="term">SQLITE_DEFAULT_CACHE_SIZE </span> </dt> - <dd>SQLite provides an in-memory cache which you size according to the maximum number of - database pages that you want to hold in memory at any given time. - Berkeley DB's in-memory cache feature performs the same function as SQLite. - To specify the suggested maximum number of pages of disk cache that will be allocated per open database file specify the SQLITE_DEFAULT_CACHE_SIZE flag. Default value is 2000 pages. - For more information, see the SQLite documentation on <a class="ulink" href="http://www.sqlite.org/pragma.html#pragma_default_cache_size" target="_top">PRAGMA default_cache_size</a>. -</dd> + <dd> + SQLite provides an in-memory cache which you + size according to the maximum number of database + pages that you want to hold in memory at any given + time. Berkeley DB's in-memory cache feature + performs the same function as SQLite. To specify + the suggested maximum number of pages of disk + cache that will be allocated per open database + file specify the SQLITE_DEFAULT_CACHE_SIZE flag. + Default value is 2000 pages. For more information, + see the SQLite documentation on <a class="ulink" href="http://www.sqlite.org/pragma.html#pragma_default_cache_size" target="_top"> + PRAGMA default_cache_size</a>. + </dd> <dt> - <span class="term">SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT -</span> + <span class="term">SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT </span> </dt> <dd> -For SQLite, this pragma identifies the maximum size that the journal file is allowed -to be. Berkeley DB does not have a journal file, but it writes and uses log files. A new log file is -created when the current log file has reached the defined maximum size. -To define this maximum size for a log file, specify the SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT flag. -Default value is 10 MB for the Berkeley DB SQL interface. -</dd> + For SQLite, this pragma identifies the + maximum size that the journal file is allowed to + be. Berkeley DB does not have a journal file, but + it writes and uses log files. A new log file is + created when the current log file has reached the + defined maximum size. To define this maximum size + for a log file, specify the + SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT flag. Default + value is 10 MB for the Berkeley DB SQL interface. + </dd> </dl> </div> </div> @@ -298,38 +380,38 @@ Default value is 10 MB for the Berkeley DB SQL interface. <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp249752"></a>Enabling Extensions</h3> + <h3 class="title"><a id="idp698856"></a>Enabling Extensions</h3> </div> </div> </div> - <p> - The Berkeley DB SQL API provides extensions such as full text - search and R-Tree index. By default, these extensions are - disabled. To enable an extension in the Berkeley DB SQL interface, - specify the related option as an argument to the configure script - using the standard environment variable, CPPFLAGS. + <p> + The Berkeley DB SQL API provides extensions such as + full text search and R-Tree index. By default, these + extensions are disabled. To enable an extension in the + Berkeley DB SQL interface, specify the related option as + an argument to the configure script using the standard + environment variable, CPPFLAGS. </p> - <p></p> <div class="variablelist"> <dl> <dt> <span class="term">SQLITE_ENABLE_FTS3</span> </dt> <dd> - Enable building the Berkeley DB full text search layer + Enable building the Berkeley DB full text + search layer </dd> <dt> <span class="term">SQLITE_ENABLE_RTREE</span> </dt> - <dd> - Enables the Berkeley DB R-Tree layer. + <dd> Enables the Berkeley DB R-Tree layer. </dd> </dl> </div> <p> - See the SQLite Documentation for more information on - <a class="ulink" href="http://www.sqlite.org/fts3.html" target="_top">full text search</a> - and <a class="ulink" href="http://www.sqlite.org/rtree.html" target="_top">R-Tree</a>. + See the SQLite Documentation for more information on + <a class="ulink" href="http://www.sqlite.org/fts3.html" target="_top">full text + search</a> and <a class="ulink" href="http://www.sqlite.org/rtree.html" target="_top">R-Tree</a>. </p> </div> <div class="sect2" lang="en" xml:lang="en"> @@ -340,28 +422,30 @@ Default value is 10 MB for the Berkeley DB SQL interface. </div> </div> </div> - <p> - This section describes how to build the JDBC driver code using - <code class="literal">autoconf</code>, which is the only method supported and - tested by the Berkeley DB team. + <p> + This section describes how to build the JDBC driver + code using <code class="literal">autoconf</code>, which is the only + method supported and tested by the Berkeley DB team. </p> - <p> - To build the JDBC driver, you must have Sun Java Development Kit - 1.1 or above installed. + <p> + To build the JDBC driver, you must have Sun Java + Development Kit 1.1 or above installed. </p> <pre class="programlisting">cd build_unix ../dist/configure --enable-jdbc --prefix=<install path> make install</pre> <p> - You can test the build by entering the following commands from the - <code class="literal">build_unix/jdbc</code> directory: + You can test the build by entering the following + commands from the <code class="literal">build_unix/jdbc</code> + directory: </p> <table class="simplelist" border="0" summary="Simple list"> <tr> <td>javac -classpath ./sqlite.jar test3.java</td> </tr> <tr> - <td>java -Djava.library.path=./.libs -classpath ./sqlite.jar:. test3 </td> + <td>java -Djava.library.path=./.libs -classpath + ./sqlite.jar:. test3 </td> </tr> </table> </div> @@ -369,87 +453,98 @@ Default value is 10 MB for the Berkeley DB SQL interface. <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp327120"></a>Using the JDBC Driver</h3> + <h3 class="title"><a id="idp704816"></a>Using the JDBC Driver</h3> </div> </div> </div> <p> - This section describes how to download, build, and run sample - programs using the built JDBC driver. + This section describes how to download, build, and run + sample programs using the built JDBC driver. </p> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp327616"></a>Downloading JDBC Sample Code</h4> + <h4 class="title"><a id="idp722352"></a>Downloading JDBC Sample Code</h4> </div> </div> </div> <p> - The download link for JDBC sample code is available on the - <a class="ulink" href="http://www.oracle.com/technetwork/java/index-139949.html" target="_top"> - Oracle Technology Network (OTN) - </a> page. You can identify the link by the "JDBC - programming examples from all three editions (ZIP format)" text - beside it. + The download link for JDBC sample code is available + on the <a class="ulink" href="http://www.oracle.com/technetwork/java/index-139949.html" target="_top"> + Oracle Technology Network (OTN) </a> page. + You can identify the link by the "JDBC programming + examples from all three editions (ZIP format)" text + beside it. </p> </div> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp322288"></a>Modifying Sample Code</h4> + <h4 class="title"><a id="idp697912"></a>Modifying Sample Code</h4> </div> </div> </div> <p> - Before running the example code, do the following: + Before running the example code, do the following: </p> <div class="orderedlist"> <ol type="1"> - <li> - Unzip the file containing the sample code to a new - directory (for example, jdbc_ex). + <li> + Unzip the file containing the sample code + to a new directory (for example, jdbc_ex). </li> <li> - <p> + <p> Substitute - <code class="literal">jdbc:sqlite:/<db-file-name></code> for - the generic JDBC URL that appears in the code. That is, put <code class="literal">jdbc:sqlite:/<db-file-name></code> - between the quotation marks in the line: + for the generic JDBC URL that appears in the + code. That is, put + <code class="literal">jdbc:sqlite:/<db-file-name></code> + between the quotation marks in the line: </p> <p> - <code class="literal">String url = "jdbc:mySubprotocol:myDataSource";</code> + <code class="literal">String url = + "jdbc:mySubprotocol:myDataSource";</code> + </p> + <p> + Note: The <db-file-name> can either + be an absolute path name like + <code class="literal">"jdbc:sqlite://jdbc_ex_db/myDataSource"</code>, + or a relative path-file-name like + <code class="literal">"jdbc:sqlite:/../jdbc_ex_db/myDataSource"</code>, + or a file name, like + <code class="literal">"jdbc:sqlite:/myDataSource"</code>, + in which case the database file will be stored + at the current directory. Note that all path + arguments require a leading slash, even in the + case of relative paths or a database in the + local directory. Please refer to the above + examples. </p> - <p> - Note: The <db-file-name> can either be an - absolute path name like - <code class="literal">"/jdbc_ex_db/myDataSource"</code>, or a - relative path-file-name like - <code class="literal">"../jdbc_ex_db/myDataSource"</code>, or a - file name, like <code class="literal">"myDataSource"</code>, in - which case the database file will be stored at the current - directory.</p> </li> <li> - Substitute <code class="literal">SQLite.JDBCDriver</code> for - <code class="literal">myDriver.ClassName</code> in the line: - <code class="literal">Class.forName("myDriver.ClassName");</code></li> + Substitute + <code class="literal">SQLite.JDBCDriver</code> for + <code class="literal">myDriver.ClassName</code> in the + line: + <code class="literal">Class.forName("myDriver.ClassName");</code></li> <li> <p> - Optionally substitute the username and password you use for your - database in the following: - <code class="literal">"myLogin", "myPassword"</code>. + Optionally substitute the username and + password you use for your database in the + following: <code class="literal">"myLogin", + "myPassword"</code>. </p> </li> - <li> - If your JDK version is above 1.5, change the variable name - <code class="literal">enum</code> in - <code class="literal">OutputApplet.java</code> to some other variable - name because, as of JDK release 5 <code class="literal">enum</code> - is a keyword and can not be used as an - identifier. + <li> + If your JDK version is above 1.5, change + the variable name <code class="literal">enum</code> in + <code class="literal">OutputApplet.java</code> to some + other variable name because, as of JDK release 5 + <code class="literal">enum</code> is a keyword and can + not be used as an identifier. </li> </ol> </div> @@ -458,44 +553,44 @@ Default value is 10 MB for the Berkeley DB SQL interface. <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp323472"></a>Building and Running the JDBC Sample code</h4> + <h4 class="title"><a id="idp710816"></a>Building and Running the JDBC Sample code</h4> </div> </div> </div> - <p> - See - <a class="xref" href="build_unix_sql.html#build_unix_jdbc" title="Building the JDBC Driver">Building the JDBC Driver</a> - for instructions on building the JDBC driver. + <p> + See <a class="xref" href="build_unix_sql.html#build_unix_jdbc" title="Building the JDBC Driver">Building the JDBC Driver</a> for instructions + on building the JDBC driver. </p> - <p> - To build and run the JDBC examples do the following: + <p> + To build and run the JDBC examples do the + following: </p> <div class="orderedlist"> <ol type="1"> <li> - Copy <code class="literal">build_unix/jdbc/sqlite.jar</code> and + Copy + <code class="literal">build_unix/jdbc/sqlite.jar</code> + and <code class="literal">build_unix/jdbc/.libs/libsqlite_jni.so</code> - to the <code class="literal">jdbc_ex</code> directory. + to the <code class="literal">jdbc_ex</code> directory. </li> <li> - <p> - In the <code class="literal">jdbc_ex</code> directory, run the - following commands: + <p> + In the <code class="literal">jdbc_ex</code> + directory, run the following commands: </p> - <pre class="programlisting"> - $ javac -classpath ./sqlite.jar *.java + <pre class="programlisting">$ javac -classpath ./sqlite.jar *.java $ java -classpath .:sqlite.jar -Djava.library.path=. \ - <ClassName, eg. CreateCoffees> - </pre> + <ClassName, eg. CreateCoffees></pre> </li> - <li> - After you run the CreateCoffees example, use the - <code class="literal">dbsql</code> executable to open the - <code class="literal">myDataSource</code> database file and check if - the table <code class="literal">COFFEES</code> has been successfully - created in the database. - <pre class="programlisting"> - $ dbsql myDataSourcedbsql> .tables + <li> + After you run the CreateCoffees example, + use the <code class="literal">dbsql</code> executable to + open the <code class="literal">myDataSource</code> database + file and check if the table + <code class="literal">COFFEES</code> has been + successfully created in the database. + <pre class="programlisting">$ dbsql myDataSourcedbsql> .tables COFFEES dbsql> .dump PRAGMA foreign_keys=OFF; @@ -503,17 +598,16 @@ Default value is 10 MB for the Berkeley DB SQL interface. CREATE TABLE COFFEES (COF_NAME varchar(32),\ SUP_ID int, PRICE float, SALES int, TOTAL int); COMMIT; - dbsql> - </pre></li> + dbsql></pre></li> <li> <p> - Repeat step 3 to run other examples. + Repeat step 3 to run other examples. </p> <p> - Note: Some examples, such as AutoGenKeys, are not yet - supported by BDB JDBC driver. The - <code class="literal">SQLFeatureNotSupportedException</code> is - displayed for those unsupported examples. + Note: Some examples, such as AutoGenKeys, + are not yet supported by BDB JDBC driver. The + <code class="literal">SQLFeatureNotSupportedException</code> + is displayed for those unsupported examples. </p> </li> </ol> @@ -524,36 +618,36 @@ Default value is 10 MB for the Berkeley DB SQL interface. <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp349152"></a>Building the ODBC Driver</h3> + <h3 class="title"><a id="idp736952"></a>Building the ODBC Driver</h3> </div> </div> </div> - <p> + <p> This section describes how to build the ODBC driver. </p> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp342536"></a>Configuring Your System</h4> + <h4 class="title"><a id="idp730032"></a>Configuring Your System</h4> </div> </div> </div> <p> - To configure your system prior to building the ODBC driver, do - the following: + To configure your system prior to building the ODBC + driver, do the following: </p> <div class="orderedlist"> <ol type="1"> <li> - Download and install the latest - <a class="ulink" href="http://www.unixodbc.org" target="_top">unixODBC</a> + Download and install the latest <a class="ulink" href="http://www.unixodbc.org" target="_top">unixODBC</a> if ODBC is not already installed on your system. </li> - <li> - Configure the ODBC server to work with SQLite databases. Follow - <a class="ulink" href="http://www.ch-werner.de/sqliteodbc/html/index.html" target="_top">these instructions</a> - from Christian Werner. + <li> + Configure the ODBC server to work with + SQLite databases. Follow <a class="ulink" href="http://www.ch-werner.de/sqliteodbc/html/index.html" target="_top"> + these instructions</a> from Christian + Werner. </li> </ol> </div> @@ -562,71 +656,79 @@ Default value is 10 MB for the Berkeley DB SQL interface. <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp353984"></a>Building the Library</h4> + <h4 class="title"><a id="idp741624"></a>Building the Library</h4> </div> </div> </div> - <p> - To build the library, do the following: + <p> + To build the library, do the following: </p> <pre class="programlisting"> - $ cd db-5.3.XX/build_unix + $ cd db-6.1.XX/build_unix $ CFLAGS="-fPIC" ../dist/configure --enable-sql_compat --disable-shared $ make $ cd ../lang/sql/odbc - $ CFLAGS="-DHAVE_ERRNO_H -I../../../build_unix -I../../../src/dbinc \ - -I../sqlite/src" LDFLAGS="../../../build_unix/libdb-5.3.a" \ + $ CFLAGS="-D_HAVE_SQLITE_CONFIG_H \ + -I../../../build_unix -I../../../build_unix/sql \ + -I../../../src/dbinc -I../sqlite/src" \ + LDFLAGS="../../../build_unix/libdb-6.1.a" \ ./configure --with-sqlite3=../generated - $ make - </pre> + $ make</pre> <p> - The <code class="literal">libsqlite3odbc.so</code> library containing a - statically linked version of Berkeley DB SQL is now - built. + The <code class="literal">libsqlite3odbc.so</code> library + containing a statically linked version of Berkeley DB + SQL is now built. </p> <p> - NOTE: The final <code class="literal">make</code> command above is known - to generate a warning when using GCC. The warning states: - <code class="literal">Warning: Linking the shared library libsqlite3odbc.la - against the static library ../../build_unix/libdb-5.3.a is - not portable!</code>. It is generally safe to ignore the - warning when using the generated library. + NOTE: The final <code class="literal">make</code> command + above is known to generate a warning when using GCC. + The warning states: <code class="literal">Warning: Linking the + shared library libsqlite3odbc.la against the + static library + ../../build_unix/libdb-6.1.a is not + portable!</code>. It is generally safe to + ignore the warning when using the generated library. </p> </div> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp357536"></a>Testing the ODBC Driver</h4> + <h4 class="title"><a id="idp745064"></a>Testing the ODBC Driver</h4> </div> </div> </div> <p> - The steps to verify that the installed driver works are as follows: + The steps to verify that the installed driver works + are as follows: </p> <div class="orderedlist"> <ol type="1"> - <li> - Alter the <code class="literal">/etc/odbcinst.ini</code> and - <code class="literal">~/.odbc.ini</code> configuration files to refer - to the libsqlite3odbc.so file built above. + <li> + Alter the + <code class="literal">/etc/odbcinst.ini</code> and + <code class="literal">~/.odbc.ini</code> configuration + files to refer to the libsqlite3odbc.so file built + above. </li> <li> - <p> - Create a data source, and launch a data source viewer - application by doing the following: + <p> + Create a data source, and launch a data + source viewer application by doing the + following: </p> <pre class="programlisting">$ mkdir ~/databases $ cd ~/databases $ /path/to/Berkeley DB/build_unix/sqlite3 mytest.db dbsql> CREATE TABLE t1(x); - dbsql> .quit; + dbsql> .quit $ DataManager </pre> - <p> - The final step opens a GUI application that displays - ODBC data sources on a system. You should be able to - find the <code class="literal">mytest.db</code> data source just - created. + <p> + The final step opens a GUI application that + displays ODBC data sources on a system. You + should be able to find the + <code class="literal">mytest.db</code> data source + just created. </p> </li> </ol> @@ -641,12 +743,13 @@ Default value is 10 MB for the Berkeley DB SQL interface. </div> </div> </div> - <p> - The BFILE extension allows you to store binary files outside of - the database, but still operate upon them as if they were - stored within the database. To enable this extension, use the - <code class="literal">--enable-load-extension</code> configuration flag. - For example: + <p> + The BFILE extension allows you to store binary files + outside of the database, but still operate upon them as if + they were stored within the database. To enable this + extension, use the + <code class="literal">--enable-load-extension</code> + configuration flag. For example: </p> <pre class="programlisting">$ cd <db>/build_unix $ export DBSQL_DIR=$PWD/../install @@ -658,25 +761,26 @@ $ make && make install</pre> BFILE extensions are only supported for Unix platforms. </p> <p> - Note that the extension support has two - interfaces: SQL expressions and a C-functions API. By default, - the SQL expressions are built when you use + Note that the extension support has two interfaces: SQL + expressions and a C-functions API. By default, the SQL + expressions are built when you use <code class="literal">--enable-load_extension</code>. To use the - C-functions API, edit <code class="literal"><db>/lang/sql/ext/bfile/build/Makefile</code> - and set <code class="literal">ENABLE_BFILE_CAPI</code> - to <code class="literal">1</code>. + C-functions API, edit + <code class="literal"><db>/lang/sql/ext/bfile/build/Makefile</code> + and set <code class="literal">ENABLE_BFILE_CAPI</code> to + <code class="literal">1</code>. </p> - <p> - Once you have enabled the extension and built the library, you - can run the included example: + <p> + Once you have enabled the extension and built the + library, you can run the included example: </p> <pre class="programlisting">$ cd lang/sql/sqlite/ext/bfile/build $ export LD_LIBRARY_PATH=$PWD:$DBSQL_DIR/lib $ ./bfile_example_sql # for SQL expressions interface $ ./bfile_example_capi # for C-functions API</pre> - <p> - For more information on using the BFILE extension, see the - <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide. + <p> + For more information on using the BFILE extension, see + the <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide. </p> </div> </div> diff --git a/docs/installation/build_unix_stacksize.html b/docs/installation/build_unix_stacksize.html index 15208b7b..e88ddc8e 100644 --- a/docs/installation/build_unix_stacksize.html +++ b/docs/installation/build_unix_stacksize.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> <link rel="prev" href="upgrade_11gr2_remsupp.html" title="Dropped Support" /> <link rel="next" href="changelog_5_0.html" title="Berkeley DB 11g Release 2 Change Log" /> </head> <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="upgrade_11gr2_remsupp.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </th> + <th width="60%" align="center">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </th> <td width="20%" align="right"> <a accesskey="n" href="changelog_5_0.html">Next</a></td> </tr> </table> @@ -38,8 +36,15 @@ </div> </div> </div> - <p>Prior to the 11gR2 release, Berkeley DB limited the stack size for threads it created using the POSIX thread API to 128 KB for 32-bit platforms and 256 KB for 64-bit platforms. In this release, the system default stack size is used unless you run the Berkeley DB configure script with the <code class="literal">--with-stacksize=SIZE</code> argument to override the default. -</p> + <p> + Prior to the 11gR2 release, Berkeley DB limited the stack + size for threads it created using the POSIX thread API to 128 + KB for 32-bit platforms and 256 KB for 64-bit platforms. In + this release, the system default stack size is used unless you + run the Berkeley DB configure script with the + <code class="literal">--with-stacksize=SIZE</code> argument to + override the default. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/build_unix_sunos.html b/docs/installation/build_unix_sunos.html index 04d17e35..36bfcf7f 100644 --- a/docs/installation/build_unix_sunos.html +++ b/docs/installation/build_unix_sunos.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,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_solaris.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_vxworks.html">Next</a></td> </tr> </table> @@ -42,13 +41,17 @@ <ol type="1"> <li> <span class="bold"> - <strong>I can't specify the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> flag to <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a>.</strong> + <strong>I can't specify the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> + flag to <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a>.</strong> </span> - <p>The <code class="literal">shmget</code>(2) interfaces are not used on SunOS releases prior -to 5.0, even though they apparently exist, because the distributed -include files did not allow them to be compiled. For this reason, it -will not be possible to specify the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> flag to those -versions of SunOS.</p> + <p> + The <code class="literal">shmget</code>(2) interfaces are not + used on SunOS releases prior to 5.0, even though they + apparently exist, because the distributed include + files did not allow them to be compiled. For this + reason, it will not be possible to specify the + <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> flag to those versions of SunOS. + </p> </li> </ol> </div> @@ -68,9 +71,7 @@ versions of SunOS.</p> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 8. - Building Berkeley DB for VxWorks - </td> + <td width="40%" align="right" valign="top"> Chapter 8. Building Berkeley DB for VxWorks </td> </tr> </table> </div> diff --git a/docs/installation/build_unix_test.html b/docs/installation/build_unix_test.html index 20271b22..4aa5fe83 100644 --- a/docs/installation/build_unix_test.html +++ b/docs/installation/build_unix_test.html @@ -14,17 +14,17 @@ <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">Running the test suite under UNIX</th> + <th colspan="3" align="center">Running the test suite under + UNIX</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_shlib.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_notes.html">Next</a></td> </tr> </table> @@ -34,7 +34,8 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_unix_test"></a>Running the test suite under UNIX</h2> + <h2 class="title" style="clear: both"><a id="build_unix_test"></a>Running the test suite under + UNIX</h2> </div> </div> </div> @@ -47,38 +48,54 @@ </dt> </dl> </div> - <p>The Berkeley DB test suite is built if you specify -<a class="link" href="build_unix_conf.html#build_unix_conf.--enable-test">--enable-test</a> -as an argument when configuring Berkeley DB. The test suite also -requires that you configure and build the Tcl interface to the -library.</p> - <p>Before running the tests for the first time, you may need to edit the -<code class="filename">include.tcl</code> file in your build directory. The -Berkeley DB configuration assumes that you intend to use the -version of the tclsh utility included in the Tcl installation with which -Berkeley DB was configured to run the test suite, and further -assumes that the test suite will be run with the libraries prebuilt in -the Berkeley DB build directory. If either of these assumptions -are incorrect, you will need to edit the <code class="filename">include.tcl</code> file and -change the following line to correctly specify the full path to the -version of tclsh with which you are going to run the test suite:</p> + <p> + The Berkeley DB test suite is built if you specify <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-test">--enable-test</a> as an argument + when configuring Berkeley DB. The test suite also requires that you configure + and build the Tcl interface to the library. + </p> + <p> + Before running the tests for the first time, you may need + to edit the <code class="filename">include.tcl</code> file in your + build directory. The Berkeley DB configuration assumes that + you intend to use the version of the tclsh utility included in + the Tcl installation with which Berkeley DB was configured to + run the test suite, and further assumes that the test suite + will be run with the libraries prebuilt in the Berkeley DB + build directory. If either of these assumptions are incorrect, + you will need to edit the <code class="filename">include.tcl</code> + file and change the following line to correctly specify the + full path to the version of tclsh with which you are going to + run the test suite: + </p> <pre class="programlisting">set tclsh_path ...</pre> - <p>You may also need to change the following line to correctly specify the -path from the directory where you are running the test suite to the -location of the Berkeley DB Tcl library you built:</p> + <p> + You may also need to change the following line to correctly + specify the path from the directory where you are running the + test suite to the location of the Berkeley DB Tcl library you + built: + </p> <pre class="programlisting">set test_path ...</pre> - <p>It may not be necessary that this be a full path if you have configured -your system's shared library mechanisms to search the directory where -you built or installed the Tcl library.</p> - <p>All Berkeley DB tests are run from within <span class="bold"><strong>tclsh</strong></span>. After -starting tclsh, you must source the file <code class="filename">test.tcl</code> in the test -directory. For example, if you built in the <code class="filename">build_unix</code> -directory of the distribution, this would be done using the following -command:</p> + <p> + It may not be necessary that this be a full path if you + have configured your system's shared library mechanisms to + search the directory where you built or installed the Tcl + library. + </p> + <p> + All Berkeley DB tests are run from within <span class="bold"><strong>tclsh</strong></span>. After starting tclsh, you + must source the file <code class="filename">test.tcl</code> in the test + directory. For example, if you built in the + <code class="filename">build_unix</code> directory of the + distribution, this would be done using the following command: + </p> <pre class="programlisting">% source ../test/tcl/test.tcl</pre> - <p>If no errors occur, you should get a "%" prompt.</p> - <p>You are now ready to run tests in the test suite; see - Running the test suite for more information.</p> + <p> + If no errors occur, you should get a "%" prompt. + </p> + <p> + You are now ready to run tests in the test suite; see + Running the test suite for more information. + </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> @@ -88,19 +105,25 @@ command:</p> </div> </div> <p> - The Berkeley DB SQL interface test suite is built if you specify -<a class="link" href="build_unix_conf.html#build_unix_conf.--enable-test">--enable-test</a> and <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-sql">--enable-sql </a> -as arguments, when configuring Berkeley DB. The test suite also -requires that you build the Berkeley DB Tcl API. -</p> + The Berkeley DB SQL interface test suite is built if + you specify <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-test"> + --enable-test</a> and <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-sql">--enable-sql + </a> as arguments, when configuring Berkeley DB. The + test suite also requires that you build the Berkeley DB + Tcl API. + </p> <pre class="programlisting"> ../dist/configure --enable-sql --enable-test --with-tcl=/usr/lib </pre> <p> -This builds the <span class="emphasis"><em>testfixture</em></span> project in <code class="literal">../build_unix/sql</code>. -</p> - <p>To enable extensions like full text search layer and R-Tree layer in the SQL test suite, configure with --enable-amalgamation. -</p> + This builds the <span class="emphasis"><em>testfixture</em></span> + project in <code class="literal">../build_unix/sql</code>. + </p> + <p> + To enable extensions like full text search layer and + R-Tree layer in the SQL test suite, configure with + --enable-amalgamation. + </p> </div> </div> <div class="navfooter"> diff --git a/docs/installation/build_vxworks.html b/docs/installation/build_vxworks.html index 98b4807c..64ec362e 100644 --- a/docs/installation/build_vxworks.html +++ b/docs/installation/build_vxworks.html @@ -14,13 +14,11 @@ <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 8. - Building Berkeley DB for VxWorks - </th> + <th colspan="3" align="center">Chapter 8. Building Berkeley DB for VxWorks </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_sunos.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="build_vxworks"></a>Chapter 8. - Building Berkeley DB for VxWorks - </h2> + <h2 class="title"><a id="build_vxworks"></a>Chapter 8. Building Berkeley DB for VxWorks </h2> </div> </div> </div> @@ -54,7 +50,8 @@ <dl> <dt> <span class="sect2"> - <a href="build_vxworks.html#idp182480">Building With Wind River Workbench using the Makefile</a> + <a href="build_vxworks.html#idp922392">Building With Wind + River Workbench using the Makefile</a> </span> </dt> </dl> @@ -68,17 +65,17 @@ <dl> <dt> <span class="sect2"> - <a href="build_vxworks_notes.html#idp491336">Building and Running the Demo Program</a> + <a href="build_vxworks_notes.html#idp934576">Building and Running the Demo Program</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_vxworks_notes.html#idp518216">Building and Running the Utility Programs</a> + <a href="build_vxworks_notes.html#idp896400">Building and Running the Utility Programs</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_vxworks_notes.html#idp518576">Support for Replication Manager</a> + <a href="build_vxworks_notes.html#idp923512">Support for Replication Manager</a> </span> </dt> </dl> @@ -102,7 +99,8 @@ <dl> <dt> <span class="sect2"> - <a href="build_vxworks.html#idp182480">Building With Wind River Workbench using the Makefile</a> + <a href="build_vxworks.html#idp922392">Building With Wind + River Workbench using the Makefile</a> </span> </dt> </dl> @@ -111,41 +109,67 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp182480"></a>Building With Wind River Workbench using the Makefile</h3> + <h3 class="title"><a id="idp922392"></a>Building With Wind + River Workbench using the Makefile</h3> </div> </div> </div> - <p>In VxWorks6.x, developers use Wind River Workbench for software -development. Two makefiles are provided in the db/build_vxworks -directory. Use them to build Berkeley DB or Berkeley DB small build, using -the build chain provided with Wind River Workbench. </p> - <p>We assume that you have installed all necessary VxWorks6.x software -including the Wind River Workbench, and that you know how to use it. </p> - <p>Use the following steps to build Berkeley DB: </p> - <p>1. Setting variables in the Makefile. -Open the Makefile and modify the BDB_ROOT variable to the path of your -Berkeley DB source tree's root directory. You may need to set other -variables when you build on different platforms, such as BUILD_SPEC, -DEBUG_MODE, PROJECT_TYPE, CC_ARCH_SPEC, VXVER, build tool flags, and BUILD_SPEC specific settings. -Please refer to the documentation of the Workbench for a complete list of -available values of each variable. You can also find out the list of values -by creating a project using the Workbench. Each variable's available values -will be listed in the GUI window which assigns values to that -variable. </p> - <p>2. Make sure "make" can be found. -Basically you need to set the make utility's path to environment variables. -</p> - <p>3. Start up the wrenv utility of the Wind River Workbench. </p> - <p>4. In the command console, move to the $(BDB_ROOT)/build_vxworks/ directory, -rename the target makefile (Makefile.6x or Makefile.6x.small) to "Makefile", -and run "make". The make process will start and create the directory -"bdbvxw". It will contain all intermediate object files as well as the -final built image "bdbvxw.out". </p> - <p>5. After the "bdbvxw.out" image is built, you can use command tools -or the Workbench IDE to download and run it.</p> - <p>6. Test and Verification. -There is a dbdemo and test_micro, which you can run to verify whether -everything works fine.</p> + <p> + In VxWorks6.x, developers use Wind River Workbench for + software development. Two makefiles are provided in the + db/build_vxworks directory. Use them to build Berkeley DB + or Berkeley DB small build, using the build chain provided + with Wind River Workbench. + </p> + <p> + We assume that you have installed all necessary + VxWorks6.x software including the Wind River Workbench, + and that you know how to use it. + </p> + <p> + Use the following steps to build Berkeley DB: + </p> + <p> + 1. Setting variables in the Makefile. Open the Makefile + and modify the BDB_ROOT variable to the path of your + Berkeley DB source tree's root directory. You may need to + set other variables when you build on different platforms, + such as BUILD_SPEC, DEBUG_MODE, PROJECT_TYPE, + CC_ARCH_SPEC, VXVER, build tool flags, and BUILD_SPEC + specific settings. Please refer to the documentation of + the Workbench for a complete list of available values of + each variable. You can also find out the list of values by + creating a project using the Workbench. Each variable's + available values will be listed in the GUI window which + assigns values to that variable. + </p> + <p> + 2. Make sure "make" can be found. Basically you need to + set the make utility's path to environment variables. + </p> + <p> + 3. Start up the wrenv utility of the Wind River + Workbench. + </p> + <p> + 4. In the command console, move to the + $(BDB_ROOT)/build_vxworks/ directory, rename the target + makefile (Makefile.6x or Makefile.6x.small) to "Makefile", + and run "make". The make process will start and create the + directory "bdbvxw". It will contain all intermediate + object files as well as the final built image + "bdbvxw.out". + </p> + <p> + 5. After the "bdbvxw.out" image is built, you can use + command tools or the Workbench IDE to download and run + it. + </p> + <p> + 6. Test and Verification. There is a dbdemo and + test_micro, which you can run to verify whether everything + works fine. + </p> </div> </div> </div> diff --git a/docs/installation/build_vxworks_faq.html b/docs/installation/build_vxworks_faq.html index ce35eb75..2b039005 100644 --- a/docs/installation/build_vxworks_faq.html +++ b/docs/installation/build_vxworks_faq.html @@ -9,12 +9,12 @@ <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> <link rel="up" href="build_vxworks.html" title="Chapter 8. Building Berkeley DB for VxWorks" /> <link rel="prev" href="build_vxworks_notes.html" title="VxWorks notes" /> - <link rel="next" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="next" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> </head> <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,10 +22,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_vxworks_notes.html">Prev</a> </td> - <th width="60%" align="center">Chapter 8. - Building Berkeley DB for VxWorks - </th> - <td width="20%" align="right"> <a accesskey="n" href="upgrade_53_toc.html">Next</a></td> + <th width="60%" align="center">Chapter 8. Building Berkeley DB for VxWorks </th> + <td width="20%" align="right"> <a accesskey="n" href="upgrade_61_toc.html">Next</a></td> </tr> </table> <hr /> @@ -42,171 +40,247 @@ <ul type="disc"> <li> <span class="bold"> - <strong>I get the error "Workspace open failed: This project workspace is an -older format.", when trying to open the supplied workspace on Tornado 2.0 -under Windows.</strong> + <strong>I get the error "Workspace open + failed: This project workspace is an older format.", + when trying to open the supplied workspace on Tornado + 2.0 under Windows.</strong> </span> - <p>This error will occur if the files were extracted in a manner that adds -a CR/LF to lines in the file. Make sure that you download the Berkeley DB -".zip" version of the Berkeley DB distribution, and, when extracting the Berkeley DB -sources, that you use an unzipper program that will not do any -conversion.</p> + <p> + This error will occur if the files were extracted in + a manner that adds a CR/LF to lines in the file. Make + sure that you download the Berkeley DB ".zip" version + of the Berkeley DB distribution, and, when extracting + the Berkeley DB sources, that you use an unzipper + program that will not do any conversion. + </p> </li> <li> <span class="bold"> - <strong>I sometimes see spurious output errors about temporary directories.</strong> + <strong>I sometimes see spurious output + errors about temporary directories.</strong> </span> - <p>These messages are coming from the <code class="literal">stat</code>(2) function call -in VxWorks. Unlike other systems, there may not be a well known -temporary directory on the target. Therefore, we highly recommend that -all applications use <a href="../api_reference/C/envset_tmp_dir.html" class="olink">DB_ENV->set_tmp_dir()</a> to -specify a temporary directory for the application.</p> + <p> + These messages are coming from the + <code class="literal">stat</code>(2) function call in + VxWorks. Unlike other systems, there may not be a well + known temporary directory on the target. Therefore, we + highly recommend that all applications use + <a href="../api_reference/C/envset_tmp_dir.html" class="olink">DB_ENV->set_tmp_dir()</a> to specify a temporary directory for + the application. + </p> </li> <li> <span class="bold"> - <strong>How can I build Berkeley DB without using Tornado?</strong> + <strong>How can I build Berkeley DB without + using Tornado?</strong> </span> - <p>The simplest way to build Berkeley DB without using Tornado is to configure -Berkeley DB on a UNIX system, and then use the Makefile and include files -generated by that configuration as the starting point for your build. -The Makefile and include files are created during configuration, in the -current directory, based on your configuration decisions (for example, -debugging vs. non-debugging builds), so you'll need to configure the -system for the way you want Berkeley DB to be built.</p> - <p>Additionally, you'll need to account for the slight difference between -the set of source files used in a UNIX build and the set used in a -VxWorks build. You can use the following command to create a list of -the Berkeley DB VxWorks files. The commands assume you are in the build_vxworks -directory of the Berkeley DB distribution:</p> + <p> + The simplest way to build Berkeley DB without using + Tornado is to configure Berkeley DB on a UNIX system, + and then use the Makefile and include files generated + by that configuration as the starting point for your + build. The Makefile and include files are created + during configuration, in the current directory, based + on your configuration decisions (for example, + debugging vs. non-debugging builds), so you'll need to + configure the system for the way you want Berkeley DB + to be built. + </p> + <p> + Additionally, you'll need to account for the slight + difference between the set of source files used in a + UNIX build and the set used in a VxWorks build. You + can use the following command to create a list of the + Berkeley DB VxWorks files. The commands assume you are + in the build_vxworks directory of the Berkeley DB + distribution: + </p> <pre class="programlisting">% cat > /tmp/files.sed s/<BEGIN> FILE_// s/_objects// ^D % grep FILE_ BerkeleyDB.wpj | grep _objects | sed -f /tmp/files.sed \ > /tmp/db.files</pre> - <p>You will then have a template Makefile and include files, and a list of -VxWorks-specific source files. You will need to convert this Makefile -and list of files into a form that is acceptable to your specific build -environment.</p> + <p> + You will then have a template Makefile and include + files, and a list of VxWorks-specific source files. + You will need to convert this Makefile and list of + files into a form that is acceptable to your specific + build environment. + </p> </li> <li> <span class="bold"> - <strong>Does Berkeley DB use floating point registers?</strong> + <strong>Does Berkeley DB use floating point + registers?</strong> </span> - <p>Yes, there are a few places in Berkeley DB where floating point computations -are performed. As a result, all applications that call -<span class="emphasis"><em>taskSpawn</em></span> should specify the <span class="bold"><strong>VX_FP_TASK</strong></span> option.</p> + <p> + Yes, there are a few places in Berkeley DB where + floating point computations are performed. As a + result, all applications that call + <span class="emphasis"><em>taskSpawn</em></span> should specify the + <span class="bold"><strong>VX_FP_TASK</strong></span> + option. + </p> </li> <li> <span class="bold"> - <strong>Can I run the test suite under VxWorks?</strong> + <strong>Can I run the test suite under + VxWorks?</strong> </span> - <p>The test suite requires the Berkeley DB Tcl library. In turn, this library -requires Tcl 8.5 or greater. In order to run the test suite, you would -need to port Tcl 8.5 or greater to VxWorks. The Tcl shell included in -<span class="emphasis"><em>windsh</em></span> is not adequate for two reasons. First, it is based on -Tcl 8.0. Second, it does not include the necessary Tcl components for -adding a Tcl extension.</p> + <p> + The test suite requires the Berkeley DB Tcl library. + In turn, this library requires Tcl 8.5 or greater. In + order to run the test suite, you would need to port + Tcl 8.5 or greater to VxWorks. The Tcl shell included + in <span class="emphasis"><em>windsh</em></span> is not adequate for two + reasons. First, it is based on Tcl 8.0. Second, it + does not include the necessary Tcl components for + adding a Tcl extension. + </p> </li> <li> <span class="bold"> - <strong>Are all Berkeley DB features available for VxWorks?</strong> + <strong>Are all Berkeley DB features + available for VxWorks?</strong> </span> - <p>All Berkeley DB features are available for VxWorks with the exception of the -<a href="../api_reference/C/dbopen.html#open_DB_TRUNCATE" class="olink">DB_TRUNCATE</a> flag for <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a>. The underlying mechanism -needed for that flag is not available consistently across different file -systems for VxWorks.</p> + <p> + All Berkeley DB features are available for VxWorks + with the exception of the <a href="../api_reference/C/dbopen.html#open_DB_TRUNCATE" class="olink">DB_TRUNCATE</a> flag for + <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a>. The underlying mechanism needed for that + flag is not available consistently across different + file systems for VxWorks. + </p> </li> <li> <span class="bold"> - <strong>Are there any constraints using particular filesystem drivers?</strong> + <strong>Are there any constraints using + particular filesystem drivers?</strong> </span> - <p>There are constraints using the dosFs filesystems with Berkeley DB. Namely, -you must configure your dosFs filesystem to support long filenames if -you are using Berkeley DB logging in your application. The VxWorks' dosFs -1.0 filesystem, by default, uses the old MS-DOS 8.3 file-naming -constraints, restricting to 8 character filenames with a 3 character -extension. If you have configured with VxWorks' dosFs 2.0 you should -be compatible with Windows FAT32 filesystems which supports long -filenames.</p> + <p> + There are constraints using the dosFs filesystems + with Berkeley DB. Namely, you must configure your + dosFs filesystem to support long filenames if you are + using Berkeley DB logging in your application. The + VxWorks' dosFs 1.0 filesystem, by default, uses the + old MS-DOS 8.3 file-naming constraints, restricting to + 8 character filenames with a 3 character extension. If + you have configured with VxWorks' dosFs 2.0 you should + be compatible with Windows FAT32 filesystems which + supports long filenames. + </p> </li> <li> <span class="bold"> - <strong>Are there any dependencies on particular filesystem drivers?</strong> + <strong>Are there any dependencies on + particular filesystem drivers?</strong> </span> - <p>There is one dependency on specifics of filesystem drivers in the port -of Berkeley DB to VxWorks. Berkeley DB synchronizes data using the FIOSYNC function -to ioctl() (another option would have been to use the FIOFLUSH function -instead). The FIOSYNC function was chosen because the NFS client driver, -nfsDrv, only supports it and doesn't support FIOFLUSH. All local file -systems, as of VxWorks 5.4, support FIOSYNC -- with the exception of -rt11fsLib, which only supports FIOFLUSH. To use rt11fsLib, you will need -to modify the os/os_fsync.c file to use the FIOFLUSH function; note that -rt11fsLib cannot work with NFS clients.</p> + <p> + There is one dependency on specifics of filesystem + drivers in the port of Berkeley DB to VxWorks. + Berkeley DB synchronizes data using the FIOSYNC + function to ioctl() (another option would have been to + use the FIOFLUSH function instead). The FIOSYNC + function was chosen because the NFS client driver, + nfsDrv, only supports it and doesn't support FIOFLUSH. + All local file systems, as of VxWorks 5.4, support + FIOSYNC -- with the exception of rt11fsLib, which only + supports FIOFLUSH. To use rt11fsLib, you will need to + modify the os/os_fsync.c file to use the FIOFLUSH + function; note that rt11fsLib cannot work with NFS + clients. + </p> </li> <li> <p> - <span class="bold"> - <strong>Are there any known filesystem problems?</strong> - </span> - </p> - <p>During the course of our internal testing, we came across three problems -with the dosFs 2.0 filesystem that warranted patches from Wind River Systems. -We strongly recommend you upgrade to dosFs 2.2, <span class="bold"><strong>SPR 79795 (x86)</strong></span> -and <span class="bold"><strong>SPR 79569 (PPC)</strong></span> which fixes all of these problems and -many more. You should ask Wind River Systems for the patches to these -problems if you encounter them and are unable to upgrade to dosFs 2.2.</p> - <p>The first problem is that files will seem to disappear. You should -look at <span class="bold"><strong>SPR 31480</strong></span> in the Wind River Systems' Support pages for -a more detailed description of this problem.</p> - <p>The second problem is a semaphore deadlock within the dosFs filesystem -code. Looking at a stack trace via CrossWind, you will see two or more of -your application's tasks waiting in semaphore code within dosFs. The patch -for this problem is under <span class="bold"><strong>SPR 33221</strong></span> at Wind River Systems. -There are several SPR numbers at Wind River Systems that refer to this -particular problem.</p> - <p>The third problem is that all tasks will hang on a dosFs semaphore. You should -look at <span class="bold"><strong>SPR 72063</strong></span> in the Wind River Systems' Support pages for -a more detailed description of this problem.</p> + <span class="bold"><strong>Are there any known filesystem + problems?</strong></span> + </p> + <p> + During the course of our internal testing, we came + across three problems with the dosFs 2.0 filesystem + that warranted patches from Wind River Systems. We + strongly recommend you upgrade to dosFs 2.2, <span class="bold"><strong>SPR 79795 (x86)</strong></span> and + <span class="bold"><strong>SPR 79569 (PPC)</strong></span> + which fixes all of these problems and many more. You + should ask Wind River Systems for the patches to these + problems if you encounter them and are unable to + upgrade to dosFs 2.2. + </p> + <p> + The first problem is that files will seem to + disappear. You should look at <span class="bold"><strong>SPR 31480</strong></span> + in the Wind River Systems' Support pages for a more detailed description of this + problem. + </p> + <p> + The second problem is a semaphore deadlock within + the dosFs filesystem code. Looking at a stack trace + via CrossWind, you will see two or more of your + application's tasks waiting in semaphore code within + dosFs. The patch for this problem is under <span class="bold"><strong>SPR 33221</strong></span> at Wind River + Systems. There are several SPR numbers at Wind River + Systems that refer to this particular problem. + </p> + <p> + The third problem is that all tasks will hang on a + dosFs semaphore. You should look at <span class="bold"><strong>SPR 72063</strong></span> in the Wind River + Systems' Support pages for a more detailed description + of this problem. + </p> </li> <li> <p> - <span class="bold"> - <strong>Are there any filesystems I cannot use?</strong> - </span> - </p> - <p>Currently both the Target Server File System (TSFS) and NFS are not able -to be used.</p> - <p>The Target Server File System (TSFS) uses the netDrv driver. This driver -does not support any ioctl that allows flushing to the disk, nor does -it allow renaming of files via FIORENAME. -The NFS file system uses nfsDrv and that driver -does not support FIORENAME and cannot be used -with Berkeley DB. </p> + <span class="bold"><strong>Are there any filesystems I + cannot use?</strong></span> + </p> + <p> + Currently both the Target Server File System (TSFS) + and NFS are not able to be used. + </p> + <p> + The Target Server File System (TSFS) uses the netDrv + driver. This driver does not support any ioctl that + allows flushing to the disk, nor does it allow + renaming of files via FIORENAME. The NFS file system + uses nfsDrv and that driver does not support FIORENAME + and cannot be used with Berkeley DB. + </p> </li> <li> <span class="bold"> - <strong>What VxWorks primitives are used for mutual exclusion in Berkeley DB?</strong> + <strong>What VxWorks primitives are used for + mutual exclusion in Berkeley DB?</strong> </span> - <p>Mutexes inside of Berkeley DB use the basic binary semaphores in VxWorks. The -mutexes are created using the FIFO queue type.</p> + <p> + Mutexes inside of Berkeley DB use the basic binary + semaphores in VxWorks. The mutexes are created using + the FIFO queue type. + </p> </li> <li> <span class="bold"> - <strong>What are the implications of VxWorks' mutex implementation -using microkernel resources?</strong> + <strong>What are the implications of + VxWorks' mutex implementation using microkernel + resources?</strong> </span> - <p>On VxWorks, the semaphore primitives implementing mutexes consume system -resources. Therefore, if an application unexpectedly fails, those -resources could leak. Berkeley DB solves this problem by always allocating -mutexes in the persistent shared memory regions. Then, if an -application fails, running recovery or explicitly removing the database -environment by calling the <a href="../api_reference/C/envremove.html" class="olink">DB_ENV->remove()</a> method will allow Berkeley DB to -release those previously held mutex resources. If an application -specifies the <a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag (choosing not to use persistent -shared memory), and then fails, mutexes allocated in that private memory -may leak their underlying system resources. Therefore, the -<a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a> flag should be used with caution on VxWorks.</p> + <p> + On VxWorks, the semaphore primitives implementing + mutexes consume system resources. Therefore, if an + application unexpectedly fails, those resources could + leak. Berkeley DB solves this problem by always + allocating mutexes in the persistent shared memory + regions. Then, if an application fails, running + recovery or explicitly removing the database + environment by calling the <a href="../api_reference/C/envremove.html" class="olink">DB_ENV->remove()</a> method will + allow Berkeley DB to release those previously held + mutex resources. If an application specifies the + <a href="../api_reference/C/envopen.html#envopen_DB_PRIVATE" class="olink">DB_PRIVATE</a> flag (choosing not to use persistent + shared memory), and then fails, mutexes allocated in + that private memory may leak their underlying system + resources. Therefore, the <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a> flag should be + used with caution on VxWorks. + </p> </li> </ul> </div> @@ -219,16 +293,14 @@ may leak their underlying system resources. Therefore, the <td width="20%" align="center"> <a accesskey="u" href="build_vxworks.html">Up</a> </td> - <td width="40%" align="right"> <a accesskey="n" href="upgrade_53_toc.html">Next</a></td> + <td width="40%" align="right"> <a accesskey="n" href="upgrade_61_toc.html">Next</a></td> </tr> <tr> <td width="40%" align="left" valign="top">VxWorks notes </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </td> + <td width="40%" align="right" valign="top"> Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </td> </tr> </table> </div> diff --git a/docs/installation/build_vxworks_notes.html b/docs/installation/build_vxworks_notes.html index ad75e763..c6a9592c 100644 --- a/docs/installation/build_vxworks_notes.html +++ b/docs/installation/build_vxworks_notes.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="build_vxworks.html">Prev</a> </td> - <th width="60%" align="center">Chapter 8. - Building Berkeley DB for VxWorks - </th> + <th width="60%" align="center">Chapter 8. Building Berkeley DB for VxWorks </th> <td width="20%" align="right"> <a accesskey="n" href="build_vxworks_faq.html">Next</a></td> </tr> </table> @@ -42,72 +40,100 @@ <dl> <dt> <span class="sect2"> - <a href="build_vxworks_notes.html#idp491336">Building and Running the Demo Program</a> + <a href="build_vxworks_notes.html#idp934576">Building and Running the Demo Program</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_vxworks_notes.html#idp518216">Building and Running the Utility Programs</a> + <a href="build_vxworks_notes.html#idp896400">Building and Running the Utility Programs</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_vxworks_notes.html#idp518576">Support for Replication Manager</a> + <a href="build_vxworks_notes.html#idp923512">Support for Replication Manager</a> </span> </dt> </dl> </div> - <p>Berkeley DB currently disallows the <a href="../api_reference/C/dbopen.html#open_DB_TRUNCATE" class="olink">DB_TRUNCATE</a> flag to the -<a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a> method on VxWorks because the operations this flag represents -are not fully supported under VxWorks.</p> - <p>The <a href="../api_reference/C/dbsync.html" class="olink">DB->sync()</a> method is implemented using an ioctl call into the file -system driver with the FIOSYNC command. Most, but not all file system -drivers support this call. Berkeley DB requires the use of a file system -that supports FIOSYNC.</p> + <p> + Berkeley DB currently disallows the <a href="../api_reference/C/dbopen.html#open_DB_TRUNCATE" class="olink">DB_TRUNCATE</a> flag to + the <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a> method on VxWorks because the operations this + flag represents are not fully supported under VxWorks. + </p> + <p> + The <a href="../api_reference/C/dbsync.html" class="olink">DB->sync()</a> method is implemented using an ioctl call into + the file system driver with the FIOSYNC command. Most, but not + all file system drivers support this call. Berkeley DB + requires the use of a file system that supports + FIOSYNC. + </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp491336"></a>Building and Running the Demo Program</h3> + <h3 class="title"><a id="idp934576"></a>Building and Running the Demo Program</h3> </div> </div> </div> - <p>The demo program should be built in a manner very similar to building -Berkeley DB. If you want different or additional BSP build specifications you -should add them by following the directions indicated in -<a class="xref" href="build_vxworks.html#build_vxworks_intro6x" title="Building for VxWorks 6.x">Building for VxWorks 6.x</a>.</p> - <p>The demo program can be downloaded and run by calling the entry function -<span class="bold"><strong>dbdemo</strong></span> with the pathname of a database to use. The demo -program will ask for some input keys. It creates a database and adds -those keys into the database, using the reverse of the key as the data -value. When complete you can either enter EOF (control-D) or -<span class="bold"><strong>quit</strong></span> and the demo program will display all of the key/data -items in the database.</p> + <p> + The demo program should be built in a manner very + similar to building Berkeley DB. If you want different or + additional BSP build specifications you should add them by + following the directions indicated in <a class="xref" href="build_vxworks.html#build_vxworks_intro6x" title="Building for VxWorks 6.x">Building for VxWorks 6.x</a>. + </p> + <p> + The demo program can be downloaded and run by calling + the entry function <span class="bold"><strong>dbdemo</strong></span> + with the pathname of a database to use. The demo program + will ask for some input keys. It creates a database and + adds those keys into the database, using the reverse of + the key as the data value. When complete you can either + enter EOF (control-D) or <span class="bold"><strong>quit</strong></span> + and the demo program will display all + of the key/data items in the database. + </p> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp518216"></a>Building and Running the Utility Programs</h3> + <h3 class="title"><a id="idp896400"></a>Building and Running the Utility Programs</h3> </div> </div> </div> - <p>The Berkeley DB utilities can be downloaded and run by calling the function equivalent to the utility's name. The utility functions take a string containing all the supported arguments. The program will then decompose that string into a traditional argc/argv used internally. For example, to execute <a href="../api_reference/C/db_stat.html" class="olink">db_stat</a> utility on a database within an environment you would execute the following from the windsh prompt. Obviously you would change the pathname and database name to reflect -your system.</p> + <p> + The Berkeley DB utilities can be downloaded and run by + calling the function equivalent to the utility's name. The + utility functions take a string containing all the + supported arguments. The program will then decompose that + string into a traditional argc/argv used internally. For + example, to execute <a href="../api_reference/C/db_stat.html" class="olink">db_stat</a> utility on a database within an + environment you would execute the following from the + windsh prompt. Obviously you would change the pathname and + database name to reflect your system. + </p> <pre class="programlisting">> db_stat "-h /tmp/myenvhome -d mydatabase.db"</pre> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp518576"></a>Support for Replication Manager</h3> + <h3 class="title"><a id="idp923512"></a>Support for Replication Manager</h3> </div> </div> </div> - <p>The Berkeley DB Replication Manager component is available on Vxworks 6.x because it provides support for TCP/IP sockets and POSIX 1003.1 - style networking and threads. You must build Berkley DB for Vxworks using the command line. Prior to building Berkeley DB, ensure you set appropriate values for the variables - specified in Step 1 of <a class="xref" href="build_vxworks.html#build_vxworks_intro6x" title="Building for VxWorks 6.x">Building for VxWorks 6.x</a>. To use Berkeley DB Replication Manager, <code class="literal">netLib</code> and <code class="literal">ioLib</code> must be present in the Vxworks image. - </p> + <p> + The Berkeley DB Replication Manager component is + available on Vxworks 6.x because it provides support for + TCP/IP sockets and POSIX 1003.1 style networking and + threads. You must build Berkley DB for Vxworks using the + command line. Prior to building Berkeley DB, ensure you + set appropriate values for the variables specified in Step + 1 of <a class="xref" href="build_vxworks.html#build_vxworks_intro6x" title="Building for VxWorks 6.x">Building for VxWorks 6.x</a>. To use + Berkeley DB Replication Manager, <code class="literal">netLib</code> + and <code class="literal">ioLib</code> must be present in the + Vxworks image. + </p> </div> </div> <div class="navfooter"> @@ -121,9 +147,7 @@ your system.</p> <td width="40%" align="right"> <a accesskey="n" href="build_vxworks_faq.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 8. - Building Berkeley DB for VxWorks - </td> + <td width="40%" align="left" valign="top">Chapter 8. Building Berkeley DB for VxWorks </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/build_win.html b/docs/installation/build_win.html index b03fd1d8..ac6a2267 100644 --- a/docs/installation/build_win.html +++ b/docs/installation/build_win.html @@ -8,22 +8,20 @@ <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> <link rel="up" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="prev" href="build_android_config.html" title="Android Configuration Options" /> + <link rel="prev" href="build_android_adfmobile.html" title="Using the JDBC Driver in ADF Mobile for Android" /> <link rel="next" href="win_build64.html" title="Building Berkeley DB for 64-bit Windows" /> </head> <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 5. - Building Berkeley DB for Windows - </th> + <th colspan="3" align="center">Chapter 5. Building Berkeley DB for Windows </th> </tr> <tr> - <td width="20%" align="left"><a accesskey="p" href="build_android_config.html">Prev</a> </td> + <td width="20%" align="left"><a accesskey="p" href="build_android_adfmobile.html">Prev</a> </td> <th width="60%" align="center"> </th> <td width="20%" align="right"> <a accesskey="n" href="win_build64.html">Next</a></td> </tr> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="build_win"></a>Chapter 5. - Building Berkeley DB for Windows - </h2> + <h2 class="title"><a id="build_win"></a>Chapter 5. Building Berkeley DB for Windows </h2> </div> </div> </div> @@ -54,22 +50,27 @@ <dl> <dt> <span class="sect2"> - <a href="build_win.html#idm1531520">Visual C++ .NET 2010</a> + <a href="build_win.html#idp283736">Visual C++ .NET 2012</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win.html#idm232112">Visual C++ .NET 2008</a> + <a href="build_win.html#idp270168">Visual C++ .NET 2010</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win.html#idm67456">Visual C++ .NET 2005</a> + <a href="build_win.html#idp285656">Visual C++ .NET 2008</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win.html#idm1085168">Build results</a> + <a href="build_win.html#idp292968">Visual C++ .NET 2005</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_win.html#idp295544">Build results</a> </span> </dt> </dl> @@ -83,7 +84,7 @@ <dl> <dt> <span class="sect2"> - <a href="win_build64.html#idm80112">x64 build with Visual Studio 2005 or newer</a> + <a href="win_build64.html#idp269712">x64 build with Visual Studio 2005 or newer</a> </span> </dt> </dl> @@ -122,18 +123,22 @@ <dl> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1386992">Binary Compatibility With SQLite</a> + <a href="build_win_sql.html#idp339096">Binary Compatibility With SQLite</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_win_sql.html#idp335872">Setting Encryption</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1146112">Setting Preprocessor Flags - </a> + <a href="build_win_sql.html#idp265480">Changing Compile Options</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1193168">Enabling Extensions</a> + <a href="build_win_sql.html#idp224800">Enabling Extensions</a> </span> </dt> <dt> @@ -148,18 +153,22 @@ </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm313872">Using the JDBC Driver</a> + <a href="build_win_sql.html#idp339720">Using the JDBC Driver</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1594400">Building the ODBC Driver</a> + <a href="build_win_sql.html#idp367344">Using the JDBC Driver in ADF/JDeveloper</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm313808"> Using the ADO.NET Driver - </a> + <a href="build_win_sql.html#idp375344">Building the ODBC Driver</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_win_sql.html#idp416760"> Using the ADO.NET Driver </a> </span> </dt> </dl> @@ -181,29 +190,33 @@ </dt> <dt> <span class="sect1"> - <a href="build_win_small.html">Building a small memory footprint library</a> + <a href="build_win_small.html">Building a small memory + footprint library</a> </span> </dt> <dt> <span class="sect1"> - <a href="build_win_test.html">Running the test suite under Windows</a> + <a href="build_win_test.html">Running the test suite under + Windows</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> - <a href="build_win_test.html#idp126120">Building the software needed by the tests</a> + <a href="build_win_test.html#idp458352">Building the software needed + by the tests</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_test.html#idp137576">Running the test suite under Windows</a> + <a href="build_win_test.html#idp389880">Running the test suite under Windows</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_test.html#build_win_test_sql">Building the software needed by the SQL tests</a> + <a href="build_win_test.html#build_win_test_sql">Building the software + needed by the SQL tests</a> </span> </dt> </dl> @@ -221,14 +234,16 @@ </dl> </div> <p> - This chapter contains general instructions on building Berkeley DB for specific windows platforms - using specific compilers. The <a class="xref" href="build_win_faq.html" title="Windows FAQ">Windows FAQ</a> - also contains helpful information. -</p> - <p> - The <code class="filename">build_windows</code> directory in the Berkeley DB distribution contains - project files for Microsoft Visual Studio: -</p> + This chapter contains general instructions on building + Berkeley DB for specific windows platforms using specific + compilers. The <a class="xref" href="build_win_faq.html" title="Windows FAQ">Windows FAQ</a> also contains helpful + information. + </p> + <p> + The <code class="filename">build_windows</code> directory in the + Berkeley DB distribution contains project files for Microsoft + Visual Studio: + </p> <div class="informaltable"> <table border="1" width="80%"> <colgroup> @@ -237,34 +252,40 @@ </colgroup> <thead> <tr> - <th>Project File</th> + <th>Project + File</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td align="center">Berkeley_DB.sln</td> - <td align="center">Visual Studio 2005 (8.0) workspace</td> + <td align="center">Visual Studio 2005 (8.0) + workspace</td> </tr> <tr> <td align="center">*.vcproj</td> - <td align="center">Visual Studio 2005 (8.0) projects</td> + <td align="center">Visual Studio 2005 (8.0) + projects</td> </tr> <tr> <td align="center">Berkeley_DB_vs2010.sln</td> - <td align="center">Visual Studio 2010 workspace</td> + <td align="center">Visual Studio 2010 + workspace</td> </tr> <tr> <td align="center">*.vcxproj</td> - <td align="center">Visual Studio 2010 projects</td> + <td align="center">Visual Studio 2010 + projects</td> </tr> </tbody> </table> </div> <p> - These project files can be used to build Berkeley DB for the following platforms: Windows - NT/2K/XP/2003/Vista and Windows7; and 64-bit Windows XP/2003/Vista and Windows7. -</p> + These project files can be used to build Berkeley DB for + Windows Server 2008, Windows Vista, Windows 7, Windows Server + 2008 R2, and Windows 8. + </p> <div class="sect1" lang="en" xml:lang="en"> <div class="titlepage"> <div> @@ -277,22 +298,27 @@ <dl> <dt> <span class="sect2"> - <a href="build_win.html#idm1531520">Visual C++ .NET 2010</a> + <a href="build_win.html#idp283736">Visual C++ .NET 2012</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win.html#idm232112">Visual C++ .NET 2008</a> + <a href="build_win.html#idp270168">Visual C++ .NET 2010</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win.html#idm67456">Visual C++ .NET 2005</a> + <a href="build_win.html#idp285656">Visual C++ .NET 2008</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win.html#idm1085168">Build results</a> + <a href="build_win.html#idp292968">Visual C++ .NET 2005</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_win.html#idp295544">Build results</a> </span> </dt> </dl> @@ -301,20 +327,40 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1531520"></a>Visual C++ .NET 2010</h3> + <h3 class="title"><a id="idp283736"></a>Visual C++ .NET 2012</h3> </div> </div> </div> <div class="orderedlist"> <ol type="1"> - <li>Choose <span class="emphasis"><em>File -> Open -> Project/Solution...</em></span>. -In the <code class="filename">build_windows</code> directory, select -<code class="filename">Berkeley_DB_vs2010.sln</code> and click Open.</li> - <li>Choose the desired project configuration from the drop-down menu on -the tool bar (either Debug or Release).</li> - <li>Choose the desired platform configuration from the drop-down menu on -the tool bar (usually Win32 or x64).</li> - <li>To build, right-click on the <code class="filename">Berkeley_DB_vs2010</code> solution and select Build Solution.</li> + <li> + Choose <span class="emphasis"><em>File -> Open -> + Project/Solution...</em></span>. In the + <code class="filename">build_windows</code> directory, + select <code class="filename">Berkeley_DB_vs2010.sln</code> + and click Open. + </li> + <li> + The <span class="emphasis"><em>Update VC++ Compiler and Libraries + </em></span> dialog box will open automatically. + Click <span class="emphasis"><em>Update</em></span> and wait for the + projects to be converted. + </li> + <li> + Choose the desired project configuration + from the drop-down menu on the tool bar (either + Debug or Release). + </li> + <li> + Choose the desired platform configuration + from the drop-down menu on the tool bar (usually + Win32 or x64). + </li> + <li> + To build, right-click on the + <code class="filename">Berkeley_DB_vs2010</code> + solution and select Build Solution. + </li> </ol> </div> </div> @@ -322,24 +368,34 @@ the tool bar (usually Win32 or x64).</li> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm232112"></a>Visual C++ .NET 2008</h3> + <h3 class="title"><a id="idp270168"></a>Visual C++ .NET 2010</h3> </div> </div> </div> <div class="orderedlist"> <ol type="1"> - <li>Choose <span class="emphasis"><em>File -> Open -> Project/Solution...</em></span>. -In the <code class="filename">build_windows</code> directory, select -<code class="filename">Berkeley_DB.sln</code> and click Open.</li> - <li>The <span class="emphasis"><em>Visual Studio Conversion Wizard</em></span> will open -automatically. Click the <span class="emphasis"><em>Finish</em></span> button.</li> - <li>On the next screen click the <span class="emphasis"><em>Close</em></span> button.</li> - <li>Choose the desired project configuration from the drop-down menu on -the tool bar (either Debug or Release).</li> - <li>Choose the desired platform configuration from the drop-down menu on -the tool bar (usually Win32 or x64).</li> - <li>To build, right-click on the Berkeley_DB solution and select Build -Solution.</li> + <li> + Choose <span class="emphasis"><em>File -> Open -> + Project/Solution...</em></span>. In the + <code class="filename">build_windows</code> directory, + select <code class="filename">Berkeley_DB_vs2010.sln</code> + and click Open. + </li> + <li> + Choose the desired project configuration + from the drop-down menu on the tool bar (either + Debug or Release). + </li> + <li> + Choose the desired platform configuration + from the drop-down menu on the tool bar (usually + Win32 or x64). + </li> + <li> + To build, right-click on the + <code class="filename">Berkeley_DB_vs2010</code> + solution and select Build Solution. + </li> </ol> </div> </div> @@ -347,20 +403,43 @@ Solution.</li> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm67456"></a>Visual C++ .NET 2005</h3> + <h3 class="title"><a id="idp285656"></a>Visual C++ .NET 2008</h3> </div> </div> </div> <div class="orderedlist"> <ol type="1"> - <li>Choose <span class="emphasis"><em>File -> Open -> Project/Solution...</em></span>. -In the <code class="filename">build_windows</code> directory, select -<code class="filename">Berkeley_DB.sln</code> and click Open</li> - <li>Choose the desired project configuration from the drop-down menu on -the tool bar (either Debug or Release).</li> - <li>Choose the desired platform configuration from the drop-down menu on -the tool bar (usually Win32 or x64).</li> - <li>To build, right-click on the Berkeley_DB solution and select Build Solution.</li> + <li> + Choose <span class="emphasis"><em>File -> Open -> + Project/Solution...</em></span>. In the + <code class="filename">build_windows</code> directory, + select <code class="filename">Berkeley_DB.sln</code> and + click Open. + </li> + <li> + The <span class="emphasis"><em>Visual Studio Conversion + Wizard</em></span> will open automatically. + Click the <span class="emphasis"><em>Finish</em></span> + button. + </li> + <li> + On the next screen click the + <span class="emphasis"><em>Close</em></span> button. + </li> + <li> + Choose the desired project configuration + from the drop-down menu on the tool bar (either + Debug or Release). + </li> + <li> + Choose the desired platform configuration + from the drop-down menu on the tool bar (usually + Win32 or x64). + </li> + <li> + To build, right-click on the Berkeley_DB + solution and select Build Solution. + </li> </ol> </div> </div> @@ -368,14 +447,48 @@ the tool bar (usually Win32 or x64).</li> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1085168"></a>Build results</h3> + <h3 class="title"><a id="idp292968"></a>Visual C++ .NET 2005</h3> </div> </div> </div> - <p> - The results of your build will be placed in one of the following - Berkeley DB subdirectories, depending on the configuration that you chose: - </p> + <div class="orderedlist"> + <ol type="1"> + <li> + Choose <span class="emphasis"><em>File -> Open -> + Project/Solution...</em></span>. In the + <code class="filename">build_windows</code> directory, + select <code class="filename">Berkeley_DB.sln</code> and + click Open + </li> + <li> + Choose the desired project configuration + from the drop-down menu on the tool bar (either + Debug or Release). + </li> + <li> + Choose the desired platform configuration + from the drop-down menu on the tool bar (usually + Win32 or x64). + </li> + <li> + To build, right-click on the Berkeley_DB + solution and select Build Solution. + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp295544"></a>Build results</h3> + </div> + </div> + </div> + <p> + The results of your build will be placed in one of + the following Berkeley DB subdirectories, depending on + the configuration that you chose: </p> <table class="simplelist" border="0" summary="Simple list"> <tr> <td> @@ -399,18 +512,37 @@ the tool bar (usually Win32 or x64).</li> </tr> </table> <p> - When building your application during development, you should normally - use compile options "Debug Multithreaded DLL" and link against - <code class="filename">build_windows\Debug\libdb53d.lib</code>. You can also - build using a release version of the Berkeley DB libraries and tools, - which will be placed in - <code class="filename">build_windows\Win32\Release\libdb53.lib</code>. When - linking against the release build, you should compile your code with - the "Release Multithreaded DLL" compile option. You will also need to - add the <code class="filename">build_windows</code> directory to the list of - include directories of your application's project, or copy the Berkeley - DB include files to another location. - </p> + When building your application during + development, you should normally use compile options + "Debug Multithreaded DLL" and link against + <code class="filename">build_windows\Debug\libdb61d.lib</code>. + </p> + <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> + <h3 class="title">Note</h3> + <p> + Building your application with the debug + configuration will create a Berkeley DB library + and utilities with debugging symbols, as well as + load various routines that can be called from a + debugger to display pages, cursor queues, and so + forth. If installed, the utilities will not be + stripped. This configuration should not be + specified when building production binaries. + </p> + </div> + <p> + You can also build using a release version of the + Berkeley DB libraries and tools, which will be placed + in + <code class="filename">build_windows\Win32\Release\libdb61.lib</code>. + When linking against the release build, you should + compile your code with the "Release Multithreaded DLL" + compile option. You will also need to add the + <code class="filename">build_windows</code> directory to + the list of include directories of your application's + project, or copy the Berkeley DB include files to + another location. + </p> </div> </div> </div> @@ -418,12 +550,12 @@ the tool bar (usually Win32 or x64).</li> <hr /> <table width="100%" summary="Navigation footer"> <tr> - <td width="40%" align="left"><a accesskey="p" href="build_android_config.html">Prev</a> </td> + <td width="40%" align="left"><a accesskey="p" href="build_android_adfmobile.html">Prev</a> </td> <td width="20%" align="center"> </td> <td width="40%" align="right"> <a accesskey="n" href="win_build64.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Android Configuration Options </td> + <td width="40%" align="left" valign="top">Using the JDBC Driver in ADF Mobile for Android </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/build_win_csharp.html b/docs/installation/build_win_csharp.html index 7b7ce999..8e76277c 100644 --- a/docs/installation/build_win_csharp.html +++ b/docs/installation/build_win_csharp.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="build_win_java.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="build_win_sql.html">Next</a></td> </tr> </table> @@ -38,27 +36,28 @@ </div> </div> </div> + <p> + The C# support is built by a separate Visual Studio + solution and requires version 2.0 (or higher) of the .NET + platform. If the Berkeley DB utilities are required, build + Berkeley DB first following the instructions under <a class="xref" href="build_win.html#win_build32" title="Building Berkeley DB for 32 bit Windows">Building Berkeley DB for 32 bit Windows</a> or + <a class="xref" href="win_build64.html" title="Building Berkeley DB for 64-bit Windows">Building Berkeley DB for 64-bit Windows</a>. + </p> <p> - The C# support is built by a separate Visual Studio solution and - requires version 2.0 (or higher) of the .NET platform. If the Berkeley - DB utilities are required, build Berkeley DB first following the - instructions under <a class="xref" href="build_win.html#win_build32" title="Building Berkeley DB for 32 bit Windows">Building Berkeley DB for 32 bit Windows</a> - or <a class="xref" href="win_build64.html" title="Building Berkeley DB for 64-bit Windows">Building Berkeley DB for 64-bit Windows</a>. - </p> + To build the C# API in Visual Studio 2005/Visual Studio + 2008, the solution is + <code class="filename">build_windows\BDB_dotnet.sln</code>; in + Visual Studio 2010/Visual Studio 2012, the solution is + <code class="filename">build_windows\BDB_dotnet_vs2010.sln</code>. + </p> <p> - To build the C# API in Visual Studio - 2005/Visual Studio 2008, the solution is - <code class="filename">build_windows\BDB_dotnet.sln</code>; in Visual Studio - 2010, the solution is - <code class="filename">build_windows\BDB_dotnet_vs2010.sln</code>. - </p> - <p> - By default, the solution will build the native libraries, the - managed assembly and all example programs. The NUnit tests need to - be built explicitly because of their dependence upon the NUnit - assembly. The native libraries will be placed in one of the - following subdirectories, depending upon the chosen configuration: - </p> + By default, the solution will build the native + libraries, the managed assembly and all example programs. + The NUnit tests need to be built explicitly because of + their dependence upon the NUnit assembly. The native + libraries will be placed in one of the following + subdirectories, depending upon the chosen configuration: + </p> <table class="simplelist" border="0" summary="Simple list"> <tr> <td> @@ -82,9 +81,10 @@ </tr> </table> <p> - The managed assembly and all C# example programs will be placed in one of - the following subdirectories, depending upon the chosen configuration: -</p> + The managed assembly and all C# example programs will + be placed in one of the following subdirectories, + depending upon the chosen configuration: + </p> <table class="simplelist" border="0" summary="Simple list"> <tr> <td> @@ -97,13 +97,14 @@ </td> </tr> </table> - <p> - The native libraries need to be locatable by the .NET platform, meaning - they must be copied into an application's directory, the Windows or - System directory, or their location must be added to the PATH - environment variable. The example programs demonstrate how to - programmatically edit the PATH variable. -</p> + <p> + The native libraries need to be locatable by the .NET + platform, meaning they must be copied into an + application's directory, the Windows or System directory, + or their location must be added to the PATH environment + variable. The example programs demonstrate how to + programmatically edit the PATH variable. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/build_win_faq.html b/docs/installation/build_win_faq.html index 14a5f228..398ff3e2 100644 --- a/docs/installation/build_win_faq.html +++ b/docs/installation/build_win_faq.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="build_win_notes.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="build_wince.html">Next</a></td> </tr> </table> @@ -42,97 +40,135 @@ <ol type="1"> <li> <span class="bold"> - <strong>My Win* C/C++ application crashes in the Berkeley DB library when Berkeley DB calls -fprintf (or some other standard C library function).</strong> + <strong>My Win* C/C++ application crashes in + the Berkeley DB library when Berkeley DB calls fprintf + (or some other standard C library + function).</strong> </span> - <p>You should be using the "Debug Multithreaded DLL" compiler option in -your application when you link with the -build_windows\Debug\libdb48d.lib library (this .lib file -is actually a stub for libdb48d.DLL). To check this -setting in Visual C++, choose the <span class="emphasis"><em>Project/Settings</em></span> menu -item and select <span class="emphasis"><em>Code Generation</em></span> under the tab marked -<span class="emphasis"><em>C/C++</em></span>; and see the box marked <span class="emphasis"><em>Use runtime -library</em></span>. This should be set to <span class="emphasis"><em>Debug Multithreaded DLL</em></span>. -If your application is linked against the static library, -build_windows\Debug\libdb48sd.lib; then, you will want -to set <span class="emphasis"><em>Use runtime library</em></span> to <span class="emphasis"><em>Debug Multithreaded</em></span>.</p> - <p>Setting this option incorrectly can cause multiple versions of the -standard libraries to be linked into your application (one on behalf -of your application, and one on behalf of the Berkeley DB library). That -violates assumptions made by these libraries, and traps can result.</p> <p> -Also, using different Visual Studio compilers in the application and -libraries can lead to a crash. So rebuild the application -with the same Visual C++ version as that of the library. -</p> + You should be using the "Debug Multithreaded DLL" + compiler option in your application when you link with + the build_windows\Debug\libdb60d.lib library (this + .lib file is actually a stub for libdb60d.DLL). To + check this setting in Visual C++, choose the + <span class="emphasis"><em>Project/Settings</em></span> menu item + and select <span class="emphasis"><em>Code Generation</em></span> under + the tab marked <span class="emphasis"><em>C/C++</em></span>; and see the + box marked <span class="emphasis"><em>Use runtime library</em></span>. + This should be set to <span class="emphasis"><em>Debug Multithreaded + DLL</em></span>. If your application is linked + against the static library, + build_windows\Debug\libdb60sd.lib; then, you will want + to set <span class="emphasis"><em>Use runtime library</em></span> to + <span class="emphasis"><em>Debug Multithreaded</em></span>. + </p> + <p> + Setting this option incorrectly can cause multiple + versions of the standard libraries to be linked into + your application (one on behalf of your application, + and onle on behalf of the Berkeley DB library). That + violates assumptions made by these libraries, and + traps can result. + </p> + <p> + Also, using different Visual Studio compilers in + the application and libraries can lead to a crash. So + rebuild the application with the same Visual C++ + version as that of the library. + </p> </li> <li> <span class="bold"> - <strong>Why are the build options for DB_DLL marked as "Use MFC in a Shared DLL"? -Does Berkeley DB use MFC?</strong> + <strong>Why are the build options for DB_DLL + marked as "Use MFC in a Shared DLL"? Does Berkeley DB + use MFC?</strong> </span> - <p>Berkeley DB does not use MFC at all. It does however, call malloc and free -and other facilities provided by the Microsoft C runtime library. We -found in our work that many applications and libraries are built -assuming MFC, and specifying this for Berkeley DB solves various -interoperation issues, and guarantees that the right runtime libraries -are selected. Note that because we do not use MFC facilities, the MFC -library DLL is not marked as a dependency for libdb.dll, but the -appropriate Microsoft C runtime is.</p> + <p> + Berkeley DB does not use MFC at all. It does + however, call malloc and free and other facilities + provided by the Microsoft C runtime library. We found + in our work that many applications and libraries are + built assuming MFC, and specifying this for Berkeley + DB solves various interoperation issues, and + guarantees that the right runtime libraries are + selected. Note that because we do not use MFC + facilities, the MFC library DLL is not marked as a + dependency for libdb.dll, but the appropriate + Microsoft C runtime is. + </p> </li> <li> <span class="bold"> - <strong>How can I build Berkeley DB for <a class="ulink" href="http://www.mingw.org" target="_top">MinGW</a>?</strong> + <strong>How can I build Berkeley DB for + <a class="ulink" href="http://www.mingw.org" target="_top">MinGW</a>?</strong> </span> - <p>Follow the instructions in <a class="xref" href="build_unix.html#build_unix_intro" title="Building for UNIX/POSIX">Building for UNIX/POSIX</a>, and specify the --enable-mingw option to the -configuration script. This configuration option currently only builds -static versions of the library, it does not yet build a DLL version of -the library, and file sizes are limited to 2GB (2^32 bytes.)</p> + <p> + Follow the instructions in <a class="xref" href="build_unix.html#build_unix_intro" title="Building for UNIX/POSIX">Building for UNIX/POSIX</a>, and specify + the --enable-mingw option to the configuration script. + This configuration option currently only builds static + versions of the library, it does not yet build a DLL + version of the library, and file sizes are limited to + 2GB (2^32 bytes.) + </p> </li> <li> <span class="bold"> - <strong>How can I build a Berkeley DB for Windows 98/ME?</strong> + <strong>How can I build a Berkeley DB for + Windows 98/ME?</strong> </span> <p> - Windows 98/ME is no longer supported by Berkeley DB. The following is - therefore only of interest to historical users of Berkeley DB. - </p> - <p> - By default on Windows, Berkeley DB supports internationalized - filenames by treating all directory paths and filenames passed to - Berkeley DB methods as UTF-8 encoded strings. All paths are - internally converted to wide character strings and passed to the - wide character variants of Windows system calls. - </p> - <p> - This allows applications to create and open databases with names - that cannot be represented with ASCII names while maintaining - compatibility with applications that work purely with ASCII paths. - </p> - <p> - Windows 98 and ME do not support Unicode paths directly. To build for - those versions of Windows, either: - </p> + Windows 98/ME is no longer supported by Berkeley + DB. The following is therefore only of interest to + historical users of Berkeley DB. + </p> + <p> + By default on Windows, Berkeley DB supports + internationalized filenames by treating all directory + paths and filenames passed to Berkeley DB methods as + UTF-8 encoded strings. All paths are internally + converted to wide character strings and passed to the + wide character variants of Windows system calls. + </p> + <p> + This allows applications to create and open + databases with names that cannot be represented with + ASCII names while maintaining compatibility with + applications that work purely with ASCII paths. + </p> + <p> + Windows 98 and ME do not support Unicode paths + directly. To build for those versions of Windows, + either: + </p> <div class="itemizedlist"> <ul type="disc"> <li> - <p> - Follow the instructions at - <a class="ulink" href="http://msdn.microsoft.com/en-us/goglobal/bb688166.aspx" target="_top">Microsoft's web site</a>. - </p> + <p> + Follow the instructions at <a class="ulink" href="http://msdn.microsoft.com/en-us/goglobal/bb688166.aspx" target="_top"> + Microsoft's web site</a>. + </p> </li> <li> - <p>Open the workspace or solution file with Visual Studio. Then -open the Project properties/settings section for the project you need to build -(at least db_dll). In the <span class="emphasis"><em>C/C++->Preprocessor->Preprocessor -Definitions</em></span> section, remove <span class="emphasis"><em>_UNICODE</em></span> and -<span class="emphasis"><em>UNICODE</em></span> entries. Add in an entry of -<span class="emphasis"><em>_MBCS</em></span>. Build the project as normal.</p> + <p> + Open the workspace or solution file with + Visual Studio. Then open the Project + properties/settings section for the project + you need to build (at least db_dll). In the + <span class="emphasis"><em>C/C++->Preprocessor->Preprocessor + Definitions</em></span> section, remove + <span class="emphasis"><em>_UNICODE</em></span> and + <span class="emphasis"><em>UNICODE</em></span> entries. Add + in an entry of <span class="emphasis"><em>_MBCS</em></span>. + Build the project as normal. + </p> </li> </ul> </div> - <p>The ASCII builds will also work on Windows NT/2K/XP/2003 and Windows7, but will -not translate paths to wide character strings.</p> + <p> + The ASCII builds will also work on newer versions of + Windows, but will not translate paths to wide character + strings. + </p> </li> </ol> </div> @@ -152,9 +188,7 @@ not translate paths to wide character strings.</p> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 6. - Building Berkeley DB for Windows Mobile - </td> + <td width="40%" align="right" valign="top"> Chapter 6. Building Berkeley DB for Windows Mobile </td> </tr> </table> </div> diff --git a/docs/installation/build_win_java.html b/docs/installation/build_win_java.html index ef2c20c4..8acbc5be 100644 --- a/docs/installation/build_win_java.html +++ b/docs/installation/build_win_java.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="win_build_stl.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="build_win_csharp.html">Next</a></td> </tr> </table> @@ -38,47 +36,94 @@ </div> </div> </div> - <p>Java support is not built automatically. The following instructions -assume that you have installed the Sun Java Development Kit in -<code class="filename">d:\java</code>. Of course, if you installed elsewhere or have -different Java software, you will need to adjust the pathnames -accordingly.</p> + <p> + Java support is not built automatically. The following + instructions assume that you have installed the Sun Java + Development Kit in <code class="filename">d:\java</code>. Of + course, if you installed elsewhere or have different Java + software, you will need to adjust the pathnames + accordingly. + </p> <div class="orderedlist"> <ol type="1"> - <li>Set your include directories. -<div class="itemizedlist"><ul type="disc"><li> -In Visual Studio 2005/Visual Studio 2008 - Choose <span class="emphasis"><em>Tools -> Options --> Projects -> VC++ Directories</em></span>. Under the "Show -directories for" pull-down, select "Include files". Add the full -pathnames for the <code class="filename">d:\java\include</code> and -<code class="filename">d:\java\include\win32</code> directories. Then click OK. -</li><li> -In Visual Studio 2010 - Right-click db_java project, choose <span class="emphasis"><em>Properties->Configuration Properties-> VC++ Directories->Include Directories</em></span>. -Add the full pathnames for the <code class="filename">d:\java\include</code> and <code class="filename">d:\java\include\win32</code> directories. Then click OK. -</li></ul></div> -These are -the directories needed when including jni.h.</li> - <li>Set the executable files directories. -<div class="itemizedlist"><ul type="disc"><li> -In Visual Studio 2005/Visual Studio 2008 - Choose <span class="emphasis"><em>Tools -> -Options -> Projects -> VC++ Directories</em></span>. Under the "Show -directories for" pull-down, select "Executable files". Add the full -pathname for the <code class="filename">d:\java\bin</code> directory, then click OK. -</li><li> -In Visual Studio 2010 - Right-click db_java project, choose <span class="emphasis"><em>Properties->Configuration Properties-> VC++ Directories->Executable Directories</em></span>. Add the full pathnames for the <code class="filename">d:\java\bin</code> directories. Then click OK. -</li></ul></div> - -This is the directory needed to find javac.</li> - <li>Set the build type to Release or Debug in the drop-down on the -tool bar.</li> <li> - <p> - To build, right-click on db_java and select Build. This builds the - Java support library for Berkeley DB and compiles all the java files, - placing the resulting <code class="filename">db.jar</code> and - <code class="filename">dbexamples.jar</code> files in one of the following - Berkeley DB subdirectories, depending on the configuration that you chose: -</p> + Set your include directories. + <div class="itemizedlist"><ul type="disc"><li> + In Visual Studio 2005/Visual Studio + 2008 - Choose <span class="emphasis"><em>Tools -> Options + -> Projects -> VC++ + Directories</em></span>. Under the "Show + directories for" pull-down, select "Include + files". Add the full pathnames for the + <code class="filename">d:\java\include</code> and + <code class="filename">d:\java\include\win32</code> + directories. Then click OK. + </li><li> + In Visual Studio 2010/Visual Studio 2012 + - Right-click db_java project, choose + <span class="emphasis"><em>Properties->Configuration + Properties-> VC++ + Directories->Include + Directories</em></span>. Add the full + pathnames for the + <code class="filename">d:\java\include</code> and + <code class="filename">d:\java\include\win32</code> + directories. Then click OK. + </li></ul></div><p> + These are the directories needed when + including jni.h. + </p></li> + <li> + Set the executable files directories. + <div class="itemizedlist"><ul type="disc"><li> + In Visual Studio 2005/Visual Studio + 2008 - Choose <span class="emphasis"><em>Tools -> Options + -> Projects -> VC++ + Directories</em></span>. Under the "Show + directories for" pull-down, select "Executable + files". Add the full pathname for the + <code class="filename">d:\java\bin</code> + directory, then click OK. + </li><li> + In Visual Studio 2010/Visual Studio 2012 + - Right-click db_java project, choose + <span class="emphasis"><em>Properties->Configuration + Properties-> VC++ + Directories->Executable + Directories</em></span>. Add the full + pathnames for the + <code class="filename">d:\java\bin</code> + directories. Then click OK. + </li></ul></div> + This is the directory needed to find + javac. + </li> + <li> + Set the build type to Release or Debug in the + drop-down on the tool bar. + </li> + <li> + Change the compiling option if you are using + Java 1.7 + <div class="itemizedlist"><ul type="disc"><li> + In Visual Studio 2005/Visual Studio + 2008/Visual Studio 2010/Visual Studio 2012 + - Right-click db_java project, choose + <span class="emphasis"><em>Properties->Configuration + Properties-> Custom Build + Step</em></span>, Remove the option of + "-target 1.5" in the "Command Line". + </li></ul></div></li> + <li> + <p> + To build, right-click on db_java and select + Build. This builds the Java support library for + Berkeley DB and compiles all the java files, + placing the resulting <code class="filename">db.jar</code> + and <code class="filename">dbexamples.jar</code> files in + one of the following Berkeley DB subdirectories, + depending on the configuration that you chose: + </p> <table class="simplelist" border="0" summary="Simple list"> <tr> <td> diff --git a/docs/installation/build_win_notes.html b/docs/installation/build_win_notes.html index ccc4efde..9aa16fca 100644 --- a/docs/installation/build_win_notes.html +++ b/docs/installation/build_win_notes.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="build_win_test.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="build_win_faq.html">Next</a></td> </tr> </table> @@ -39,44 +37,71 @@ </div> </div> <div class="orderedlist"> - <p>If a system memory environment is closed by all processes, subsequent -attempts to open it will return an error. To successfully open a -transactional environment in this state, recovery must be run by the -next process to open the environment. For non-transactional -environments, applications should remove the existing environment and -then create a new database environment.</p> + <p> + If a system memory environment is closed by all + processes, subsequent attempts to open it will return an + error. To successfully open a transactional environment in + this state, recovery must be run by the next process to + open the environment. For non-transactional environments, + applications should remove the existing environment and + then create a new database environment. + </p> <ol type="1"> - <li>Berkeley DB does not support the Windows/95, Windows/98 or - Windows/ME platforms.</li> - <li>On Windows, system paging file memory is freed on last close. For this -reason, multiple processes sharing a database environment created using -the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> flag must arrange for at least one process to -always have the environment open, or alternatively that any process -joining the environment be prepared to re-create it.</li> - <li>When using the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> flag, Berkeley DB shared regions are -created without ACLs, which means that the regions are only accessible -to a single user. If wider sharing is appropriate (for example, both -user applications and Windows/NT service applications need to access -the Berkeley DB regions), the Berkeley DB code will need to be modified to create -the shared regions with the correct ACLs. Alternatively, by not -specifying the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> flag, filesystem-backed regions -will be created instead, and the permissions on those files may be -directly specified through the <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a> method.</li> - <li>Applications that operate on wide character strings can use the -Windows function WideCharToMultiByte with the code page CP_UTF8 to -convert paths to the form expected by Berkeley DB. Internally, Berkeley DB calls -MultiByteToWideChar on paths before calling Windows functions.</li> - <li>Various Berkeley DB methods take a <span class="bold"><strong>mode</strong></span> argument, which is intended -to specify the underlying file permissions for created files. Berkeley DB -currently ignores this argument on Windows systems. -<p>It would be possible to construct a set of security attributes to pass to -<span class="bold"><strong>CreateFile</strong></span> that accurately represents the mode. In the worst -case, this would involve looking up user and all group names, and creating -an entry for each. Alternatively, we could call the <span class="bold"><strong>_chmod</strong></span> -(partial emulation) function after file creation, although this leaves us -with an obvious race.</p><p>Practically speaking, however, these efforts would be largely meaningless -on a FAT file system, which only has a "readable" and "writable" flag, -applying to all users.</p></li> + <li> + Berkeley DB does not support the Windows XP, + Windows 2003 or earlier Windows platforms. + </li> + <li> + On Windows, system paging file memory is freed on + last close. For this reason, multiple processes sharing a + database environment created using the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> + flag must arrange for at least one process to always have + the environment open, or alternatively that any process + joining the environment be prepared to re-create it. + </li> + <li> + When using the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> flag, Berkeley DB + shared regions are created without ACLs, which means that + the regions are only accessible to a single user. If wider + sharing is appropriate (for example, both user + applications and Windows/NT service applications need to + access the Berkeley DB regions), the Berkeley DB code will + need to be modified to create the shared regions with the + correct ACLs. Alternatively, by not specifying the + <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> flag, filesystem-backed regions will be + created instead, and the permissions on those files may be + directly specified through the <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a> method. + </li> + <li> + Applications that operate on wide character strings + can use the Windows function WideCharToMultiByte with the + code page CP_UTF8 to convert paths to the form expected by + Berkeley DB. Internally, Berkeley DB calls + MultiByteToWideChar on paths before calling Windows + functions. + </li> + <li> + Various Berkeley DB methods take a <span class="bold"><strong>mode</strong></span> argument, which is + intended to specify the underlying file permissions for + created files. Berkeley DB currently ignores this argument + on Windows systems. + <p> + It would be possible to + construct a set of security attributes to pass to + <span class="bold"><strong>CreateFile</strong></span> that + accurately represents the mode. In the worst case, + this would involve looking up user and all group + names, and creating an entry for each. Alternatively, + we could call the <span class="bold"><strong>_chmod</strong></span> + (partial emulation) function + after file creation, although this leaves us with an + obvious race. + </p><p> + Practically speaking, however, these efforts would + be largely meaningless on a FAT file system, which + only has a "readable" and "writable" flag, applying to + all users. + </p></li> </ol> </div> </div> @@ -91,7 +116,8 @@ applying to all users.</p></li> <td width="40%" align="right"> <a accesskey="n" href="build_win_faq.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Running the test suite under Windows </td> + <td width="40%" align="left" valign="top">Running the test suite under + Windows </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/build_win_small.html b/docs/installation/build_win_small.html index aeaba0ce..6b79ae85 100644 --- a/docs/installation/build_win_small.html +++ b/docs/installation/build_win_small.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">Building a small memory footprint library</th> + <th colspan="3" align="center">Building a small memory + footprint library</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="win_additional_options.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="build_win_test.html">Next</a></td> </tr> </table> @@ -34,50 +33,54 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_win_small"></a>Building a small memory footprint library</h2> + <h2 class="title" style="clear: both"><a id="build_win_small"></a>Building a small memory + footprint library</h2> </div> </div> </div> <p> - For applications that don't require all of the functionality of the - full Berkeley DB library, an option is provided to build a static - library with certain functionality disabled. In particular, - cryptography, hash and queue access methods, replication and - verification are all turned off. In addition, all message text - is stripped from the library. This can reduce the memory - footprint of Berkeley DB significantly. + For applications that don't require all of the + functionality of the full Berkeley DB library, an option is + provided to build a static library with certain functionality + disabled. In particular, cryptography, hash, heap and queue + access methods, replication and verification are all turned + off. In addition, all message text is stripped from the + library. This can reduce the memory footprint of Berkeley DB + significantly. </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p> - If your library has stripped messages, you can get an idea of - what text should be issued for a given error message by using - the <a href="../articles/mssgtxt/index.html" class="olink">Message - Reference for Stripped Libraries</a> guide. + If your library has stripped messages, you can get an + idea of what text should be issued for a given error + message by using the <a href="../articles/mssgtxt/index.html" class="olink">Berkeley DB Message Reference Guide + </a>. </p> </div> - <p> - In general on Windows systems, you will want to evaluate the size - of the final application, not the library build. The Microsoft LIB - file format (like UNIX archives) includes copies of all of the - object files and additional information. The linker rearranges - symbols and strips out the overhead, and the resulting application - is much smaller than the library. There is also a Visual C++ - optimization to "Minimize size" that will reduce the library size - by a few percent. + <p> + In general on Windows systems, you will want to evaluate + the size of the final application, not the library build. The + Microsoft LIB file format (like UNIX archives) includes copies + of all of the object files and additional information. The + linker rearranges symbols and strips out the overhead, and the + resulting application is much smaller than the library. There + is also a Visual C++ optimization to "Minimize size" that will + reduce the library size by a few percent. + </p> + <p> + A Visual C++ project file called + <code class="filename">db_small</code> is provided for this small + memory configuration. During a build, static libraries are + created in <code class="filename">Release</code> or + <code class="filename">Debug</code>, respectively. The library name + is <code class="filename">libdb_small60sd.lib</code> for the debug + build, or <code class="filename">libdb_small60s.lib</code> for the + release build. </p> <p> - A Visual C++ project file called <code class="filename">db_small</code> is - provided for this small memory configuration. During a build, - static libraries are created in <code class="filename">Release</code> or - <code class="filename">Debug</code>, respectively. The library name is - <code class="filename">libdb_small48sd.lib</code> for the debug build, or - <code class="filename">libdb_small48s.lib</code> for the release - build.</p> - <p>For assistance in further reducing the size of - the Berkeley DB library, or in building small memory footprint - libraries on other systems, please contact Berkeley DB - support. + For assistance in further reducing the size of the Berkeley + DB library, or in building small memory footprint libraries on + other systems, please contact Berkeley DB support. </p> </div> <div class="navfooter"> @@ -95,7 +98,8 @@ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Running the test suite under Windows</td> + <td width="40%" align="right" valign="top"> Running the test suite under + Windows</td> </tr> </table> </div> diff --git a/docs/installation/build_win_sql.html b/docs/installation/build_win_sql.html index cb6beb85..af5bf542 100644 --- a/docs/installation/build_win_sql.html +++ b/docs/installation/build_win_sql.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="build_win_csharp.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="build_win_tcl.html">Next</a></td> </tr> </table> @@ -42,18 +40,22 @@ <dl> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1386992">Binary Compatibility With SQLite</a> + <a href="build_win_sql.html#idp339096">Binary Compatibility With SQLite</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1146112">Setting Preprocessor Flags - </a> + <a href="build_win_sql.html#idp335872">Setting Encryption</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1193168">Enabling Extensions</a> + <a href="build_win_sql.html#idp265480">Changing Compile Options</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_win_sql.html#idp224800">Enabling Extensions</a> </span> </dt> <dt> @@ -68,138 +70,282 @@ </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm313872">Using the JDBC Driver</a> + <a href="build_win_sql.html#idp339720">Using the JDBC Driver</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1594400">Building the ODBC Driver</a> + <a href="build_win_sql.html#idp367344">Using the JDBC Driver in ADF/JDeveloper</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm313808"> Using the ADO.NET Driver - </a> + <a href="build_win_sql.html#idp375344">Building the ODBC Driver</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_win_sql.html#idp416760"> Using the ADO.NET Driver </a> </span> </dt> </dl> </div> <p> - SQL support is built as part of the default build on Windows. - For information on the build instructions, see - <a class="xref" href="build_win.html" title="Chapter 5. Building Berkeley DB for Windows"> - Building Berkeley DB for Windows - </a>. - </p> + SQL support is built as part of the default build on + Windows. For information on the build instructions, see + <a class="xref" href="build_win.html" title="Chapter 5. Building Berkeley DB for Windows"> Building Berkeley DB for Windows </a>. + </p> <p> - The SQL library is built as <code class="literal">libdb_sql53.dll</code> - in the Release mode or <code class="literal">libdb_sql53d.dll</code> in - the Debug mode. An SQL command line interpreter called - <code class="literal">dbsql.exe</code> is also built. - </p> + The SQL library is built as + <code class="literal">libdb_sql61.dll</code> in the Release mode + or <code class="literal">libdb_sql61d.dll</code> in the Debug mode. + An SQL command line interpreter called + <code class="literal">dbsql.exe</code> is also built. + </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1386992"></a>Binary Compatibility With SQLite</h3> + <h3 class="title"><a id="idp339096"></a>Binary Compatibility With SQLite</h3> </div> </div> </div> <p> - <code class="literal">libdb_sql53.dll</code> is compatible with - <code class="literal">sqlite3.dll</code>. You can copy - <code class="literal">libdb_sql53.dll</code> to - <code class="literal">sqlite3.dll</code> and - <code class="literal">dbsql.exe</code> to - <code class="literal">sqlite3.exe</code>, and use these applications - as a replacement for the standard SQLite binaries with the same - names. However, if you want to do this, then any legacy data in use by - those tools must be migrated from the standard SQLite database - to a Berkeley DB SQL database <span class="emphasis"><em>before</em></span> you - replace the standard SQLite dll and executable with the - Berkeley DB equivalent. For information on migrating data from - standard SQLite databases to a Berkeley DB SQL database, see - the <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide. - </p> + <code class="literal">libdb_sql61.dll</code> is compatible with + <code class="literal">sqlite3.dll</code>. You can copy + <code class="literal">libdb_sql61.dll</code> to + <code class="literal">sqlite3.dll</code> and + <code class="literal">dbsql.exe</code> to + <code class="literal">sqlite3.exe</code>, and use these + applications as a replacement for the standard SQLite + binaries with the same names. However, if you want to + do this, then any legacy data in use by those tools + must be migrated from the standard SQLite database to + a Berkeley DB SQL database <span class="emphasis"><em>before</em></span> + you replace the standard SQLite dll and executable + with the Berkeley DB equivalent. For information on + migrating data from standard SQLite databases to a + Berkeley DB SQL database, see the + <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide. + </p> <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Warning</h3> <p> - Rename your dlls and executables to the standard SQLite - names with <span class="emphasis"><em>extreme</em></span> care. Doing this - will cause all existing tools to break that currently - have data stored in a standard SQLite database. - </p> + Rename your dlls and executables to the + standard SQLite names with + <span class="emphasis"><em>extreme</em></span> care. Doing this + will cause all existing tools to break that + currently have data stored in a standard SQLite + database. + </p> <p> - <span class="emphasis"><em> - For best results, rename your dlls and command - line tool to use the standard SQLite names only if you - know there are no other tools on your production - platform that rely on standard SQLite. - </em></span> - </p> + <span class="emphasis"><em> For best results, rename your dlls and + command line tool to use the standard SQLite + names only if you know there are no other + tools on your production platform that rely on + standard SQLite. </em></span> + </p> </div> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1146112"></a>Setting Preprocessor Flags - </h3> + <h3 class="title"><a id="idp335872"></a>Setting Encryption</h3> </div> </div> </div> <p> - By default, Berkeley DB SQL generates each table as a subdatabase in - a single file. To generate each table in a separate file, specify - <span class="emphasis"><em>BDBSQL_FILE_PER_TABLE</em></span> in - <span class="emphasis"><em>Preprocessor Definitions </em></span>of the <code class="literal">db_sql</code> project. - </p> + To enable encryption in the Berkeley DB SQL API, + specify <span class="emphasis"><em>SQLITE_HAS_CODEC</em></span> in + <span class="emphasis"><em>Preprocessor Definitions </em></span>of + the <code class="literal">db_sql</code> project. See + <a href="../bdb-sql/sql_encryption.html" class="olink">SQL Encryption</a> in the + <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide for + usage details. + </p> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp265480"></a>Changing Compile Options</h3> + </div> + </div> + </div> <p> - When this option is enabled, the SQL database name is used as a - directory name. This directory contains one file for the metadata - and one file each for every table created by the SQL API. Do not add - or delete files from the database directory. Adding or deleting - files may corrupt the database. To backup just the metadata - (schema), make a copy of the <code class="literal">metadata</code> and - <code class="literal">table00001</code> files from the database directory. - Make a new copy whenever the schema is changed. - - </p> + There are several configuration options you can add + to the <span class="emphasis"><em>Preprocessor Definitions + </em></span>of the <code class="literal">db_sql</code> project. + For example, to enable the option + BDBSQL_FILE_PER_TABLE, add + <code class="literal">BDBSQL_FILE_PER_TABLE=1;</code> to the + <span class="emphasis"><em>Preprocessor Definitions </em></span>of + the <code class="literal">db_sql</code> project. + </p> + <div class="variablelist"> + <dl> + <dt> + <span class="term">BDBSQL_DEFAULT_PAGE_SIZE</span> + </dt> + <dd> + To set the default page size when you + create a database, specify the + BDBSQL_DEFAULT_PAGE_SIZE flag. The assigned + value must be 0, 512, 1024, 2048, 4096, 8192, + 16384, 32768, or 65536. The default value is + 4096. If the value is set to zero, Berkeley DB + queries the file system to determine the best + page size, and the value of + SQLITE_DEFAULT_PAGE_SIZE is used to calculate + the cache size, because the cache size is + specified as a number of pages. + </dd> + <dt> + <span class="term">BDBSQL_FILE_PER_TABLE</span> + </dt> + <dd> + To generate each table in a separate + file, rather than as subdatabases in a single + file, specify the BDBSQL_FILE_PER_TABLE flag. + When this option is enabled, the SQL database + name is used as a directory name. This + directory contains one file for the metadata + and one file each for every table created by + the SQL API. Note that adding or deleting + files from the database directory may corrupt + your database. To backup the metadata + (schema), make a copy of the + <code class="literal">metadata</code> and + <code class="literal">table00001</code> files from + the database directory. Make a new copy + whenever the schema is changed. + </dd> + <dt> + <span class="term">BDBSQL_LOG_REGIONMAX</span> + </dt> + <dd> + To configure the log region size for + the underlying storage engine, specify the + BDBSQL_LOG_REGIONMAX flag. For more + information, see <a href="../api_reference/C/envget_lg_regionmax.html" class="olink">DB_ENV->get_lg_regionmax()</a>. + </dd> + <dt> + <span class="term">BDBSQL_OMIT_LEAKCHECK</span> + </dt> + <dd> + For Berkeley DB to use the default + system allocation routines rather than the + SQLite allocation routines, specify the + BDBSQL_OMIT_LEAKCHECK flag. + </dd> + <dt> + <span class="term">BDBSQL_OMIT_LOG_REMOVE</span> + </dt> + <dd> + Berkeley DB automatically removes log + files that are no longer required That is, + files that are older than the most recent + checkpoint. To disable this functionality, + specify the BDBSQL_OMIT_LOG_REMOVE flag. It is + necessary to provide this flag if you are + using replication with Berkeley DB SQL. + </dd> + <dt> + <span class="term">BDBSQL_OMIT_SHARING</span> + </dt> + <dd> + To create a private environment rather + than a shared environment, specify the + BDBSQL_OMIT_SHARING flag. That is, the cache + and other region files will be created in + memory rather than using file backed shared + memory. For more information, see the + DB_PRIVATE flag of <a href="../api_reference/C/envopen.html" class="olink">DB_ENV->open()</a></dd> + <dt> + <span class="term">BDBSQL_SINGLE_THREAD</span> + </dt> + <dd> + To disable locking and thread safe + connections, specify the BDBSQL_SINGLE_THREAD + flag. If an application is going to use + Berkeley DB from a single thread and a single + process, enabling this flag can deliver + significant performance advantages. + </dd> + <dt> + <span class="term">SQLITE_DEFAULT_CACHE_SIZE</span> + </dt> + <dd> + SQLite provides an in-memory cache + which you size according to the maximum number + of database pages that you want to hold in + memory at any given time. Berkeley DB's + in-memory cache feature performs the same + function as SQLite. To specify the suggested + maximum number of pages of disk cache that + will be allocated per open database file + specify the SQLITE_DEFAULT_CACHE_SIZE flag. + Default value is 2000 pages. For more + information, see the SQLite documentation on + <a class="ulink" href="http://www.sqlite.org/pragma.html#pragma_default_cache_size" target="_top"> + PRAGMA default_cache_size</a>. + </dd> + <dt> + <span class="term">SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT</span> + </dt> + <dd> + For SQLite, this pragma identifies the + maximum size that the journal file is allowed + to be. Berkeley DB does not have a journal + file, but it writes and uses log files. A new + log file is created when the current log file + has reached the defined maximum size. To + define this maximum size for a log file, + specify the SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT + flag. Default value is 10 MB for the Berkeley + DB SQL interface. + </dd> + </dl> + </div> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1193168"></a>Enabling Extensions</h3> + <h3 class="title"><a id="idp224800"></a>Enabling Extensions</h3> </div> </div> </div> <p> - The Berkeley DB SQL API provides extensions such as full text - search and R-Tree index. To enable these extensions, do the - following: - </p> + The Berkeley DB SQL API provides extensions such as + full text search and R-Tree index. To enable these + extensions, do the following: + </p> <div class="orderedlist"> <ol type="1"> <li> - Open the Berkeley DB solution in Visual Studio. - </li> - <li> - Specify <span class="emphasis"><em>SQLITE_ENABLE_FTS3</em></span> or - <span class="emphasis"><em>SQLITE_ENABLE_RTREE</em></span> in - <span class="emphasis"><em>Preprocessor Definitions</em></span> of the - <code class="literal">db_sql</code> project. - </li> - <li> - Re-build the <code class="literal">db_sql</code> project. - </li> + Open the Berkeley DB solution in Visual + Studio. + </li> + <li> + Specify + <span class="emphasis"><em>SQLITE_ENABLE_FTS3</em></span> or + <span class="emphasis"><em>SQLITE_ENABLE_RTREE</em></span> in + <span class="emphasis"><em>Preprocessor Definitions</em></span> + of the <code class="literal">db_sql</code> project. </li> + <li> + Re-build the <code class="literal">db_sql</code> + project. + </li> </ol> </div> - <p> - See the SQLite Documentation for more information on - <a class="ulink" href="http://www.sqlite.org/fts3.html" target="_top">full text search</a> - and <a class="ulink" href="http://www.sqlite.org/rtree.html" target="_top">R-Tree</a>. - </p> + <p> + See the SQLite Documentation for more information + on <a class="ulink" href="http://www.sqlite.org/fts3.html" target="_top">full + text search</a> and <a class="ulink" href="http://www.sqlite.org/rtree.html" target="_top"> + R-Tree</a>. + </p> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> @@ -210,25 +356,28 @@ </div> </div> <p> - You can disable checksums in log records so as to provide a - boost to database performance. However, this comes at the risk - of having undetectable log file corruption that could prevent data - recovery in the event of database corruption. - </p> + You can disable checksums in log records so as to + provide a boost to database performance. However, this + comes at the risk of having undetectable log file + corruption that could prevent data recovery in the + event of database corruption. + </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p> - Note that disabling log record checksums is meant to only be - used with the SQL interface. However, disabling checksums for - the SQL interface also disables checksums for the non-SQL - interfaces. - </p> + Note that disabling log record checksums is + meant to only be used with the SQL interface. + However, disabling checksums for the SQL interface + also disables checksums for the non-SQL + interfaces. + </p> </div> <p> - To disable log checksums, before you build the library edit the - <code class="literal">build_windows/db_config.h</code> file, and delete - the following line: - </p> + To disable log checksums, before you build the + library edit the + <code class="literal">build_windows/db_config.h</code> file, + and delete the following line: + </p> <pre class="programlisting">#define HAVE_LOG_CHECKSUM 1</pre> </div> <div class="sect2" lang="en" xml:lang="en"> @@ -240,92 +389,128 @@ </div> </div> <p> - This section describes the steps to build the JDBC driver. - </p> + This section describes the steps to build the JDBC + driver. + </p> <div class="orderedlist"> <ol type="1"> <li> - <p> - Configure your build environment. For information on how to - configure to build Java applications, see - <a class="xref" href="build_win_java.html" title="Building the Java API">Building the Java API</a>. - </p> + <p> + Configure your build environment. For + information on how to configure to build Java + applications, see <a class="xref" href="build_win_java.html" title="Building the Java API">Building the Java API</a>. + </p> </li> <li> - <p> - Build the SQL project in Debug mode. - </p> + <p> + Build the SQL project in Debug mode. + </p> </li> <li> <p> - Open Berkeley_DB.sln or Berkeley_DB_vs2010.sln in Visual Studio. - If you are using Java 1.6, do the following: - </p> + Open Berkeley_DB.sln or + Berkeley_DB_vs2010.sln in Visual Studio. If + you are using Java 1.6, do the following: + </p> <div class="itemizedlist"> <ul type="disc"> <li> - <p> - In the Solution Explorer, right-click the - <code class="literal">db_sql_jdbc</code> project and select - <span class="emphasis"><em>properties</em></span>. - </p> + <p> + In the Solution Explorer, + right-click the + <code class="literal">db_sql_jdbc</code> + project and select + <span class="emphasis"><em>properties</em></span>. + </p> </li> <li> <p> - In the <span class="emphasis"><em>Configuration Properties -> Build - Events -> Pre-Build Event</em></span> section, - alter the command to refer to <code class="literal">JDBC2z</code> - instead of <code class="literal">JDBC2x</code>. - </p> + In the <span class="emphasis"><em>Configuration + Properties -> Build Events -> + Pre-Build Event</em></span> section, + alter the command to refer to + <code class="literal">JDBC2z</code> instead + of <code class="literal">JDBC2x</code>. + </p> </li> </ul> </div> <p> - If you are using Java 1.7, do the following: - </p> + If you are using Java 1.7, do the + following: + </p> <div class="itemizedlist"> <ul type="disc"> <li> <p> - In the Solution Explorer, right-click the - <code class="literal">db_sql_jdbc</code> project and select - <span class="emphasis"><em>properties</em></span>. - </p> + In the Solution Explorer, + right-click the + <code class="literal">db_sql_jdbc</code> + project and select + <span class="emphasis"><em>properties</em></span>. + </p> </li> <li> <p> - In the <span class="emphasis"><em>Configuration Properties -> Build - Events -> Pre-Build Event</em></span> section, - alter the command to refer to - <code class="literal">JDBC2z1</code> instead of - <code class="literal">JDBC2x</code>. Also, remove the option of - "-target 1.5". - </p> + In the <span class="emphasis"><em>Configuration + Properties -> Build Events -> + Pre-Build Event</em></span> section, + alter the command to refer to + <code class="literal">JDBC2z1</code> instead + of <code class="literal">JDBC2x</code>. Also, + remove the option of "-target 1.5". + </p> </li> <li> <p> - Go to <code class="literal">db\lang\sql\jdbc\SQLite</code>, and - replace <code class="literal">JDBCDriver.java</code> with - <code class="literal">JDBCDriver.java17</code>, and replace - <code class="literal">JDBCDataSource.java</code> with - <code class="literal">JDBCDataSource.java17</code>. - </p> + Go to + <code class="literal">db\lang\sql\jdbc\SQLite</code>, + and replace + <code class="literal">JDBCDriver.java</code> + with + <code class="literal">JDBCDriver.java17</code>, + and replace + <code class="literal">JDBCDataSource.java</code> + with + <code class="literal">JDBCDataSource.java17</code>. + </p> </li> </ul> </div> </li> <li> - Build the <code class="filename">db_sql_jdbc</code> project in Visual Studio. - </li> + <p> + To enable encryption in the Berkeley DB SQL + JDBC driver, make sure the + <code class="literal">db_dql</code> project is built + with encryption enabled and specify + <code class="literal">HAVE_SQLITE3_KEY</code> in + <code class="literal">Preprocessor + Definitions</code> of the + <code class="filename">db_sql_jdbc</code> project. + See <a href="../bdb-sql/sql_encryption.html" class="olink">SQL Encryption</a> in the + <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide + for usage details. + </p> + </li> + <li> + <p> + Build the <code class="filename">db_sql_jdbc</code> + project in Visual Studio. + </p> + </li> </ol> </div> - <p> - You can test the build by entering the following commands from the - <code class="literal">db\build_windows\Win32\Debug</code> directory: - </p> + <p> + You can test the build by entering + the following commands from the + <code class="literal">db\build_windows\Win32\Debug</code> + directory: + </p> <table class="simplelist" border="0" summary="Simple list"> <tr> - <td> javac -cp ".;jdbc.jar" -d . ..\..\..\sql\jdbc\test3.java </td> + <td> javac -cp ".;jdbc.jar" -d . + ..\..\..\lang\sql\jdbc\test3.java </td> </tr> <tr> <td>java -cp ".;jdbc.jar" test3 </td> @@ -336,48 +521,97 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm313872"></a>Using the JDBC Driver</h3> + <h3 class="title"><a id="idp339720"></a>Using the JDBC Driver</h3> </div> </div> </div> <p> - This section describes the steps to download, build, and run - sample programs using the built JDBC driver. - </p> + This section describes the steps to download, + build, and run sample programs using the built JDBC + driver. + </p> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idm626152"></a>Downloading JDBC Sample Code</h4> + <h4 class="title"><a id="idp356776"></a>Downloading JDBC Sample Code</h4> </div> </div> </div> <p> - The download link for JDBC sample code is available on the - <a class="ulink" href="http://www.oracle.com/technetwork/java/index-139949.html" target="_top"> - Oracle Technology Network (OTN) - </a>. You can identify - the link by the "JDBC programming examples from all three - editions (ZIP format)" text beside it. - </p> + The download link for JDBC sample code is + available on the <a class="ulink" href="http://www.oracle.com/technetwork/java/index-139949.html" target="_top"> + Oracle Technology Network (OTN) </a>. + You can identify the link by the "JDBC programming + examples from all three editions (ZIP format)" + text beside it. + </p> </div> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp67696"></a>Modifying Sample Code</h4> + <h4 class="title"><a id="idp386864"></a>Modifying Sample Code</h4> </div> </div> </div> - <p>Before running the sample code, do the following:</p> + <p> + Before running the sample code, do the + following: + </p> <div class="orderedlist"> <ol type="1"> - <li>Unzip the file containing the sample code to a new directory (for example, jdbc_ex).</li> - <li>Substitute <code class="literal">jdbc:sqlite:/<db-file-name></code> for the generic JDBC URL that appears in the code. That is, put <code class="literal">jdbc:sqlite:/<db-file-name></code> between the quotation marks in the line: - <p><code class="literal"> String url = "jdbc:mySubprotocol:myDataSource";</code></p><p> Note: The <db-file-name> can either be an absolute path name like <code class="literal">"D:\\jdbc_ex_db\\myDataSource"</code>, or a relative path-file-name like <code class="literal">"..\\jdbc_ex_db\myDataSource"</code>, or a file name, like <code class="literal">"myDataSource"</code>, in which the database file will be stored at the current directory.</p></li> - <li>Substitute <code class="literal">SQLite.JDBCDriver</code> for <code class="literal">myDriver.ClassName</code> in the line: <code class="literal">Class.forName("myDriver.ClassName");</code></li> - <li>Substitute the username and password you use for your database in the following: <code class="literal">"myLogin", "myPassword"</code>. <p>This is optional.</p></li> - <li>If your JDK version is above 1.5, change the variable name <code class="literal">enum</code> in <code class="literal">OutputApplet.java</code> to some other variable name because, as of JDK release 5 <code class="literal">enum</code> is a keyword and can not be used as an identifier.</li> + <li> + Unzip the file containing the sample + code to a new directory (for example, + jdbc_ex). + </li> + <li> + Substitute + <code class="literal">jdbc:sqlite:/<db-file-name></code> + for the generic JDBC URL that appears in the + code. That is, put + <code class="literal">jdbc:sqlite:/<db-file-name></code> + between the quotation marks in the line: + <p> + <code class="literal"> String url = + "jdbc:mySubprotocol:myDataSource";</code> + </p><p> + Note: The <db-file-name> can + either be an absolute path name like + <code class="literal">"jdbc:sqlite:/D:\\jdbc_ex_db\\myDataSource"</code>, + or a relative path-file-name like + <code class="literal">"jdbc:sqlite:/..\\jdbc_ex_db\myDataSource"</code>, + or a file name, like + <code class="literal">"jdbc:sqlite:/myDataSource"</code>, + in which the database file will be stored + at the current directory. Note that all + path arguments require a leading slash, + even in the case of relative paths or a + database in the local directory. Please + refer to the above examples. + </p></li> + <li> + Substitute + <code class="literal">SQLite.JDBCDriver</code> for + <code class="literal">myDriver.ClassName</code> in + the line: + <code class="literal">Class.forName("myDriver.ClassName");</code></li> + <li> + Substitute the username and password you + use for your database in the following: + <code class="literal">"myLogin", + "myPassword"</code>. <p>This is + optional.</p></li> + <li> + If your JDK version is above 1.5, change + the variable name <code class="literal">enum</code> in + <code class="literal">OutputApplet.java</code> to + some other variable name because, as of JDK + release 5 <code class="literal">enum</code> is a keyword + and can not be used as an + identifier. + </li> </ol> </div> </div> @@ -385,21 +619,35 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp78192"></a>Building and Running the JDBC Sample code</h4> + <h4 class="title"><a id="idp356840"></a>Building and Running the JDBC Sample code</h4> </div> </div> </div> - <p>See <a class="xref" href="build_win_sql.html#build_jdbc" title="Building the JDBC Driver">Building the JDBC Driver</a> for instructions about building JDBC driver.</p> - <p>To build and run the JDBC examples do the following:</p> + <p> + See <a class="xref" href="build_win_sql.html#build_jdbc" title="Building the JDBC Driver">Building the JDBC Driver</a> for instructions + about building JDBC driver. + </p> + <p> + To build and run the JDBC examples do the + following: + </p> <div class="orderedlist"> <ol type="1"> - <li>In the <code class="literal">db\build_windows\Win32\Debug</code> directory, run following commands: - <pre class="programlisting"> + <li> + In the + <code class="literal">db\build_windows\Win32\Debug</code> + directory, run following commands: + <pre class="programlisting"> $ javac -classpath ".;jdbc.jar" -d . \path\to\jdbc_ex\*.java - $ java -classpath ".;jdbc.jar" <ClassName, eg. CreateCoffees> - </pre></li> - <li>After you run the CreateCoffees example, use the <code class="literal">dbsql</code> executable to open the <code class="literal">myDataSource</code> database file and check if the table <code class="literal">COFFEES</code> has been successfully created in the database. - <pre class="programlisting"> + $ java -classpath ".;jdbc.jar" <ClassName, eg. CreateCoffees></pre></li> + <li> + After you run the CreateCoffees example, + use the <code class="literal">dbsql</code> executable to + open the <code class="literal">myDataSource</code> + database file and check if the table + <code class="literal">COFFEES</code> has been + successfully created in the database. + <pre class="programlisting"> $ dbsql myDataSourcedbsql> .tables COFFEES dbsql> .dump @@ -408,10 +656,17 @@ CREATE TABLE COFFEES (COF_NAME varchar(32),/ SUP_ID int, PRICE float, SALES int, TOTAL int); COMMIT; - dbsql> - </pre></li> - <li>Repeat step 2 to run other examples. - <p>Note: Some examples like AutoGenKeys are not yet supported by BDB JDBC driver. The <code class="literal">SQLFeatureNotSupportedException</code> is displayed for those unsupported examples.</p></li> + dbsql></pre></li> + <li> + Repeat step 2 to run other examples. + <p> + Note: Some examples like AutoGenKeys + are not yet supported by BDB JDBC driver. + The + <code class="literal">SQLFeatureNotSupportedException</code> + is displayed for those unsupported + examples. + </p></li> </ol> </div> </div> @@ -420,34 +675,158 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1594400"></a>Building the ODBC Driver</h3> + <h3 class="title"><a id="idp367344"></a>Using the JDBC Driver in ADF/JDeveloper</h3> </div> </div> </div> <p> - This section describes the steps required to build the ODBC driver.</p> + This section describes steps to use BDB JDBC driver in the integrated + development environment ADF/JDeveloper. + </p> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Build the JDBC driver. For more information, see <a class="xref" href="build_win_sql.html#build_jdbc" title="Building the JDBC Driver">Building the JDBC Driver</a> . + </p> + <p> + Ensure that the Java environment used to build the JDBC driver is + same as used in ADF/JDeveloper. + </p> + <p> + Include JDBC driver path in the system <code class="literal">CLASSPATH</code> + and <code class="literal">LD_LIBRARY_PATH</code>. + </p> + </li> + <li> + <p> + Create BDB JDBC Database Connection in JDeveloper. + ADF accesses the database by Database Connection. As long as the + database file exists and has tables, you can see all tables located + by the database connection in the project application resources panel. + </p> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <p> + Select <span class="emphasis"><em>File</em></span> -> <span class="emphasis"><em>New</em></span> -> + <span class="emphasis"><em>General</em></span> -> <span class="emphasis"><em>Connections</em></span> -> + <span class="emphasis"><em>Database Connection</em></span>. + </p> + <div class="orderedlist"> + <ol type="a"> + <li> + In the panel of <code class="literal">"Create Database Connection",</code> choose + <code class="literal">"Generic JDBC"</code> as <code class="literal">"Connection Type"</code>. + </li> + <li> + In the <code class="literal">"Generic JDBC Settings"</code> section, select <code class="literal"> + "New"</code> to register a JDBC driver. + </li> + </ol> + </div> + </li> + <li> + <p> + In the registration form, enter <code class="literal">"SQLite.JDBCDriver"</code> + for Driver Class. + </p> + <div class="orderedlist"> + <ol type="a"> + <li> + Select <code class="literal">"Browse"</code> to locate the library. + </li> + <li> + In the library information form, select <span class="emphasis"><em>User</em></span> -> + <span class="emphasis"><em>New</em></span> to create a library. + </li> + <li> + Enter <code class="literal">"DBSQL_JDBC"</code> for <code class="literal">"Library Name,"</code> and add the path of the JDBC driver + to the Class Path. + </li> + <li> + Select <code class="literal">"OK"</code> to save. + </li> + </ol> + </div> + </li> + <li> + <p> + Test the connection in the panel of Create Database Connection. + </p> + <div class="orderedlist"> + <ol type="a"> + <li> + Configure the JDBC URL with <code class="literal">jdbc:sqlite:/<db-file-name></code>. The + <code class="literal"><db-file-name></code> should include the database file path which must be + absolute. + </li> + <li> + Select Test Connection. If the connection is proved to be + working, a <code class="literal">"Success"</code> message is displayed. + </li> + </ol> + </div> + </li> + </ul> + </div> + </li> + <li> + <p> + Apply BDB JDBC Database Connection in the ADF application. + After successfully creating the database connection, you can create + and initialize ADF BC component with it. During initialization, choose + <code class="literal">"SQL92"</code> as SQL Platform and <code class="literal">"Java"</code> + as Data Type Map for the connection. + </p> + <p> + You can define the ADF BC component by adding entity objects, view objects + etc. and the database connection takes charge of accessing the database. + For more information, see the example <code class="literal">lang/sql/adf/EX_ADF</code>. + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp375344"></a>Building the ODBC Driver</h3> + </div> + </div> + </div> + <p> + This section describes the steps required to build + the ODBC driver. + </p> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp69920"></a>Configuring Your System</h4> + <h4 class="title"><a id="idp410816"></a>Configuring Your System</h4> </div> </div> </div> <p> - To configure your system prior to building the ODBC driver, do the following: - </p> + To configure your system prior to building the + ODBC driver, do the following: + </p> <div class="orderedlist"> <ol type="1"> - <li> - Download and install the latest SQLite ODBC driver Windows installer package for <a class="ulink" href="http://www.ch-werner.de/sqliteodbc/sqliteodbc.exe" target="_top">32 bit Windows</a> or <a class="ulink" href="http://www.ch-werner.de/sqliteodbc/sqliteodbc_w64.exe" target="_top">64 bit Windows</a>. - </li> - <li> - Download and install the latest - <a class="ulink" href="http://www.microsoft.com/download/en/details.aspx?id=21995" target="_top"> - Microsoft Data Access Components (MDAC) SDK - </a>. The MDAC SDK is only required for testing the installation. - </li> + <li> + Download and install the latest SQLite + ODBC driver Windows installer package for + <a class="ulink" href="http://www.ch-werner.de/sqliteodbc/sqliteodbc.exe" target="_top">32 bit Windows</a> + or <a class="ulink" href="http://www.ch-werner.de/sqliteodbc/sqliteodbc_w64.exe" target="_top"> + 64 bit Windows</a>. + </li> + <li> + Download and install the latest + <a class="ulink" href="http://www.microsoft.com/en-us/download/details.aspx?id=21995" target="_top"> + Microsoft Data Access Components (MDAC) SDK </a>. The MDAC SDK is + only required for testing the installation. + </li> </ol> </div> </div> @@ -455,63 +834,134 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp97216"></a>Building the Library</h4> + <h4 class="title"><a id="idp412408"></a>Building the Library</h4> </div> </div> </div> <div class="orderedlist"> <ol type="1"> + <li> + Build the SQL project in Release mode. + See <a class="xref" href="build_win_sql.html" title="Building the SQL API">Building the SQL API</a>. + </li> + <li> + Open Visual Studio. + </li> + <li> + Load the Berkeley_DB solution file into + Visual Studio. + </li> + <li> + Set the build target to + <span class="emphasis"><em>Release</em></span></li> <li> - Build the SQL project in Release mode. See <a class="xref" href="build_win_sql.html" title="Building the SQL API">Building the SQL API</a>. - </li> - <li>Open Visual Studio.</li> - <li>Load the Berkeley_DB solution file into Visual Studio.</li> - <li>Set the build target to <span class="emphasis"><em>Release</em></span></li> - <li>Build the solution.</li> + Build the solution. + </li> <li> - Select <span class="emphasis"><em>File</em></span> -> <span class="emphasis"><em>Add</em></span> -> <span class="emphasis"><em>Existing Project</em></span>. - </li> - <li>Select <code class="filename">build_windows</code>.</li> + Select <span class="emphasis"><em>File</em></span> -> + <span class="emphasis"><em>Add</em></span> -> + <span class="emphasis"><em>Existing Project</em></span>. + </li> <li> - Select the appropriate directory for your compiler: <code class="filename">VS8</code> or <code class="filename">VS10</code>. - </li> + Select + <code class="filename">build_windows</code>. + </li> <li> - Select <code class="filename">db_sql_odbc.vcproj</code> and add it to the Berkeley_DB solution. - This adds the <code class="filename">db_sql_odbc</code> Visual Studio project to the Berkeley_DB solution file. - </li> - <li>Build the <code class="filename">db_sql_odbc</code> project. This can be done by right-clicking the <code class="filename">db_sql_odbc</code> project in the project explorer panel, and selecting <code class="literal">build</code>.</li> + Select the appropriate directory for + your compiler: <code class="filename">VS8</code> or + <code class="filename">VS10</code>. + </li> + <li> + Select + <code class="filename">db_sql_odbc.vcproj</code> + and add it to the Berkeley_DB solution. This + adds the <code class="filename">db_sql_odbc</code> + Visual Studio project to the Berkeley_DB + solution file. + </li> + <li> + Build the + <code class="filename">db_sql_odbc</code> project. + This can be done by right-clicking the + <code class="filename">db_sql_odbc</code> project + in the project explorer panel, and selecting + <code class="literal">build</code>. + </li> </ol> </div> - <p>The <code class="literal">sqlite3odbc.dll</code>, <code class="literal">libdb_sql53.dll</code> and <code class="literal">libdb53.dll</code> files are now built.</p> + <p> + The <code class="literal">db_sql_odbc61.dll</code>, + <code class="literal">libdb_sql61.dll</code> and + <code class="literal">libdb61.dll</code> files are now + built. + </p> </div> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp81624"></a>Installing the Library</h4> + <h4 class="title"><a id="idp420848"></a>Installing the Library</h4> </div> </div> </div> - <p>Copy the dll files built in the <span class="emphasis"><em>Building the Library</em></span> section to the Windows system folder.</p> - <p>The Windows system folder is different on different systems, but is often <code class="literal">C:\WINDOWS\System32</code>.</p> + <p> + Rename <code class="literal">db_sql_odbc61.dll</code> + to <code class="literal">sqlite3odbc.dll</code> + and copy the dll files built in the + <span class="emphasis"><em>Building the Library</em></span> + section to the Windows system folder. + </p> + <p> + The Windows system folder is different on + different systems, but is often + <code class="literal">C:\WINDOWS\System32</code>. + </p> </div> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp92728"></a>Testing the ODBC Install</h4> + <h4 class="title"><a id="idp344512"></a>Testing the ODBC Install</h4> </div> </div> </div> - <p>The steps to verify that the installed driver works are as follows:</p> + <p> + The steps to verify that the installed driver + works are as follows: + </p> <div class="orderedlist"> <ol type="1"> - <li>Open the Unicode ODBCTest application. On Windows XP: <span class="emphasis"><em>Windows start</em></span> -> <span class="emphasis"><em>Microsoft Data Access SDK 2.8</em></span> -> <span class="emphasis"><em>ODBCTest (Unicode, x86).</em></span></li> - <li>Select the <span class="emphasis"><em>Conn</em></span> -> <span class="emphasis"><em>Full Connect...</em></span> menu item.</li> - <li>Select <code class="literal">SQLite3 Datasource</code> and click <code class="literal">OK</code>.</li> - <li>Select the <span class="emphasis"><em>Stmt</em></span> -> <span class="emphasis"><em>SQLExecDirect...</em></span> menu item.</li> - <li>Enter <code class="literal">CREATE TABLE t1(x);</code> in the <code class="literal">Statement</code> text box and click <code class="literal">OK</code>.</li> - <li>Verify that no error messages were output to the error window.</li> + <li> + Open the Unicode ODBCTest application. + On Windows: <span class="emphasis"><em>Windows + start</em></span> -> <span class="emphasis"><em>Microsoft + Data Access SDK 2.8</em></span> -> + <span class="emphasis"><em>ODBCTest (Unicode, + x86).</em></span></li> + <li> + Select the <span class="emphasis"><em>Conn</em></span> -> + <span class="emphasis"><em>Full Connect...</em></span> menu + item. + </li> + <li> + Select <code class="literal">SQLite3 + Datasource</code> and click + <code class="literal">OK</code>.</li> + <li> + Select the <span class="emphasis"><em>Stmt</em></span> -> + <span class="emphasis"><em>SQLExecDirect...</em></span> menu + item. + </li> + <li> + Enter <code class="literal">CREATE TABLE + t1(x);</code> in the + <code class="literal">Statement</code> text box and + click <code class="literal">OK</code>. + </li> + <li> + Verify that no error messages were + output to the error window. + </li> </ol> </div> </div> @@ -520,18 +970,17 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm313808"></a> Using the ADO.NET Driver - </h3> + <h3 class="title"><a id="idp416760"></a> Using the ADO.NET Driver </h3> </div> </div> </div> <p> - Go to the - <a class="ulink" href="http://www.oracle.com/technetwork/database/berkeleydb/downloads/index.html" target="_top">Oracle Berkeley DB download page</a>, - and download the ADO.NET package. Build the package by following - the <a href="../bdb-sql/buildinstall.html#ado_net" class="olink">instructions</a> included - in the package. - </p> + Go to the <a class="ulink" href="http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index.html" target="_top">Oracle + Berkeley DB download page</a>, and download + the ADO.NET package. Build the package by following + the <a href="../bdb-sql/buildinstall.html#ado_net" class="olink"> + instructions</a> included in the package. + </p> </div> </div> <div class="navfooter"> diff --git a/docs/installation/build_win_tcl.html b/docs/installation/build_win_tcl.html index 48d2d114..6b70a5d9 100644 --- a/docs/installation/build_win_tcl.html +++ b/docs/installation/build_win_tcl.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="build_win_sql.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="win_build_dist_dll.html">Next</a></td> </tr> </table> @@ -38,80 +36,117 @@ </div> </div> </div> - <p>Tcl support is not built automatically. See - <a href="../programmer_reference/tcl.html#tcl_intro" class="olink">Loading Berkeley DB with Tcl</a> for -information on sites from which you can download Tcl and which Tcl -versions are compatible with Berkeley DB. These notes assume that Tcl is -installed as <code class="filename">d:\tcl</code>, but you can change that if you want.</p> - <p>The Tcl library must be built as the same build type as the Berkeley DB -library (both Release or both Debug). We found that the binary -release of Tcl can be used with the Release configuration of Berkeley DB, -but you will need to build Tcl from sources for the Debug -configuration. Before building Tcl, you will need to modify its -makefile to make sure that you are building a debug version, including -thread support. This is because the set of DLLs linked into the Tcl -executable must match the corresponding set of DLLs used by Berkeley DB.</p> + <p> + Tcl support is not built automatically. See <a href="../programmer_reference/tcl.html#tcl_intro" class="olink">Loading Berkeley DB with Tcl</a> + for information on sites from which you can download Tcl + and which Tcl versions are compatible with Berkeley DB. + These notes assume that Tcl is installed as + <code class="filename">d:\tcl</code>, but you can change that + if you want. + </p> + <p> + The Tcl library must be built as the same build type as + the Berkeley DB library (both Release or both Debug). We + found that the binary release of Tcl can be used with the + Release configuration of Berkeley DB, but you will need to + build Tcl from sources for the Debug configuration. Before + building Tcl, you will need to modify its makefile to make + sure that you are building a debug version, including + thread support. This is because the set of DLLs linked + into the Tcl executable must match the corresponding set + of DLLs used by Berkeley DB. + </p> <div class="orderedlist"> <ol type="1"> - <li>Set the include directories. -<div class="itemizedlist"><ul type="disc"><li> -In Visual Studio 2005/Visual Studio 2008 - -Choose <span class="emphasis"><em>Tools -> Options --> Projects -> VC++ Directories</em></span>. Under the "Show -directories for" pull-down, select "Include files". Add the full -pathname for <code class="filename">d:\tcl\include</code>, then click OK. -</li><li> -In Visual Studio 2010 - Right-click db_java project, choose <span class="emphasis"><em>Properties->Configuration Properties-> VC++ Directories->Include Directories</em></span>. -Add the full pathnames for <code class="filename">d:\tcl\include</code>, then click OK. -</li></ul></div> -This is the -directory that contains <code class="filename">tcl.h</code>.</li> - <li>Set the library files directory. -<div class="itemizedlist"><ul type="disc"><li> -In Visual Studio 2005/Visual Studio 2008 - -Choose <span class="emphasis"><em>Tools -> -Options -> Projects -> VC++ Directories</em></span>. Under the "Show -directories for" pull-down, select "Library files". Add the full -pathname for the <code class="filename">d:\tcl\lib</code> directory, then click OK. -</li><li> -In Visual Studio 2010 - Right-click db_java project, choose <span class="emphasis"><em>Properties->Configuration Properties-> VC++ Directories->Library Directories</em></span>. Add the full pathname for the <code class="filename">d:\tcl\lib</code> directory, then click OK. -</li></ul></div> - -This is the directory needed to find -<code class="filename">tcl85g.lib</code> (or whatever the -library is named in your distribution).</li> - <li>Set the build type to Release or Debug in the drop-down on the -tool bar.</li> <li> - <p> - To build, right-click on db_tcl and select Build. This builds the Tcl - support library for Berkeley DB, placing the result into one of the - following Berkeley DB subdirectories, depending upon the - configuration that you chose: - </p> + Set the include directories. + <div class="itemizedlist"><ul type="disc"><li> + In Visual Studio 2005/Visual Studio + 2008 - Choose <span class="emphasis"><em>Tools -> Options + -> Projects -> VC++ + Directories</em></span>. Under the "Show + directories for" pull-down, select "Include + files". Add the full pathname for + <code class="filename">d:\tcl\include</code>, then + click OK. + </li><li> + In Visual Studio 2010/Visual Studio 2012 - Right-click + db_tcl project, choose + <span class="emphasis"><em>Properties->Configuration + Properties-> VC++ + Directories->Include + Directories</em></span>. Add the full + pathnames for + <code class="filename">d:\tcl\include</code>, then + click OK. + </li></ul></div> + This is the directory that contains + <code class="filename">tcl.h</code>. + </li> + <li> + Set the library files directory. + <div class="itemizedlist"><ul type="disc"><li> + In Visual Studio 2005/Visual Studio + 2008 - Choose <span class="emphasis"><em>Tools -> Options + -> Projects -> VC++ + Directories</em></span>. Under the "Show + directories for" pull-down, select "Library + files". Add the full pathname for the + <code class="filename">d:\tcl\lib</code> directory, + then click OK. + </li><li> + In Visual Studio 2010 - Right-click + db_tcl project, choose + <span class="emphasis"><em>Properties->Configuration + Properties-> VC++ + Directories->Library + Directories</em></span>. Add the full + pathname for the + <code class="filename">d:\tcl\lib</code> directory, + then click OK. + </li></ul></div> + This is the directory needed to find + <code class="filename">tcl85.lib</code> (or whatever the + library is named in your distribution). + </li> + <li> + Set the build type to Release or Debug in the + drop-down on the tool bar. + </li> + <li> + <p> + To build, right-click on db_tcl and select + Build. This builds the Tcl support library for + Berkeley DB, placing the result into one of the + following Berkeley DB subdirectories, depending + upon the configuration that you chose: + </p> <table class="simplelist" border="0" summary="Simple list"> <tr> <td> - <code class="filename">build_windows\Win32\Debug\libdb_tcl53d.dll</code> + <code class="filename">build_windows\Win32\Debug\libdb_tcl61d.dll</code> </td> </tr> <tr> <td> - <code class="filename">build_windows\Win32\Release\libdb_tcl53.dll</code> + <code class="filename">build_windows\Win32\Release\libdb_tcl61.dll</code> </td> </tr> </table> </li> </ol> </div> - <p>If you use a version different from Tcl 8.5.x you will -need to change the name of the Tcl library used in the build (for -example, <code class="filename">tcl85g.lib</code>) to the -appropriate name. To do this, right click on <span class="emphasis"><em>db_tcl</em></span>, go to -<span class="emphasis"><em>Properties -> Linker -> Input -> Additional -dependencies</em></span> and change -<code class="filename">tcl85g.lib</code> to match the Tcl -version you are using.</p> + <p> + If you use a version different from Tcl 8.5.x you will + need to change the name of the Tcl library used in the + build (for example, <code class="filename">tcl85.lib</code>) to the + appropriate name. To do this, right click on + <span class="emphasis"><em>db_tcl</em></span>, go to + <span class="emphasis"><em>Properties -> Linker -> Input -> + Additional dependencies</em></span> and change + <code class="filename">tcl85.lib</code> to match the Tcl + version you are using. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/build_win_test.html b/docs/installation/build_win_test.html index dc477e01..9a870241 100644 --- a/docs/installation/build_win_test.html +++ b/docs/installation/build_win_test.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">Running the test suite under Windows</th> + <th colspan="3" align="center">Running the test suite under + Windows</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_win_small.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="build_win_notes.html">Next</a></td> </tr> </table> @@ -34,7 +33,8 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_win_test"></a>Running the test suite under Windows</h2> + <h2 class="title" style="clear: both"><a id="build_win_test"></a>Running the test suite under + Windows</h2> </div> </div> </div> @@ -42,111 +42,231 @@ <dl> <dt> <span class="sect2"> - <a href="build_win_test.html#idp126120">Building the software needed by the tests</a> + <a href="build_win_test.html#idp458352">Building the software needed + by the tests</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_test.html#idp137576">Running the test suite under Windows</a> + <a href="build_win_test.html#idp389880">Running the test suite under Windows</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_test.html#build_win_test_sql">Building the software needed by the SQL tests</a> + <a href="build_win_test.html#build_win_test_sql">Building the software + needed by the SQL tests</a> </span> </dt> </dl> </div> - <p>To build the test suite on Windows platforms, you will need to configure -Tcl support. You will also need sufficient main memory (at least 64MB), -and disk (around 250MB of disk will be sufficient).</p> - <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="idp126120"></a>Building the software needed by the tests</h3></div></div></div> -The test suite must be run against a Debug version of -Berkeley DB, so you will need a Debug version of the Tcl -libraries. This involves building Tcl from its source. See the Tcl -sources for more information. -Then build the Tcl API - see -<a class="xref" href="build_win_tcl.html" title="Building the Tcl API">Building the Tcl API</a> for details. -<div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="idp134640"></a>Visual Studio 2005 or newer</h4></div></div></div><p>To build for testing, perform the following steps:</p><p> -</p><div class="orderedlist"><ol type="1"><li>Open the Berkeley DB solution.</li><li>Ensure that the target configuration is Debug</li><li>Right click the <span class="emphasis"><em>db_tcl</em></span> project in the Solution Explorer, and select <span class="emphasis"><em>Build</em></span>.</li><li>Right click the <span class="emphasis"><em>db_test</em></span> project in the Solution Explorer, and select <span class="emphasis"><em>Build</em></span>.</li></ol></div><p> - -</p></div></div> + <p> + To build the test suite on Windows platforms, you will need + to configure Tcl support. You will also need sufficient main + memory (at least 64MB), and disk (around 250MB of disk will be + sufficient). + </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp137576"></a>Running the test suite under Windows</h3> + <h3 class="title"><a id="idp458352"></a>Building the software needed + by the tests</h3> </div> </div> </div> - <p>Before running the tests for the first time, you must edit the file -<code class="filename">include.tcl</code> in your build directory and change the line -that reads:</p> + <p> + The test suite must be run against a Debug version of + Berkeley DB, so you will need a Debug version of the Tcl + libraries. This involves building Tcl from its source. See + the Tcl sources for more information. Then build the Tcl + API - see <a class="xref" href="build_win_tcl.html" title="Building the Tcl API">Building the Tcl API</a> for details. + </p> + <div class="sect3" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h4 class="title"><a id="idp472136"></a>Visual Studio 2005 or newer</h4> + </div> + </div> + </div> + <p> + To build for testing, perform the following steps: + </p> + <div class="orderedlist"> + <ol type="1"> + <li> + Open the Berkeley DB solution. + </li> + <li> + Ensure that the target configuration is + Debug + </li> + <li> + Right click the <span class="emphasis"><em>db_tcl</em></span> + project in the Solution Explorer, and select + <span class="emphasis"><em>Build</em></span>. + </li> + <li> + Right click the + <span class="emphasis"><em>db_test</em></span> project in the + Solution Explorer, and select + <span class="emphasis"><em>Build</em></span>. + </li> + </ol> + </div> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp389880"></a>Running the test suite under Windows</h3> + </div> + </div> + </div> + <p> + Before running the tests for the first time, you must + edit the file <code class="filename">include.tcl</code> in your + build directory and change the line that reads: + </p> <pre class="programlisting">set tclsh_path SET_YOUR_TCLSH_PATH</pre> - <p>You will want to use the location of the <code class="filename">tclsh</code> program (be -sure to include the name of the executable). For example, if Tcl is -installed in <code class="filename">d:\tcl</code>, this line should be the following:</p> - <pre class="programlisting">set tclsh_path d:\tcl\bin\tclsh85g.exe</pre> - <p>If your path includes spaces be sure to enclose it in quotes:</p> - <pre class="programlisting">set tclsh_path "c:\Program Files\tcl\bin\tclsh85g.exe"</pre> - <p>Make sure that the path to Berkeley DB's tcl library is in your -current path. On Windows NT/2000/XP, edit your PATH using the My -Computer -> Properties -> Advanced -> Environment -Variables dialog. On earlier versions of Windows, you may find it -convenient to add a line to c:\AUTOEXEC.BAT:</p> + <p> + You will want to use the location of the + <code class="filename">tclsh</code> program (be sure to include + the name of the executable). For example, if Tcl is + installed in <code class="filename">d:\tcl</code>, this line should + be the following: + </p> + <pre class="programlisting">set tclsh_path d:\tcl\bin\tclsh85.exe</pre> + <p> + If your path includes spaces be sure to enclose it in + quotes: + </p> + <pre class="programlisting">set tclsh_path "c:\Program Files\tcl\bin\tclsh85.exe"</pre> + <p> + Make sure that the path to Berkeley DB's tcl library is + in your current path. Edit your PATH using the Control + Panel -> System -> Advanced system settings + -> Environment Variables dialog. On earlier versions of + Windows, you may find it convenient to add a line to + c:\AUTOEXEC.BAT: + </p> <pre class="programlisting">SET PATH=%PATH%;c:\db\build_windows</pre> - <p>Then, in a shell of your choice enter the following commands:</p> + <p> + Then, in a shell of your choice enter the following + commands: + </p> <div class="orderedlist"> <ol type="1"> - <li>cd build_windows</li> - <li>run <code class="filename">d:\tcl\bin\tclsh85g.exe</code>, or the equivalent name of -the Tcl shell for your system. -<p>You should get a "%" prompt.</p></li> - <li>% source ../test/tcl/test.tcl -<p>If no errors occur, you should get a "%" prompt.</p></li> + <li> + cd build_windows + </li> + <li> + run + <code class="filename">d:\tcl\bin\tclsh85.exe</code>, or the + equivalent name of the Tcl shell for your system. + <p> + You should get a "%" prompt. + </p></li> + <li> + % source ../test/tcl/test.tcl + <p> + If no + errors occur, you should get a "%" prompt. + </p></li> </ol> </div> - <p>You are now ready to run tests in the test suite; see - Running the test suite for more -information.</p> + <p> + You are now ready to run tests in the test suite; see + Running the test suite for more information. + </p> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="build_win_test_sql"></a>Building the software needed by the SQL tests</h3> + <h3 class="title"><a id="build_win_test_sql"></a>Building the software + needed by the SQL tests</h3> </div> </div> </div> - <p> The SQL test suite must be run against a Debug version of Berkeley DB, so you need a Debug version of the Tcl libraries. This involves building Tcl from its source. See the Tcl sources for more information. Then build the Tcl API - see <a class="xref" href="build_win_tcl.html" title="Building the Tcl API">Building the Tcl API</a> for details. - </p> - <p>Before building for SQL tests, build the db_tcl and db_sql_testfixture projects. This requires Tcl 8.5 or above. If you are using a later version of Tcl, edit the Tcl library that db_tcl and db_sql_testfixture link to. </p> - <p>To do this right click the <span class="emphasis"><em>db_tcl</em></span><code class="literal">/</code><span class="emphasis"><em>db_sql_testfixture</em></span> project, select <span class="emphasis"><em>Properties->Configuration Properties->Linker->Input->Additional Dependencies</em></span> and edit the Tcl library, <span class="emphasis"><em>tcl85g.lib</em></span>, to match the version you are using. - </p> - <p>Building the db_sql_testfixture project builds the testfixture.exe program in <code class="literal">../build_windows/Win32/Debug</code>. It also builds the projects db and db_sql, on which it depends. - </p> + <p> + The SQL test suite must be run against a Debug version + of Berkeley DB, so you need a Debug version of the Tcl + libraries. This involves building Tcl from its source. See + the Tcl sources for more information. Then build the Tcl + API - see <a class="xref" href="build_win_tcl.html" title="Building the Tcl API">Building the Tcl API</a> for details. + </p> + <p> + Before building for SQL tests, build the db_tcl and + db_sql_testfixture projects. This requires Tcl 8.5 or + above. If you are using a later version of Tcl, edit the + Tcl library that db_tcl and db_sql_testfixture link to. + </p> + <p> + To do this right click the + <span class="emphasis"><em>db_tcl</em></span><code class="literal">/</code><span class="emphasis"><em>db_sql_testfixture</em></span> + project, select <span class="emphasis"><em>Properties -> Configuration + Properties -> Linker -> Input -> Additional + Dependencies</em></span> and edit the Tcl library, + <span class="emphasis"><em>tcl85.lib</em></span>, to match the version + you are using. + </p> + <p> + Building the db_sql_testfixture project builds the + testfixture.exe program in + <code class="literal">../build_windows/Win32/Debug</code>. It + also builds the projects db and db_sql, on which it + depends. + </p> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp154912"></a>Visual Studio 2005 or newer</h4> + <h4 class="title"><a id="idp488224"></a>Visual Studio 2005 or newer</h4> </div> </div> </div> - <p> To build for testing, perform the following steps:</p> + <p> + To build for testing, perform the following steps: + </p> <div class="orderedlist"> <ol type="1"> - <li>Open the Berkeley DB solution.</li> - <li>Ensure that the target configuration is Debug.</li> - <li>Right click the <span class="emphasis"><em>db_tcl</em></span> project in the Solution Explorer, and select <span class="emphasis"><em>Build</em></span>.</li> - <li>Right click the <span class="emphasis"><em>db_sql_testfixture</em></span> project in the Solution Explorer, and select <span class="emphasis"><em>Build</em></span>.</li> + <li> + Open the Berkeley DB solution. + </li> + <li> + Ensure that the target configuration is + Debug. + </li> + <li> + Right click the <span class="emphasis"><em>db_tcl</em></span> + project in the Solution Explorer, and select + <span class="emphasis"><em>Build</em></span>. + </li> + <li> + Right click the + <span class="emphasis"><em>db_sql_testfixture</em></span> + project in the Solution Explorer, and select + <span class="emphasis"><em>Build</em></span>. + </li> </ol> </div> - <p>To test extensions, specify the following in the <span class="emphasis"><em>Preprocessor Definitions</em></span> of the <span class="emphasis"><em>db_sql_testfixture</em></span> project:</p> + <p> + To test extensions, specify the following in the + <span class="emphasis"><em>Preprocessor Definitions</em></span> of + the <span class="emphasis"><em>db_sql_testfixture</em></span> project: + </p> <div class="itemizedlist"> <ul type="disc"> - <li><code class="literal">SQLITE_ENABLE_FTS3</code> to enable the full text search layer</li> - <li><code class="literal">SQLITE_ENABLE_RTREE</code> to enable the R-Tree layer</li> + <li><code class="literal"> + SQLITE_ENABLE_FTS3</code> to enable + the full text search layer + </li> + <li><code class="literal"> + SQLITE_ENABLE_RTREE</code> to enable + the R-Tree layer + </li> </ul> </div> </div> @@ -163,7 +283,8 @@ information.</p> <td width="40%" align="right"> <a accesskey="n" href="build_win_notes.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Building a small memory footprint library </td> + <td width="40%" align="left" valign="top">Building a small memory + footprint library </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/build_wince.html b/docs/installation/build_wince.html index b37a49cc..32056ed6 100644 --- a/docs/installation/build_wince.html +++ b/docs/installation/build_wince.html @@ -14,13 +14,11 @@ <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 6. - Building Berkeley DB for Windows Mobile - </th> + <th colspan="3" align="center">Chapter 6. Building Berkeley DB for Windows Mobile </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_win_faq.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="build_wince"></a>Chapter 6. - Building Berkeley DB for Windows Mobile - </h2> + <h2 class="title"><a id="build_wince"></a>Chapter 6. Building Berkeley DB for Windows Mobile </h2> </div> </div> </div> @@ -47,24 +43,25 @@ <dl> <dt> <span class="sect1"> - <a href="build_wince.html#build_wince_intro">Building for Windows Mobile</a> + <a href="build_wince.html#build_wince_intro">Building for Windows + Mobile</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> - <a href="build_wince.html#idm516512">Building Berkeley DB for Windows Mobile</a> + <a href="build_wince.html#idp475008">Building Berkeley DB for Windows Mobile</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_wince.html#idp180744">Changing Build Configuration Type</a> + <a href="build_wince.html#idp520696">Changing Build Configuration Type</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_wince.html#idp156256">Building Berkeley DB for different target platforms</a> + <a href="build_wince.html#build_wince_intro.add_platform">Building Berkeley DB for different target platforms</a> </span> </dt> </dl> @@ -79,13 +76,39 @@ <a href="build_wince_faq.html">Windows Mobile FAQ</a> </span> </dt> + <dt> + <span class="sect1"> + <a href="build_winec_intro.html">Building for Windows + Embedded Compact 7</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="build_winec_intro.html#idp578472">Building Berkeley DB for Windows Embedded Compact 7</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_winec_intro.html#idp570016">Changing Build Configuration Type</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_winec_intro.html#idp588240">Troubleshooting Common Build Errors</a> + </span> + </dt> + </dl> + </dd> </dl> </div> <div class="sect1" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="build_wince_intro"></a>Building for Windows Mobile</h2> + <h2 class="title" style="clear: both"><a id="build_wince_intro"></a>Building for Windows + Mobile</h2> </div> </div> </div> @@ -93,25 +116,31 @@ <dl> <dt> <span class="sect2"> - <a href="build_wince.html#idm516512">Building Berkeley DB for Windows Mobile</a> + <a href="build_wince.html#idp475008">Building Berkeley DB for Windows Mobile</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_wince.html#idp180744">Changing Build Configuration Type</a> + <a href="build_wince.html#idp520696">Changing Build Configuration Type</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_wince.html#idp156256">Building Berkeley DB for different target platforms</a> + <a href="build_wince.html#build_wince_intro.add_platform">Building Berkeley DB for different target platforms</a> </span> </dt> </dl> </div> - <p>This page contains general instructions on building Berkeley DB for -Windows Mobile platforms using specific compilers.</p> - <p>The <code class="filename">build_wince</code> directory in the Berkeley DB distribution contains -project files for Microsoft Visual 2005 with the Mobile SDK installed:</p> + <p> + This page contains general instructions on building Berkeley + DB for Windows Mobile platforms using specific + compilers. + </p> + <p> + The <code class="filename">build_wince</code> directory in the + Berkeley DB distribution contains project files for Microsoft + Visual 2005 with the Mobile SDK installed: + </p> <div class="informaltable"> <table border="1" width="80%"> <colgroup> @@ -127,21 +156,26 @@ project files for Microsoft Visual 2005 with the Mobile SDK installed:</p> <tbody> <tr> <td align="center">Berkeley_DB.sln</td> - <td align="center">Visual Studio 2005 solution</td> + <td align="center">Visual Studio 2005 + solution</td> </tr> <tr> <td align="center">*.vcproj</td> - <td align="center">Visual Studio 2005 project files</td> + <td align="center">Visual Studio 2005 project + files</td> </tr> </tbody> </table> </div> - <p>These project files can be used to build Berkeley DB for the Windows Mobile platform.</p> + <p> + These project files can be used to build Berkeley DB for the + Windows Mobile platform. + </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm516512"></a>Building Berkeley DB for Windows Mobile</h3> + <h3 class="title"><a id="idp475008"></a>Building Berkeley DB for Windows Mobile</h3> </div> </div> </div> @@ -149,17 +183,26 @@ project files for Microsoft Visual 2005 with the Mobile SDK installed:</p> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp144872"></a>Visual Studio 2005</h4> + <h4 class="title"><a id="idp456008"></a>Visual Studio 2005</h4> </div> </div> </div> <div class="orderedlist"> <ol type="1"> - <li>Choose <span class="emphasis"><em>File -> Open Workspace...</em></span>. -Navigate to the <code class="filename">build_wince</code> directory, select <code class="filename">Berkeley_DB</code> -and click <code class="literal">Open</code>.</li> - <li>Select the desired target platform from the platform drop-down menu.</li> - <li>Build the desired projects.</li> + <li> + Choose <span class="emphasis"><em>File -> Open + Workspace...</em></span>. Navigate to the + <code class="filename">build_wince</code> directory, + select <code class="filename">Berkeley_DB</code> and click + <code class="literal">Open</code>. + </li> + <li> + Select the desired target platform from the + platform drop-down menu. + </li> + <li> + Build the desired projects. + </li> </ol> </div> </div> @@ -167,13 +210,14 @@ and click <code class="literal">Open</code>.</li> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp184624"></a>Build results</h4> + <h4 class="title"><a id="idp524896"></a>Build results</h4> </div> </div> </div> - <p>The results of your build will be placed in any one of the following Berkeley DB subdirectories, -depending on the configuration that you chose: -</p> + <p> + The results of your build will be placed in any one + of the following Berkeley DB subdirectories, depending + on the configuration that you chose: </p> <table class="simplelist" border="0" summary="Simple list"> <tr> <td> @@ -197,31 +241,39 @@ depending on the configuration that you chose: </tr> </table> <p> -</p> - <p>When building your application during development, you must -link against -<code class="filename">libdb_small53sd.lib</code> or against <code class="filename">libdb_sql53sd.lib</code> for SQL features. You can -also build using a release version of the Berkeley DB libraries and tools, -which will be placed in the -<code class="filename">build_wince\(Platform)\Release_static </code>directory. -You must add the <code class="filename">build_wince</code> directory to the list -of include directories of your application's project, or copy the Berkeley DB -include files to a location in your Visual Studio include path.</p> + </p> + <p> + When building your application during development, + you must link against + <code class="filename">libdb_small61sd.lib</code> + or against + <code class="filename">libdb_sql61sd.lib</code> + for SQL features. You can also build using a release + version of the Berkeley DB libraries and tools, which + will be placed in the + <code class="filename">build_wince\(Platform)\Release_static + </code>directory. You must add the + <code class="filename">build_wince</code> directory to the + list of include directories of your application's + project, or copy the Berkeley DB include files to a + location in your Visual Studio include path. + </p> </div> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp180744"></a>Changing Build Configuration Type</h3> + <h3 class="title"><a id="idp520696"></a>Changing Build Configuration Type</h3> </div> </div> </div> - <p> -This section contains information on how to change between a dynamic -library (.dll) and static library (.lib). The library projects and their default -output and configuration in the Release build is as follows: -</p> + <p> + This section contains information on how to change + between a dynamic library (.dll) and static library + (.lib). The library projects and their default output and + configuration in the Release build is as follows: + </p> <div class="informaltable"> <table border="1" width="80%"> <colgroup> @@ -233,107 +285,131 @@ output and configuration in the Release build is as follows: <tr> <th align="center">Project</th> <th align="center">Default Output</th> - <th align="center">Default Configuration</th> + <th align="center">Default + Configuration</th> </tr> </thead> <tbody> <tr> <td align="center">db_small_static</td> - <td align="center">libdb_small53s.lib</td> + <td align="center">libdb_small61s.lib</td> <td align="center">Static Library</td> </tr> <tr> <td align="center">db_static</td> - <td align="center">libdb53s.lib</td> + <td align="center">libdb61s.lib</td> <td align="center">Static Library</td> </tr> <tr> <td align="center">db_sql</td> - <td align="center">libdb_sql53.dll</td> + <td align="center">libdb_sql61.dll</td> <td align="center">Dynamic Library</td> </tr> <tr> <td align="center">db_sql_static</td> - <td align="center">libdb_sql53s.lib</td> + <td align="center">libdb_sql61s.lib</td> <td align="center">Static Library</td> </tr> </tbody> </table> </div> <p> -To change a project configuration type in Visual Studio 2005, select a -project and do the following: -</p> + To change a project configuration type in Visual Studio + 2005, select a project and do the following: + </p> <div class="orderedlist"> <ol type="1"> - <li>Choose <span class="emphasis"><em>Project</em></span>-><span class="emphasis"><em>Properties</em></span> and navigate to <code class="literal">Configuration Properties.</code></li> - <li>Under <code class="literal">Project Defaults</code>, change the <code class="literal">Configuration Type</code> to your desired type.</li> + <li> + Choose + <span class="emphasis"><em>Project</em></span>-><span class="emphasis"><em>Properties</em></span> + and navigate to <code class="literal">Configuration + Properties.</code></li> + <li> + Under <code class="literal">Project Defaults</code>, + change the <code class="literal">Configuration Type</code> to + your desired type. + </li> </ol> </div> - <p>Note: After this change, the output file names change to the Visual Studio 2005 defaults based on the project name.</p> + <p> + Note: After this change, the output file names change to + the Visual Studio 2005 defaults based on the project + name. + </p> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp156256"></a>Building Berkeley DB for different target platforms</h3> + <h3 class="title"><a id="build_wince_intro.add_platform"></a>Building Berkeley DB for different target platforms</h3> </div> </div> </div> + <p> + There are many possible target CPU architectures for a + Windows Mobile application. This section outlines the + process required to add a new target architecture to the + project files supplied with Berkeley DB. + </p> + <p> + The Visual Studio 2005 project files will by default + build for Pocket PC 2003 and Smartphone 2003, and Windows + Mobile 6.5.3 Professional. If you want to build for other + platforms such as Windows Mobile 6.0, 6.1, or 6.5, you + need to follow the steps provided in this section. + </p> <p> - There are many possible target CPU architectures for a Windows - Mobile application. This section outlines the process required to - add a new target architecture to the project files supplied with - Berkeley DB. - </p> - <p> - The Visual Studio 2005 project files will by default build for - Pocket PC 2003 and Smartphone 2003, and Windows Mobile 6.5.3 Professional. If you want to - build for other platforms such as Windows Mobile 6.0, 6.1, or 6.5, you need to follow the steps provided in this section. - </p> - <p> - Different target architectures are available in different Platform - SDK or DTK downloads from Microsoft. The appropriate SDK must be installed - for your mobile architecture before you can build for that - platform. You can find the downloads at the <a class="ulink" href=" http://msdn.microsoft.com/en-us/windowsmobile/default.aspx" target="_top">Microsoft Developer Center</a> page. - </p> + Different target architectures are available in + different Platform SDK or DTK downloads from Microsoft. + The appropriate SDK must be installed for your mobile + architecture before you can build for that platform. You + can find the downloads at the <a class="ulink" href=" http://msdn.microsoft.com/en-us/windowsmobile/default.aspx" target="_top"> + Microsoft Developer Center</a> page. + </p> <div class="sect3" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp191952"></a>Visual Studio 2005</h4> + <h4 class="title"><a id="idp532440"></a>Visual Studio 2005</h4> </div> </div> </div> <div class="orderedlist"> <ol type="1"> <li> - Choose <span class="emphasis"><em>File -> Open Workspace...</em></span>. - Navigate to the <code class="filename">build_wince</code> directory, - select <code class="filename">Berkeley_DB</code> and click Open. - </li> - <li> - From the <code class="literal">Solution explorer</code> window, - right-click the <code class="literal">Solution Berkeley_DB</code> and - select <code class="literal">Configuration manager...</code></li> - <li> - In the <code class="literal">Active solution platform:</code> drop - down box select <code class="literal">New...</code></li> - <li> - From the <code class="literal">Type or select the new platform</code> - drop-down box, select a configuration from the ones - available and click <code class="literal">OK.</code></li> + Choose <span class="emphasis"><em>File -> Open + Workspace...</em></span>. Navigate to the + <code class="filename">build_wince</code> directory, + select <code class="filename">Berkeley_DB</code> and click + Open. + </li> <li> - Click <code class="literal">Close</code> from the - <code class="literal">Configuration Manager</code> dialog box. - </li> + From the <code class="literal">Solution + explorer</code> window, right-click the + <code class="literal">Solution Berkeley_DB</code> and + select <code class="literal">Configuration manager...</code></li> + <li> + In the <code class="literal">Active solution + platform:</code> drop down box select + <code class="literal">New...</code></li> + <li> + From the <code class="literal">Type or select the new + platform</code> drop-down box, select a + configuration from the ones available and click + <code class="literal">OK.</code></li> <li> - The target platform drop-down now contains the platform - just added. - </li> + Click <code class="literal">Close</code> from the + <code class="literal">Configuration Manager</code> + dialog box. + </li> <li> - Build as per the instructions given at the beginning of this chapter. - </li> + The target platform drop-down now contains + the platform just added. + </li> + <li> + Build as per the instructions given at the + beginning of this chapter. + </li> </ol> </div> </div> @@ -341,18 +417,34 @@ project and do the following: <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp198816"></a>BDB SQL Notes</h4> + <h4 class="title"><a id="idp502048"></a>BDB SQL Notes</h4> </div> </div> </div> <p> - After building for a different platform, change the deployment remote directory for the <code class="literal">db_sql</code> project to run the <code class="literal">wce_sql</code> sample application: - </p> + After building for a different platform, change the + deployment remote directory for the + <code class="literal">db_sql</code> project to run the + <code class="literal">wce_sql</code> sample application: + </p> <div class="orderedlist"> <ol type="1"> - <li>Select <code class="literal">db_sql</code> from the <code class="literal">Solution explorer</code> window.</li> - <li>Choose <span class="emphasis"><em>Project->Properties</em></span> and navigate to <code class="literal">Configuration Properties</code>.</li> - <li>Under <code class="literal">Deployment</code>, change the remote directory to <code class="literal">%CSIDL_PROGRAM_FILES%\wce_sql</code>.</li> + <li> + Select <code class="literal">db_sql</code> from the + <code class="literal">Solution explorer</code> + window. + </li> + <li> + Choose + <span class="emphasis"><em>Project->Properties</em></span> and + navigate to <code class="literal">Configuration + Properties</code>. + </li> + <li> + Under <code class="literal">Deployment</code>, change + the remote directory to + <code class="literal">%CSIDL_PROGRAM_FILES%\wce_sql</code>. + </li> </ol> </div> </div> diff --git a/docs/installation/build_wince_faq.html b/docs/installation/build_wince_faq.html index e5f64528..c22b356e 100644 --- a/docs/installation/build_wince_faq.html +++ b/docs/installation/build_wince_faq.html @@ -9,12 +9,12 @@ <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> <link rel="up" href="build_wince.html" title="Chapter 6. Building Berkeley DB for Windows Mobile" /> <link rel="prev" href="build_wince_notes.html" title="Windows Mobile notes" /> - <link rel="next" href="build_unix.html" title="Chapter 7. Building Berkeley DB for UNIX/POSIX" /> + <link rel="next" href="build_winec_intro.html" title="Building for Windows Embedded Compact 7" /> </head> <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,10 +22,8 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_wince_notes.html">Prev</a> </td> - <th width="60%" align="center">Chapter 6. - Building Berkeley DB for Windows Mobile - </th> - <td width="20%" align="right"> <a accesskey="n" href="build_unix.html">Next</a></td> + <th width="60%" align="center">Chapter 6. Building Berkeley DB for Windows Mobile </th> + <td width="20%" align="right"> <a accesskey="n" href="build_winec_intro.html">Next</a></td> </tr> </table> <hr /> @@ -40,58 +38,178 @@ </div> <div class="orderedlist"> <ol type="1"> + <li><span class="bold"><strong>What if my Windows Mobile device + does not support SetFilePointer and/or + SetEndOfFile?</strong></span><p> + You can manually disable the truncate functionality + from the build. + </p><p> + Do that by opening the + <code class="filename">db-X.X.X/build_wince/db_config.h</code> + file, and change the line that reads + </p><pre class="programlisting">#define HAVE_FTRUCATE 1</pre> + to read + <pre class="programlisting">#undef HAVE_FTRUNCATE</pre><p> + Making this change disables <a href="../api_reference/C/dbcompact.html" class="olink">DB->compact()</a> for btree + databases. + </p></li> <li> <span class="bold"> - <strong>What if my Windows Mobile device does not support SetFilePointer and/or SetEndOfFile?</strong> + <strong>Why doesn't automatic log archiving work?</strong> </span> - <p>You can manually disable the truncate functionality from the build.</p> - <p>Do that by opening the <code class="filename">db-X.X.X/build_wince/db_config.h</code> file, and change the line that reads </p> - <pre class="programlisting">#define HAVE_FTRUCATE 1</pre> - <p> to read </p> - <pre class="programlisting">#undef HAVE_FTRUNCATE</pre> - <p>Making this change disables <a href="../api_reference/C/dbcompact.html" class="olink">DB->compact()</a> for btree databases.</p> + <p> + The Windows Mobile platform does not have a concept + of a working directory. This means that the + <a href="../api_reference/C/logarchive.html#archive_DB_ARCH_REMOVE" class="olink">DB_ARCH_REMOVE</a> and <a href="../api_reference/C/logarchive.html#archive_DB_ARCH_ABS" class="olink">DB_ARCH_ABS</a> flags do not work + properly within Windows Mobile, because they rely on + having a working directory. + </p> + <p> + To work around this issue, you can call log_archive + with the <a href="../api_reference/C/logarchive.html#archive_DB_ARCH_LOG" class="olink">DB_ARCH_LOG</a> flag, the list of returned file + handles will not contain absolute paths. Your + application can take this list of files, construct + absolute paths, and delete the files. + </p> </li> <li> <span class="bold"> - <strong>Why doesn't automatic log archiving work?</strong> + <strong>Does Berkeley DB support Windows Mobile?</strong> </span> - <p>The Windows Mobile platform does not have a concept of a working directory. This means that the <a href="../api_reference/C/logarchive.html#archive_DB_ARCH_REMOVE" class="olink">DB_ARCH_REMOVE</a> and <a href="../api_reference/C/logarchive.html#archive_DB_ARCH_ABS" class="olink">DB_ARCH_ABS</a> flags do not work properly within Windows Mobile, because they rely on having a working directory.</p> - <p> To work around this issue, you can call log_archive with the <a href="../api_reference/C/logarchive.html#archive_DB_ARCH_LOG" class="olink">DB_ARCH_LOG</a> flag, the list of returned file handles will not contain absolute paths. Your application can take this list of files, construct absolute paths, and delete the files.</p> + <p> + Yes. + </p> + <p> + Berkeley DB relies on a subset of the Windows API, + and some standard C library APIs. These are provided + by Windows CE. Windows Mobile is built "on top" of + Windows CE. + </p> </li> <li> <span class="bold"> - <strong>Does Berkeley DB support Windows Mobile?</strong> + <strong>Does Berkeley DB support Windows CE?</strong> </span> <p>Yes. </p> - <p>Berkeley DB relies on a subset of the Windows API, and some standard C library APIs. These are provided by Windows CE. Windows Mobile is built "on top" of Windows CE.</p> + <p> + Berkeley DB relies on a subset of the Windows API, + and some standard C library APIs. These are provided + by Windows CE. + </p> </li> <li> <span class="bold"> - <strong>Does Berkeley DB support Windows CE?</strong> + <strong>Does Berkeley DB support Windows Embedded + Compact 7?</strong> </span> <p>Yes. </p> - <p>Berkeley DB relies on a subset of the Windows API, and some standard C library APIs. These are provided by Windows CE.</p> + <p> + Starting from release 12.1.6.1, it is possible to build Berkeley DB + on Windows Embedded Compact 7. Below are tips for the build process: + </p> + <div class="orderedlist"> + <ol type="a"> + <li> + <span class="emphasis"> + <em>Compile error at line 146 in stdlib.h</em> + </span> + <p> + This is a known bug for the Windows Embedded Compact 7 SDK. + A workaround is to change the line 146 in stdlib.h to read: + </p> + <pre class="programlisting">__checkReturn __bcount(_Size) void * __cdecl _alloca(__in size_t +_Size);</pre> + </li> + <li> + <span class="emphasis"> + <em>error LNK2019: unresolved external symbol _localtime_s referenced in function _osLocaltime</em> + </span> + <p> + This link error is caused by the fact that the Windows + Embedded Compact 7 runtime used to link Berkeley DB does not + provide the localtime_s() function. A workaround is to add + </p> + <pre class="programlisting">HAVE_LOCALTIME_S=0</pre> + <p> + to the proprocessor definitions of the db_sql project. This + can be done by right clicking the db_sql project, select + Properties->Configuration Properties->C/C++->Preprocessor->Proprocessor Definitions, + and append </p> + <pre class="programlisting">HAVE_LOCALTIME_S=0</pre> + <p> + at the end of the list. + </p> + </li> + <li> + <span class="emphasis"> + <em>error LNK1221: a subsystem can't be inferred and must be defined</em> + </span> + <p> + This link error happens on Visual Studio 2008, because it + cannot understand the subsystem configured for Visual + Studio 2005. To fix this error, right click the project + reporting this link error, select Properties->Configuration Properties-> + Linker->System->SubSystem, and change the value to WindowsCE (/SUBSYSTEM:WINDOWSCE). + </p> + </li> + <li> + <span class="emphasis"> + <em>warning C4996: 'xxx': This function or variable may be unsafe.</em> + </span> + <p> + Used within the Berkeley DB source tree, these functions are actually safe. + You can safely ignore these warnings. + </p> + </li> + </ol> + </div> </li> <li> <span class="bold"> - <strong>What platforms are the supplied sample applications designed for?</strong> + <strong>What platforms are the supplied + sample applications designed for?</strong> </span> - <p>The supplied sample applications were developed for the Pocket PC 2003 emulator. They are known to work on real pocket PC devices and later versions of the emulator as well.</p> - <p>The supplied applications are not designed to work with Smartphone devices. The screen size and input mechanisms are not compatible.</p> + <p> + The supplied sample applications were developed for + the Pocket PC 2003 emulator. They are known to work on + real pocket PC devices and later versions of the + emulator as well. + </p> + <p> + The supplied applications are not designed to work + with Smartphone devices. The screen size and input + mechanisms are not compatible. + </p> </li> <li> <span class="bold"> - <strong>I see a file mapping error when opening a Berkeley DB environment or database. What is wrong?</strong> + <strong>I see a file mapping error when + opening a Berkeley DB environment or database. What is + wrong?</strong> </span> - <p>The default behavior of Berkeley DB is to use memory mapped files in the environment. Windows Mobile does not allow memory mapped files to be created on flash storage.</p> - <p>There are two workarounds:</p> + <p> + The default behavior of Berkeley DB is to use memory + mapped files in the environment. Windows Mobile does + not allow memory mapped files to be created on flash + storage. + </p> + <p> + There are two workarounds: + </p> <div class="orderedlist"> <ol type="a"> <li> - Configure the Berkeley DB environment not to use memory mapped files. The options are discussed in detail in - <a href="../programmer_reference/env_region.html" class="olink">Shared memory region</a>. - </li> - <li>Create the Berkeley DB environment on non-flash storage. It is possible to store database and log files in a different location to using the <a href="../api_reference/C/envset_data_dir.html" class="olink">DB_ENV->set_data_dir()</a> and <a href="../api_reference/C/envset_lg_dir.html" class="olink">DB_ENV->set_lg_dir()</a> APIs.</li> + Configure the Berkeley DB environment not + to use memory mapped files. The options are + discussed in detail in <a href="../programmer_reference/env_region.html" class="olink">Shared memory region</a>. + </li> + <li> + Create the Berkeley DB environment on + non-flash storage. It is possible to store + database and log files in a different location to + using the <a href="../api_reference/C/envadd_data_dir.html" class="olink">DB_ENV->add_data_dir()</a> and <a href="../api_reference/C/envset_lg_dir.html" class="olink">DB_ENV->set_lg_dir()</a> + APIs. + </li> </ol> </div> </li> @@ -106,16 +224,15 @@ <td width="20%" align="center"> <a accesskey="u" href="build_wince.html">Up</a> </td> - <td width="40%" align="right"> <a accesskey="n" href="build_unix.html">Next</a></td> + <td width="40%" align="right"> <a accesskey="n" href="build_winec_intro.html">Next</a></td> </tr> <tr> <td width="40%" align="left" valign="top">Windows Mobile notes </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 7. - Building Berkeley DB for UNIX/POSIX - </td> + <td width="40%" align="right" valign="top"> Building for Windows + Embedded Compact 7</td> </tr> </table> </div> diff --git a/docs/installation/build_wince_notes.html b/docs/installation/build_wince_notes.html index 3115feb3..72fe29b3 100644 --- a/docs/installation/build_wince_notes.html +++ b/docs/installation/build_wince_notes.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="build_wince.html">Prev</a> </td> - <th width="60%" align="center">Chapter 6. - Building Berkeley DB for Windows Mobile - </th> + <th width="60%" align="center">Chapter 6. Building Berkeley DB for Windows Mobile </th> <td width="20%" align="right"> <a accesskey="n" href="build_wince_faq.html">Next</a></td> </tr> </table> @@ -40,14 +38,66 @@ </div> <div class="orderedlist"> <ol type="1"> - <li>The C++ API is not supported on Windows Mobile. The file stream and -exception handling functionality provided by the Berkeley DB C++ API are not -supported by Windows Mobile. It is possible to build a C++ application -against the Berkeley DB C API.</li> - <li>The Java API is not currently supported on Windows Mobile.</li> - <li>Tcl support is not currently supported on Windows Mobile.</li> - <li>Berkeley DB is shipped with support for the Pocket PC 2003 and Smartphone 2003 target platforms. It is possible to build Berkeley DB for different target platforms using Visual Studio's Configuration Manager. -<p>This can be done using the following steps:</p><div class="orderedlist"><ol type="a"><li>Open Visual Studio, and load the <code class="filename">build_wince/Berkeley_DB.sln</code> solution file.</li><li>Select the <span class="emphasis"><em>Build->Configuration Manager...</em></span> menu item.</li><li>In the <span class="emphasis"><em>Active Solution Platform...</em></span> dropdown, select <span class="emphasis"><em>New...</em></span></li><li>Select the desired target platform (you must have the desired Microsoft Platform SDK installed for it to appear in the list). Choose to copy settings from either the Pocket PC 2003 or Smartphone 2003 platforms.</li></ol></div><p>Before building the wce_tpcb sample application for the new platform, you will need to complete the following steps:</p><div class="orderedlist"><ol type="a"><li>Open the project properties page for wce_tpcb. Do this by: Right click <span class="emphasis"><em>wce_tpcb</em></span> in the <span class="emphasis"><em>Solution Explorer</em></span> then select <span class="emphasis"><em>Properties</em></span></li><li>Select <span class="emphasis"><em>Configuration Properties->Linker->Input</em></span></li><li>Remove <code class="filename">secchk.lib</code> and <code class="filename">crtti.lib</code> from the <span class="emphasis"><em>Additional Dependencies</em></span> field.</li></ol></div><p>NOTE: These steps are based on Visual Studio 2005, and might vary slightly depending on which version of Visual Studio being used.</p></li> + <li> + The C++ API is not supported on Windows Mobile. The + file stream and exception handling functionality provided + by the Berkeley DB C++ API are not supported by Windows + Mobile. It is possible to build a C++ application against + the Berkeley DB C API. + </li> + <li> + The Java API is not currently supported on Windows + Mobile. + </li> + <li> + Tcl support is not currently supported on Windows + Mobile. + </li> + <li> + Berkeley DB is shipped with support for the Pocket + PC 2003 and Smartphone 2003 target platforms. It is + possible to build Berkeley DB for different target + platforms using Visual Studio's Configuration Manager. + <p> + This can be done using the following + steps: + </p><div class="orderedlist"><ol type="a"><li> + Open Visual Studio, and load the + <code class="filename">build_wince/Berkeley_DB.sln</code> + solution file. + </li><li> + Select the <span class="emphasis"><em>Build->Configuration + Manager...</em></span> menu item. + </li><li> + In the <span class="emphasis"><em>Active Solution + Platform...</em></span> dropdown, select + <span class="emphasis"><em>New...</em></span></li><li> + Select the desired target platform (you must + have the desired Microsoft Platform SDK installed + for it to appear in the list). Choose to copy + settings from either the Pocket PC 2003 or + Smartphone 2003 platforms. + </li></ol></div><p> + Before building the wce_tpcb sample application for + the new platform, you will need to complete the + following steps: + </p><div class="orderedlist"><ol type="a"><li> + Open the project properties page for + wce_tpcb. Do this by: Right click + <span class="emphasis"><em>wce_tpcb</em></span> in the + <span class="emphasis"><em>Solution Explorer</em></span> then + select <span class="emphasis"><em>Properties</em></span></li><li> + Select <span class="emphasis"><em>Configuration + Properties->Linker->Input</em></span></li><li> + Remove <code class="filename">secchk.lib</code> and + <code class="filename">crtti.lib</code> from the + <span class="emphasis"><em>Additional Dependencies</em></span> + field. + </li></ol></div><p> + NOTE: These steps are based on Visual Studio 2005, + and might vary slightly depending on which version of + Visual Studio being used. + </p></li> </ol> </div> </div> @@ -62,9 +112,7 @@ against the Berkeley DB C API.</li> <td width="40%" align="right"> <a accesskey="n" href="build_wince_faq.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 6. - Building Berkeley DB for Windows Mobile - </td> + <td width="40%" align="left" valign="top">Chapter 6. Building Berkeley DB for Windows Mobile </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/build_winec_intro.html b/docs/installation/build_winec_intro.html new file mode 100644 index 00000000..0911f0db --- /dev/null +++ b/docs/installation/build_winec_intro.html @@ -0,0 +1,355 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Building for Windows Embedded Compact 7</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="build_wince.html" title="Chapter 6. Building Berkeley DB for Windows Mobile" /> + <link rel="prev" href="build_wince_faq.html" title="Windows Mobile FAQ" /> + <link rel="next" href="build_unix.html" title="Chapter 7. Building Berkeley DB for UNIX/POSIX" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Building for Windows + Embedded Compact 7</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="build_wince_faq.html">Prev</a> </td> + <th width="60%" align="center">Chapter 6. Building Berkeley DB for Windows Mobile </th> + <td width="20%" align="right"> <a accesskey="n" href="build_unix.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="build_winec_intro"></a>Building for Windows + Embedded Compact 7</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="build_winec_intro.html#idp578472">Building Berkeley DB for Windows Embedded Compact 7</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_winec_intro.html#idp570016">Changing Build Configuration Type</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_winec_intro.html#idp588240">Troubleshooting Common Build Errors</a> + </span> + </dt> + </dl> + </div> + <p> + This page contains general instructions on building Berkeley + DB for Windows Embedded Compact 7 platforms using specific + compilers. + </p> + <p> + The <code class="filename">build_wince</code> directory in the + Berkeley DB distribution contains project files for Microsoft + Visual 2008 with the Windows Embedded Compact 7 installed: + </p> + <div class="informaltable"> + <table border="1" width="80%"> + <colgroup> + <col /> + <col /> + </colgroup> + <thead> + <tr> + <th align="center">Project File</th> + <th align="center">Description</th> + </tr> + </thead> + <tbody> + <tr> + <td align="center">Berkeley_DB.sln</td> + <td align="center">Visual Studio 2008 + solution</td> + </tr> + <tr> + <td align="center">*.vcproj</td> + <td align="center">Visual Studio 2008 project + files</td> + </tr> + </tbody> + </table> + </div> + <p> + These project files can be used to build Berkeley DB for the + Windows Embedded Compact 7 platform. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp578472"></a>Building Berkeley DB for Windows Embedded Compact 7</h3> + </div> + </div> + </div> + <div class="sect3" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h4 class="title"><a id="idp577440"></a>Visual Studio 2008</h4> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + Install + <a class="ulink" href="http://msdn.microsoft.com/en-US/library/gg154201(v=winembedded.70).aspx" target="_top">Windows Embedded Compact 7</a>, + and add it to + <a class="link" href="build_wince.html#build_wince_intro.add_platform" title="Building Berkeley DB for different target platforms">target platforms</a>. + </li> + <li> + Choose <span class="emphasis"><em>File -> Open + Project/Solution...</em></span>. Navigate to the + <code class="filename">build_wince</code> directory, + select <code class="filename">Berkeley_DB</code> and click + <code class="literal">Open</code>. Wait for the project conversion + to finish. + </li> + <li> + Select the desired target platform from the + platform drop-down menu. + </li> + <li> + Build the desired projects. + </li> + </ol> + </div> + </div> + <div class="sect3" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h4 class="title"><a id="idp584736"></a>Build results</h4> + </div> + </div> + </div> + <p> + The results of your build will be placed in any one + of the following Berkeley DB subdirectories, depending + on the configuration that you chose: </p> + <table class="simplelist" border="0" summary="Simple list"> + <tr> + <td> + <code class="filename">build_wince\(Platform)\Debug</code> + </td> + </tr> + <tr> + <td> + <code class="filename">build_wince\(Platform)\Release</code> + </td> + </tr> + <tr> + <td> + <code class="filename">build_wince\(Platform)\Debug_static</code> + </td> + </tr> + <tr> + <td> + <code class="filename">build_wince\(Platform)\Release_static</code> + </td> + </tr> + </table> + <p> + </p> + <p> + When building your application during development, + you must link against + <code class="filename">libdb_small61sd.lib</code> + or against + <code class="filename">libdb_sql61sd.lib</code> + for SQL features. You can also build using a release + version of the Berkeley DB libraries and tools, which + will be placed in the + <code class="filename">build_wince\(Platform)\Release_static + </code>directory. You must add the + <code class="filename">build_wince</code> directory to the + list of include directories of your application's + project, or copy the Berkeley DB include files to a + location in your Visual Studio include path. + </p> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp570016"></a>Changing Build Configuration Type</h3> + </div> + </div> + </div> + <p> + This section contains information on how to change + between a dynamic library (.dll) and static library + (.lib). The library projects and their default output and + configuration in the Release build is as follows: + </p> + <div class="informaltable"> + <table border="1" width="80%"> + <colgroup> + <col /> + <col /> + <col /> + </colgroup> + <thead> + <tr> + <th align="center">Project</th> + <th align="center">Default Output</th> + <th align="center">Default + Configuration</th> + </tr> + </thead> + <tbody> + <tr> + <td align="center">db_small</td> + <td align="center">libdb_small61s.lib</td> + <td align="center">Static Library</td> + </tr> + <tr> + <td align="center">db</td> + <td align="center">libdb61s.lib</td> + <td align="center">Static Library</td> + </tr> + <tr> + <td align="center">db_sql</td> + <td align="center">libdb_sql61.dll</td> + <td align="center">Dynamic Library</td> + </tr> + </tbody> + </table> + </div> + <p> + To change a project configuration type in Visual Studio + 2008, select a project and do the following: + </p> + <div class="orderedlist"> + <ol type="1"> + <li> + Choose + <span class="emphasis"><em>Project</em></span>-><span class="emphasis"><em>Properties</em></span> + and navigate to <code class="literal">Configuration + Properties.</code></li> + <li> + Under <code class="literal">Project Defaults</code>, + change the <code class="literal">Configuration Type</code> to + your desired type. + </li> + </ol> + </div> + <p> + Note: After this change, the output file names change to + the Visual Studio 2008 defaults based on the project + name. + </p> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp588240"></a>Troubleshooting Common Build Errors</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <span class="emphasis"> + <em>Compile error at line 146 in stdlib.h</em> + </span> + <p> + This is a known bug for the Windows Embedded Compact 7 SDK. + A workaround is to change the line 146 in stdlib.h to read: + </p> + <pre class="programlisting">__checkReturn __bcount(_Size) void * __cdecl _alloca(__in size_t +_Size);</pre> + </li> + <li> + <span class="emphasis"> + <em>error LNK2019: unresolved external symbol _localtime_s referenced in function _osLocaltime</em> + </span> + <p> + This link error is caused by the fact that the Windows + Embedded Compact 7 runtime used to link Berkeley DB does not + provide the localtime_s() function. A workaround is to add + </p> + <pre class="programlisting">HAVE_LOCALTIME_S=0</pre> + <p> + to the proprocessor definitions of the db_sql project. This + can be done by right click the db_sql project, select + Properties->Configuration Properties->C/C++->Preprocessor->Proprocessor Definitions, + and append </p> + <pre class="programlisting">HAVE_LOCALTIME_S=0</pre> + <p> + at the end of the list. + </p> + </li> + <li> + <span class="emphasis"> + <em>error LNK1221: a subsystem can't be inferred and must be defined</em> + </span> + <p> + This link error happens on Visual Studio 2008, because it + cannot understand the subsystem configured for Visual + Studio 2005. To fix this error, right click the project + reporting this link error, select Properties->Configuration Properties-> + Linker->System->SubSystem, and change the value to WindowsCE (/SUBSYSTEM:WINDOWSCE). + </p> + </li> + <li> + <span class="emphasis"> + <em>warning C4996: 'xxx': This function or variable may be unsafe.</em> + </span> + <p> + Used within the Berkeley DB source tree, these functions are actually safe. + You can safely ignore these warnings. + </p> + </li> + </ol> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="build_wince_faq.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="build_wince.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="build_unix.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Windows Mobile FAQ </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Chapter 7. Building Berkeley DB for UNIX/POSIX + </td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/ch01s02.html b/docs/installation/ch01s02.html index 6de2fbeb..57deba22 100644 --- a/docs/installation/ch01s02.html +++ b/docs/installation/ch01s02.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> @@ -32,124 +32,126 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="idm340960"></a>Supported Platforms</h2> + <h2 class="title" style="clear: both"><a id="idp57872"></a>Supported Platforms</h2> </div> </div> </div> - <p> - You can install Berkeley DB on the following platforms: - </p> + <p> + You can install Berkeley DB on the following platforms: + </p> <div class="itemizedlist"> <ul type="disc"> <li> - <p> - Most versions of Linux (x86-64 and x86) including: - </p> + <p> + Most versions of Linux (x86-64 and x86) + including: + </p> <div class="itemizedlist"> <ul type="circle"> <li> <p> - Oracle Linux 4, 5, and 6 - </p> + Oracle Linux 4, 5, and 6 + </p> </li> <li> - <p> - Red Hat - </p> + <p> + Red Hat + </p> </li> <li> - <p> - Ubuntu - </p> + <p> + Ubuntu + </p> </li> <li> - <p> - Wind River - </p> + <p> + Wind River + </p> </li> <li> - <p> - MontaVista Embedded Linux version 6.0 - </p> + <p> + MontaVista Embedded Linux version 6.0 + </p> </li> </ul> </div> </li> <li> - <p> - Oracle Solaris versions 9 and 10 on x86_64, x86, - and SPARC. - </p> + <p> + Oracle Solaris versions 9 and 10 on x86_64, + x86, and SPARC. + </p> </li> <li> <p> - FreeBSD - </p> + FreeBSD + </p> </li> <li> <p> - Microsoft Windows (x86-64 and x86). - </p> + Microsoft Windows (x86-64 and x86). + </p> <div class="itemizedlist"> <ul type="circle"> <li> - XP (SP2, SP3) - </li> - <li> - Vista - </li> - <li> - Windows 7 - </li> + XP (SP2, SP3) + </li> <li> - Server 2008 - </li> + Vista + </li> <li> - Windows Mobile (6.x) - </li> + Windows 7 + </li> + <li> + Server 2008 + </li> + <li> + Windows Mobile (6.x) + </li> </ul> </div> </li> <li> <p> - Apple Mac OS X 10.5 and 10.6. - </p> + Apple Mac OS X 10.5 and 10.6. + </p> </li> <li> <p> - IBM AIX version 5 and 6. - </p> + IBM AIX version 5 and 6. + </p> </li> <li> - <p> - VxWorks 6.x - </p> + <p> + VxWorks 6.x + </p> </li> <li> <p> - QNX Neutrino/POSIX version 6 - </p> + QNX Neutrino/POSIX version 6 + </p> </li> <li> <p> - Android - </p> + Android + </p> </li> <li> - <p> - Apple iOS (previously known as iPhone OS) - </p> + <p> + Apple iOS (previously known as iPhone OS) + </p> </li> </ul> </div> - <p> - Apart from those mentioned in the list above, you can install - Berkeley DB on most other systems which are POSIX-compliant. - When there is a need to run Berkeley DB on a platform that is - currently not supported, DB is distributed in source code form - that you can use as base source to port Berkeley DB to that - platform. For more information on porting to other platforms, - see the Berkeley DB Porting Guide. + <p> + Apart from those mentioned in the list above, you can + install Berkeley DB on most other systems which are + POSIX-compliant. When there is a need to run Berkeley DB + on a platform that is currently not supported, DB is + distributed in source code form that you can use as base + source to port Berkeley DB to that platform. For more + information on porting to other platforms, see the + Berkeley DB Porting Guide. </p> </div> <div class="navfooter"> @@ -167,9 +169,7 @@ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 2. - System Installation Notes - </td> + <td width="40%" align="right" valign="top"> Chapter 2. System Installation Notes </td> </tr> </table> </div> diff --git a/docs/installation/changelog_4_8.html b/docs/installation/changelog_4_8.html index 5af290a9..c568f0d6 100644 --- a/docs/installation/changelog_4_8.html +++ b/docs/installation/changelog_4_8.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> + <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> <link rel="prev" href="upgrade_4_8_disk.html" title="Upgrade Requirements" /> - <link rel="next" href="test.html" title="Chapter 14. Test Suite" /> + <link rel="next" href="test.html" title="Chapter 16. Test Suite" /> </head> <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,7 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="upgrade_4_8_disk.html">Prev</a> </td> - <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> + <th width="60%" align="center">Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> <td width="20%" align="right"> <a accesskey="n" href="test.html">Next</a></td> </tr> </table> @@ -40,183 +40,183 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp908504"> + <a href="changelog_4_8.html#idp1293368"> Changes between 4.8.26 and 4.8.28:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp853904"> + <a href="changelog_4_8.html#idp1497568"> Known bugs in 4.8 </a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp885088"> + <a href="changelog_4_8.html#idp1482176"> Changes between 4.8.24 and 4.8.26:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp907544"> + <a href="changelog_4_8.html#idp1475624"> Changes between 4.8.21 and 4.8.24:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp853432"> + <a href="changelog_4_8.html#idp1553248"> Changes between 4.7 and 4.8.21:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp944680"> + <a href="changelog_4_8.html#idp1542376"> Database or Log File On-Disk Format Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp875992"> + <a href="changelog_4_8.html#idp1323496"> New Features:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp945096"> + <a href="changelog_4_8.html#idp1471240"> Database Environment Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp953944"> + <a href="changelog_4_8.html#idp1552400"> Concurrent Data Store Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp954344"> + <a href="changelog_4_8.html#idp1552800"> General Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp964688"> + <a href="changelog_4_8.html#idp1562416"> Btree Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp962400"> + <a href="changelog_4_8.html#idp1560192"> Hash Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp972744"> + <a href="changelog_4_8.html#idp1570528"> Queue Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp973816"> + <a href="changelog_4_8.html#idp1478984"> Recno Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp959840"> + <a href="changelog_4_8.html#idp1558464"> C-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp964968"> + <a href="changelog_4_8.html#idp1562696"> C++-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp985536"> + <a href="changelog_4_8.html#idp1583472"> Java-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp978792"> + <a href="changelog_4_8.html#idp1577104"> Direct Persistence Layer (DPL), Bindings and Collections API:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp979064"> + <a href="changelog_4_8.html#idp1576792"> Tcl-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp991048"> + <a href="changelog_4_8.html#idp1588984"> RPC-specific Client/Server Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp992632"> + <a href="changelog_4_8.html#idp1576880"> Replication Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp988920"> + <a href="changelog_4_8.html#idp1586856"> XA Resource Manager Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp994464"> + <a href="changelog_4_8.html#idp1592504"> Locking Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp987808"> + <a href="changelog_4_8.html#idp1585688"> Logging Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1005064"> + <a href="changelog_4_8.html#idp1603104"> Memory Pool Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1005456"> + <a href="changelog_4_8.html#idp1592944"> Mutex Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp987512"> + <a href="changelog_4_8.html#idp1585392"> Test Suite Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp996512"> + <a href="changelog_4_8.html#idp1594608"> Transaction Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1018456"> + <a href="changelog_4_8.html#idp1588800"> Utility Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1020896"> + <a href="changelog_4_8.html#idp1618888"> Configuration, Documentation, Sample Application, Portability and Build Changes:</a> </span> </dt> @@ -226,7 +226,7 @@ Configuration, Documentation, Sample Application, Portability and Build Changes: <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp908504"></a> + <h3 class="title"><a id="idp1293368"></a> Changes between 4.8.26 and 4.8.28:</h3> </div> </div> @@ -258,7 +258,7 @@ Place more emphasis on single version and obsolete buffers. [#18114] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp853904"></a> + <h3 class="title"><a id="idp1497568"></a> Known bugs in 4.8 </h3> </div> </div> @@ -277,7 +277,7 @@ Sharing logs across mixed-endian systems does not work.[#18032] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp885088"></a> + <h3 class="title"><a id="idp1482176"></a> Changes between 4.8.24 and 4.8.26:</h3> </div> </div> @@ -351,7 +351,7 @@ Fixed a bug where gets fail if the DB_GET_BOTH_FLAG is specified in a hash, sort <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp907544"></a> + <h3 class="title"><a id="idp1475624"></a> Changes between 4.8.21 and 4.8.24:</h3> </div> </div> @@ -402,7 +402,7 @@ Fixed an incorrect representation of log system configuration info. [#17532] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp853432"></a> + <h3 class="title"><a id="idp1553248"></a> Changes between 4.7 and 4.8.21:</h3> </div> </div> @@ -412,7 +412,7 @@ Changes between 4.7 and 4.8.21:</h3> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp944680"></a> + <h3 class="title"><a id="idp1542376"></a> Database or Log File On-Disk Format Changes:</h3> </div> </div> @@ -431,7 +431,7 @@ The log file format changed in 4.8. <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp875992"></a> + <h3 class="title"><a id="idp1323496"></a> New Features:</h3> </div> </div> @@ -532,7 +532,7 @@ Berkeley DB now has the ability to compare two cursors for equality. [#16811] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp945096"></a> + <h3 class="title"><a id="idp1471240"></a> Database Environment Changes:</h3> </div> </div> @@ -559,7 +559,7 @@ Fixed a bug that could cause a trap if an environment open failed and failchk th <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp953944"></a> + <h3 class="title"><a id="idp1552400"></a> Concurrent Data Store Changes:</h3> </div> </div> @@ -572,7 +572,7 @@ None. <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp954344"></a> + <h3 class="title"><a id="idp1552800"></a> General Access Method Changes:</h3> </div> </div> @@ -670,7 +670,7 @@ DB_TRUNCATE flag. [#17191] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp964688"></a> + <h3 class="title"><a id="idp1562416"></a> Btree Access Method Changes:</h3> </div> </div> @@ -709,7 +709,7 @@ it rather than returning DB_KEYEXIST. [#16803] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp962400"></a> + <h3 class="title"><a id="idp1560192"></a> Hash Access Method Changes:</h3> </div> </div> @@ -737,7 +737,7 @@ Fixed a bug to now return the expected buffer size on a DB_BUFFER_SMALL conditio <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp972744"></a> + <h3 class="title"><a id="idp1570528"></a> Queue Access Method Changes:</h3> </div> </div> @@ -782,7 +782,7 @@ Added the DB_CONSUME flag to DB->del and DBC->del to force adjustment of t <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp973816"></a> + <h3 class="title"><a id="idp1478984"></a> Recno Access Method Changes:</h3> </div> </div> @@ -816,7 +816,7 @@ Fixed a bug to now disallow passing DB_DUP and DB_RECNUM together to __db_set_fl <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp959840"></a> + <h3 class="title"><a id="idp1558464"></a> C-specific API Changes:</h3> </div> </div> @@ -835,7 +835,7 @@ Add get functions for each set functions of DB and DB_ENV structures which didn' <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp964968"></a> + <h3 class="title"><a id="idp1562696"></a> C++-specific API Changes:</h3> </div> </div> @@ -867,7 +867,7 @@ Fixed a memory leak when using nested transactions.[#16956] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp985536"></a> + <h3 class="title"><a id="idp1583472"></a> Java-specific API Changes:</h3> </div> </div> @@ -908,7 +908,7 @@ Fixed a bug so that position(), limit() and capacity() of ByteBuffers are obeyed <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp978792"></a> + <h3 class="title"><a id="idp1577104"></a> Direct Persistence Layer (DPL), Bindings and Collections API:</h3> </div> @@ -1065,7 +1065,7 @@ javadoc. [#17233] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp979064"></a> + <h3 class="title"><a id="idp1576792"></a> Tcl-specific API Changes:</h3> </div> @@ -1087,7 +1087,7 @@ The mutex API is now available when using Tcl. [#16342] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp991048"></a> + <h3 class="title"><a id="idp1588984"></a> RPC-specific Client/Server Changes:</h3> </div> </div> @@ -1108,7 +1108,7 @@ RPC support has been removed from Berkeley DB. [#16785] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp992632"></a> + <h3 class="title"><a id="idp1576880"></a> Replication Changes:</h3> </div> </div> @@ -1338,7 +1338,7 @@ given was smaller than number of sites that actually exists. [#16825] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp988920"></a> + <h3 class="title"><a id="idp1586856"></a> XA Resource Manager Changes:</h3> </div> </div> @@ -1358,7 +1358,7 @@ The XA Resource Manager has been removed from Berkeley DB. [#6459] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp994464"></a> + <h3 class="title"><a id="idp1592504"></a> Locking Subsystem Changes:</h3> </div> </div> @@ -1417,7 +1417,7 @@ Fixed a bug so that DB_STAT_CLEAR now restores the value of st_partitions. [#167 <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp987808"></a> + <h3 class="title"><a id="idp1585688"></a> Logging Subsystem Changes:</h3> </div> </div> @@ -1457,7 +1457,7 @@ databases in that interim step. [#17203] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp1005064"></a> + <h3 class="title"><a id="idp1603104"></a> Memory Pool Subsystem Changes:</h3> </div> </div> @@ -1490,7 +1490,7 @@ Fixed a possible race condition between dirtying and freeing a buffer that could <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp1005456"></a> + <h3 class="title"><a id="idp1592944"></a> Mutex Subsystem Changes:</h3> </div> </div> @@ -1563,7 +1563,7 @@ or contact Oracle for support. [#17470] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp987512"></a> + <h3 class="title"><a id="idp1585392"></a> Test Suite Changes</h3> </div> </div> @@ -1647,7 +1647,7 @@ incoming messages to trigger rerequest. <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp996512"></a> + <h3 class="title"><a id="idp1594608"></a> Transaction Subsystem Changes:</h3> </div> </div> @@ -1695,7 +1695,7 @@ Fixed a mutex leak in some corner cases. [#16665] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp1018456"></a> + <h3 class="title"><a id="idp1588800"></a> Utility Changes:</h3> </div> </div> @@ -1745,7 +1745,7 @@ Fixed a bug that would cause db_hotbackup to fail if a database file was removed <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp1020896"></a> + <h3 class="title"><a id="idp1618888"></a> Configuration, Documentation, Sample Application, Portability and Build Changes:</h3> </div> </div> @@ -1872,9 +1872,7 @@ HP-UX 10 is no longer supported. <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 14. - Test Suite - </td> + <td width="40%" align="right" valign="top"> Chapter 16. Test Suite </td> </tr> </table> </div> diff --git a/docs/installation/changelog_5_0.html b/docs/installation/changelog_5_0.html index d60f19be..babd9c93 100644 --- a/docs/installation/changelog_5_0.html +++ b/docs/installation/changelog_5_0.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> <link rel="prev" href="build_unix_stacksize.html" title="Changing Stack Size" /> - <link rel="next" href="upgrade_4_8_toc.html" title="Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> + <link rel="next" href="upgrade_4_8_toc.html" title="Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> </head> <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="build_unix_stacksize.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </th> + <th width="60%" align="center">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_4_8_toc.html">Next</a></td> </tr> </table> @@ -42,22 +40,22 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp872512">Changes between 11.2.5.0.26 and 11.2.5.0.32</a> + <a href="changelog_5_0.html#idp1469256">Changes between 11.2.5.0.26 and 11.2.5.0.32</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp863208">Changes between 11.2.5.0.21 and 11.2.5.0.26</a> + <a href="changelog_5_0.html#idp1470160">Changes between 11.2.5.0.21 and 11.2.5.0.26</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp851296">Changes between 4.8 and 11.2.5.0.21</a> + <a href="changelog_5_0.html#idp1448240">Changes between 4.8 and 11.2.5.0.21</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp883672">Known Bugs</a> + <a href="changelog_5_0.html#idp1481264">Known Bugs</a> </span> </dt> </dl> @@ -66,7 +64,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp872512"></a>Changes between 11.2.5.0.26 and 11.2.5.0.32</h3> + <h3 class="title"><a id="idp1469256"></a>Changes between 11.2.5.0.26 and 11.2.5.0.32</h3> </div> </div> </div> @@ -209,7 +207,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp863208"></a>Changes between 11.2.5.0.21 and 11.2.5.0.26</h3> + <h3 class="title"><a id="idp1470160"></a>Changes between 11.2.5.0.21 and 11.2.5.0.26</h3> </div> </div> </div> @@ -302,7 +300,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp851296"></a>Changes between 4.8 and 11.2.5.0.21</h3> + <h3 class="title"><a id="idp1448240"></a>Changes between 4.8 and 11.2.5.0.21</h3> </div> </div> </div> @@ -310,7 +308,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp877680"></a>Database or Log File On-Disk Format Changes</h4> + <h4 class="title"><a id="idp1474872"></a>Database or Log File On-Disk Format Changes</h4> </div> </div> </div> @@ -328,7 +326,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp851384"></a>New Features</h4> + <h4 class="title"><a id="idp1448328"></a>New Features</h4> </div> </div> </div> @@ -441,7 +439,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp871480"></a>Database Environment Changes</h4> + <h4 class="title"><a id="idp1468224"></a>Database Environment Changes</h4> </div> </div> </div> @@ -469,7 +467,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp900736"></a>Access Method Changes</h4> + <h4 class="title"><a id="idp1498880"></a>Access Method Changes</h4> </div> </div> </div> @@ -567,7 +565,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp870128"></a>Locking Subsystem Changes</h4> + <h4 class="title"><a id="idp1499288"></a>Locking Subsystem Changes</h4> </div> </div> </div> @@ -595,7 +593,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp877248"></a>Logging Subsystem Changes</h4> + <h4 class="title"><a id="idp1474440"></a>Logging Subsystem Changes</h4> </div> </div> </div> @@ -613,7 +611,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp871544"></a>Memory Pool Subsystem Changes</h4> + <h4 class="title"><a id="idp1499352"></a>Memory Pool Subsystem Changes</h4> </div> </div> </div> @@ -661,7 +659,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp907016"></a>Mutex Subsystem Changes</h4> + <h4 class="title"><a id="idp1504680"></a>Mutex Subsystem Changes</h4> </div> </div> </div> @@ -689,7 +687,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp921280"></a>Tcl-specific API Changes</h4> + <h4 class="title"><a id="idp1458984"></a>Tcl-specific API Changes</h4> </div> </div> </div> @@ -707,7 +705,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp867472"></a>C#-specific API Changes</h4> + <h4 class="title"><a id="idp1468480"></a>C#-specific API Changes</h4> </div> </div> </div> @@ -730,7 +728,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp876680"></a>API Changes</h4> + <h4 class="title"><a id="idp1509528"></a>API Changes</h4> </div> </div> </div> @@ -753,7 +751,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp898112"></a>Replication Changes</h4> + <h4 class="title"><a id="idp1496312"></a>Replication Changes</h4> </div> </div> </div> @@ -861,7 +859,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp898496"></a>Transaction Subsystem Changes</h4> + <h4 class="title"><a id="idp1497376"></a>Transaction Subsystem Changes</h4> </div> </div> </div> @@ -889,7 +887,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp907896"></a>Utility Changes</h4> + <h4 class="title"><a id="idp1474288"></a>Utility Changes</h4> </div> </div> </div> @@ -927,7 +925,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp861848"></a>Example Changes</h4> + <h4 class="title"><a id="idp1525336"></a>Example Changes</h4> </div> </div> </div> @@ -975,7 +973,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp927552"></a>Deprecated Features</h4> + <h4 class="title"><a id="idp1464392"></a>Deprecated Features</h4> </div> </div> </div> @@ -993,7 +991,7 @@ <div class="titlepage"> <div> <div> - <h4 class="title"><a id="idp907336"></a>Configuration, Documentation, Sample Apps, Portability and Build Changes</h4> + <h4 class="title"><a id="idp1520392"></a>Configuration, Documentation, Sample Apps, Portability and Build Changes</h4> </div> </div> </div> @@ -1052,7 +1050,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp883672"></a>Known Bugs</h3> + <h3 class="title"><a id="idp1481264"></a>Known Bugs</h3> </div> </div> </div> @@ -1117,7 +1115,7 @@ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</td> + <td width="40%" align="right" valign="top"> Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</td> </tr> </table> </div> diff --git a/docs/installation/changelog_5_1.html b/docs/installation/changelog_5_1.html index aa222938..c6b92616 100644 --- a/docs/installation/changelog_5_1.html +++ b/docs/installation/changelog_5_1.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_51_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> + <link rel="up" href="upgrade_51_toc.html" title="Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> <link rel="prev" href="upgrade_11gr2_51_mod_db4_unsupp.html" title="Mod_db4 Support Discontinued" /> - <link rel="next" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="next" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> </head> <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="upgrade_11gr2_51_mod_db4_unsupp.html">Prev</a> </td> - <th width="60%" align="center">Chapter 11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </th> + <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_toc.html">Next</a></td> </tr> </table> @@ -42,122 +40,122 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp799888">Database or Log File On-Disk Format Changes</a> + <a href="changelog_5_1.html#idp1395416">Database or Log File On-Disk Format Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp792216">New Features</a> + <a href="changelog_5_1.html#idp1335544">New Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp787976">Database Environment Changes</a> + <a href="changelog_5_1.html#idp1322264">Database Environment Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp806432">Concurrent Data Store Changes</a> + <a href="changelog_5_1.html#idp1402240">Concurrent Data Store Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp727768">Access Method Changes</a> + <a href="changelog_5_1.html#idp1322352">Access Method Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp795776">API Changes</a> + <a href="changelog_5_1.html#idp1395912">API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp802264">SQL-Specific API Changes</a> + <a href="changelog_5_1.html#idp1398072">SQL-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp803624">Tcl-Specific API Changes</a> + <a href="changelog_5_1.html#idp1399432">Tcl-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp799176">Java-Specific API Changes</a> + <a href="changelog_5_1.html#idp1394704">Java-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp734296">C#-Specific API Changes</a> + <a href="changelog_5_1.html#idp1391096">C#-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp807320">Direct Persistence Layer (DPL), Bindings and Collections API</a> + <a href="changelog_5_1.html#idp1412856">Direct Persistence Layer (DPL), Bindings and Collections API</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp816672">Replication Changes</a> + <a href="changelog_5_1.html#idp1412472">Replication Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp827552">Locking Subsystem Changes</a> + <a href="changelog_5_1.html#idp1423304">Locking Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp839224">Logging Subsystem Changes</a> + <a href="changelog_5_1.html#idp1436016">Logging Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp822992">Memory Pool Subsystem Changes</a> + <a href="changelog_5_1.html#idp1418744">Memory Pool Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp827368">Mutex Subsystem Changes</a> + <a href="changelog_5_1.html#idp1423120">Mutex Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp836200">Transaction Subsystem Changes</a> + <a href="changelog_5_1.html#idp1431840">Transaction Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp813832">Test Suite Changes</a> + <a href="changelog_5_1.html#idp1409688">Test Suite Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp834616">Utility Changes</a> + <a href="changelog_5_1.html#idp1430312">Utility Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp837928">Configuration, Documentation, Sample Apps, Portability, and Build Changes</a> + <a href="changelog_5_1.html#idp1433952">Configuration, Documentation, Sample Apps, Portability, and Build Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp828192">Example Changes</a> + <a href="changelog_5_1.html#idp1423944">Example Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp848592">Miscellaneous Bug Fixes</a> + <a href="changelog_5_1.html#idp1445752">Miscellaneous Bug Fixes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp846464">Deprecated Features</a> + <a href="changelog_5_1.html#idp1443624">Deprecated Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp847112">Known Bugs</a> + <a href="changelog_5_1.html#idp1444272">Known Bugs</a> </span> </dt> </dl> @@ -171,7 +169,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp799888"></a>Database or Log File On-Disk Format Changes</h3> + <h3 class="title"><a id="idp1395416"></a>Database or Log File On-Disk Format Changes</h3> </div> </div> </div> @@ -194,7 +192,7 @@ The log file format was unchanged in 11gR2 library version 11.2.5.1. <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp792216"></a>New Features</h3> + <h3 class="title"><a id="idp1335544"></a>New Features</h3> </div> </div> </div> @@ -302,7 +300,7 @@ Added an encryption implementation to the SQL API [#18683] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp787976"></a>Database Environment Changes</h3> + <h3 class="title"><a id="idp1322264"></a>Database Environment Changes</h3> </div> </div> </div> @@ -335,7 +333,7 @@ Fixed a bug that could cause recovery to fail with the error "DB_LOGC->get: l <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp806432"></a>Concurrent Data Store Changes</h3> + <h3 class="title"><a id="idp1402240"></a>Concurrent Data Store Changes</h3> </div> </div> </div> @@ -353,7 +351,7 @@ None <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp727768"></a>Access Method Changes</h3> + <h3 class="title"><a id="idp1322352"></a>Access Method Changes</h3> </div> </div> </div> @@ -416,7 +414,7 @@ Fixed a bug that would return DB_NOTFOUND instead of DB_BUFFER_SMALL when the fi <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp795776"></a>API Changes</h3> + <h3 class="title"><a id="idp1395912"></a>API Changes</h3> </div> </div> </div> @@ -434,7 +432,7 @@ Fixed various items uncovered by extending DB_CONFIG support: [#18720] - Added <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp802264"></a>SQL-Specific API Changes</h3> + <h3 class="title"><a id="idp1398072"></a>SQL-Specific API Changes</h3> </div> </div> </div> @@ -502,7 +500,7 @@ Fixed a bug causing a segfault when releasing a savepoint that was already relea <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp803624"></a>Tcl-Specific API Changes</h3> + <h3 class="title"><a id="idp1399432"></a>Tcl-Specific API Changes</h3> </div> </div> </div> @@ -520,7 +518,7 @@ Changed to link tcl8.5 by default on Windows[#18244] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp799176"></a>Java-Specific API Changes</h3> + <h3 class="title"><a id="idp1394704"></a>Java-Specific API Changes</h3> </div> </div> </div> @@ -588,7 +586,7 @@ Added LEASE_TIMEOUT field to the ReplicationTimeoutType class that enables confi <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp734296"></a>C#-Specific API Changes</h3> + <h3 class="title"><a id="idp1391096"></a>C#-Specific API Changes</h3> </div> </div> </div> @@ -621,7 +619,7 @@ Fixed a bug that use leading to the error: "Transaction that opened the DB handl <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp807320"></a>Direct Persistence Layer (DPL), Bindings and Collections API</h3> + <h3 class="title"><a id="idp1412856"></a>Direct Persistence Layer (DPL), Bindings and Collections API</h3> </div> </div> </div> @@ -683,7 +681,7 @@ The following classes are now certified to be serializable. [#18738] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp816672"></a>Replication Changes</h3> + <h3 class="title"><a id="idp1412472"></a>Replication Changes</h3> </div> </div> </div> @@ -741,7 +739,7 @@ Fixed a bug which would cause failure if client env attempted to perform sync-up <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp827552"></a>Locking Subsystem Changes</h3> + <h3 class="title"><a id="idp1423304"></a>Locking Subsystem Changes</h3> </div> </div> </div> @@ -759,7 +757,7 @@ Moved the wait mutex from the lock structure to the locker structure, reducing t <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp839224"></a>Logging Subsystem Changes</h3> + <h3 class="title"><a id="idp1436016"></a>Logging Subsystem Changes</h3> </div> </div> </div> @@ -777,7 +775,7 @@ None. <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp822992"></a>Memory Pool Subsystem Changes</h3> + <h3 class="title"><a id="idp1418744"></a>Memory Pool Subsystem Changes</h3> </div> </div> </div> @@ -805,7 +803,7 @@ Changed memory pool allocation so that the EIO error is returned rather than the <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp827368"></a>Mutex Subsystem Changes</h3> + <h3 class="title"><a id="idp1423120"></a>Mutex Subsystem Changes</h3> </div> </div> </div> @@ -823,7 +821,7 @@ Fixed problems with the printed statistics for DB_MUTEX_SHARED latches. The DB_S <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp836200"></a>Transaction Subsystem Changes</h3> + <h3 class="title"><a id="idp1431840"></a>Transaction Subsystem Changes</h3> </div> </div> </div> @@ -846,7 +844,7 @@ Fix javadoc to note the exception to the rule that a transaction handle may not <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp813832"></a>Test Suite Changes</h3> + <h3 class="title"><a id="idp1409688"></a>Test Suite Changes</h3> </div> </div> </div> @@ -864,7 +862,7 @@ None. [#18831] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp834616"></a>Utility Changes</h3> + <h3 class="title"><a id="idp1430312"></a>Utility Changes</h3> </div> </div> </div> @@ -892,7 +890,7 @@ Fixed a bug in db_hotbackup that would cause a trap if the -D flag is used and t <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp837928"></a>Configuration, Documentation, Sample Apps, Portability, and Build Changes</h3> + <h3 class="title"><a id="idp1433952"></a>Configuration, Documentation, Sample Apps, Portability, and Build Changes</h3> </div> </div> </div> @@ -960,7 +958,7 @@ Upgraded Berkeley DB SQL to SQLite version 3.7.0 [#18857] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp828192"></a>Example Changes</h3> + <h3 class="title"><a id="idp1423944"></a>Example Changes</h3> </div> </div> </div> @@ -978,7 +976,7 @@ Renamed examples/c/bench_001 to examples/c/ex_bulk. [#18537] <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp848592"></a>Miscellaneous Bug Fixes</h3> + <h3 class="title"><a id="idp1445752"></a>Miscellaneous Bug Fixes</h3> </div> </div> </div> @@ -1011,7 +1009,7 @@ Fixed a bug which caused database verification to hang when verifying a database <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp846464"></a>Deprecated Features</h3> + <h3 class="title"><a id="idp1443624"></a>Deprecated Features</h3> </div> </div> </div> @@ -1029,7 +1027,7 @@ Fixed a bug which caused database verification to hang when verifying a database <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp847112"></a>Known Bugs</h3> + <h3 class="title"><a id="idp1444272"></a>Known Bugs</h3> </div> </div> </div> @@ -1059,9 +1057,7 @@ None <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </td> + <td width="40%" align="right" valign="top"> Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </td> </tr> </table> </div> diff --git a/docs/installation/changelog_5_2.html b/docs/installation/changelog_5_2.html index 49ed416d..41282543 100644 --- a/docs/installation/changelog_5_2.html +++ b/docs/installation/changelog_5_2.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_hot_backup.html" title="Hot Backup Changes" /> - <link rel="next" href="upgrade_51_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> + <link rel="next" href="upgrade_51_toc.html" title="Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> </head> <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="upgrade_11gr2_52_hot_backup.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_51_toc.html">Next</a></td> </tr> </table> @@ -42,112 +40,112 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp719568">Database or Log File On-Disk Format Changes</a> + <a href="changelog_5_2.html#idp1313480">Database or Log File On-Disk Format Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp725640">New Features</a> + <a href="changelog_5_2.html#idp1320448">New Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp731112">Database Environment Changes</a> + <a href="changelog_5_2.html#idp1304040">Database Environment Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp742672">Concurrent Data Store Changes</a> + <a href="changelog_5_2.html#idp1337840">Concurrent Data Store Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp736048">Access Method Changes</a> + <a href="changelog_5_2.html#idp1331240">Access Method Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp736464">SQL API Changes</a> + <a href="changelog_5_2.html#idp1319744">SQL API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp719112">C API Changes</a> + <a href="changelog_5_2.html#idp1312960">C API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp743448">Tcl-specific API Changes</a> + <a href="changelog_5_2.html#idp1338616">Tcl-specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp749040">C#-specific API Changes</a> + <a href="changelog_5_2.html#idp1313048">C#-specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp741376">Replication Changes</a> + <a href="changelog_5_2.html#idp1336544">Replication Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp743864">Locking Subsystem Changes</a> + <a href="changelog_5_2.html#idp1339000">Locking Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp749456">Logging Subsystem Changes</a> + <a href="changelog_5_2.html#idp1352672">Logging Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp763176">Memory Pool Subsystem Changes</a> + <a href="changelog_5_2.html#idp1334816">Memory Pool Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp765792">Mutex Subsystem Changes</a> + <a href="changelog_5_2.html#idp1360960">Mutex Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp766552">Transaction Subsystem Changes</a> + <a href="changelog_5_2.html#idp1353088">Transaction Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp763560">Test Suite Changes</a> + <a href="changelog_5_2.html#idp1345456">Test Suite Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp776568">Utility Changes</a> + <a href="changelog_5_2.html#idp1371840">Utility Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp766936">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> + <a href="changelog_5_2.html#idp1373456">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp780312">Example Changes</a> + <a href="changelog_5_2.html#idp1345232">Example Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp781208">Miscellaneous Bug Fixes</a> + <a href="changelog_5_2.html#idp1376368">Miscellaneous Bug Fixes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp782744">Deprecated Features</a> + <a href="changelog_5_2.html#idp1377904">Deprecated Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp785040">Known Bugs</a> + <a href="changelog_5_2.html#idp1379824">Known Bugs</a> </span> </dt> </dl> @@ -161,7 +159,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp719568"></a>Database or Log File On-Disk Format Changes</h3> + <h3 class="title"><a id="idp1313480"></a>Database or Log File On-Disk Format Changes</h3> </div> </div> </div> @@ -184,7 +182,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp725640"></a>New Features</h3> + <h3 class="title"><a id="idp1320448"></a>New Features</h3> </div> </div> </div> @@ -262,7 +260,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp731112"></a>Database Environment Changes</h3> + <h3 class="title"><a id="idp1304040"></a>Database Environment Changes</h3> </div> </div> </div> @@ -280,7 +278,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp742672"></a>Concurrent Data Store Changes</h3> + <h3 class="title"><a id="idp1337840"></a>Concurrent Data Store Changes</h3> </div> </div> </div> @@ -298,7 +296,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp736048"></a>Access Method Changes</h3> + <h3 class="title"><a id="idp1331240"></a>Access Method Changes</h3> </div> </div> </div> @@ -396,7 +394,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp736464"></a>SQL API Changes</h3> + <h3 class="title"><a id="idp1319744"></a>SQL API Changes</h3> </div> </div> </div> @@ -484,7 +482,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp719112"></a>C API Changes</h3> + <h3 class="title"><a id="idp1312960"></a>C API Changes</h3> </div> </div> </div> @@ -527,7 +525,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp743448"></a>Tcl-specific API Changes</h3> + <h3 class="title"><a id="idp1338616"></a>Tcl-specific API Changes</h3> </div> </div> </div> @@ -545,7 +543,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp749040"></a>C#-specific API Changes</h3> + <h3 class="title"><a id="idp1313048"></a>C#-specific API Changes</h3> </div> </div> </div> @@ -568,7 +566,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp741376"></a>Replication Changes</h3> + <h3 class="title"><a id="idp1336544"></a>Replication Changes</h3> </div> </div> </div> @@ -691,7 +689,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp743864"></a>Locking Subsystem Changes</h3> + <h3 class="title"><a id="idp1339000"></a>Locking Subsystem Changes</h3> </div> </div> </div> @@ -724,7 +722,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp749456"></a>Logging Subsystem Changes</h3> + <h3 class="title"><a id="idp1352672"></a>Logging Subsystem Changes</h3> </div> </div> </div> @@ -752,7 +750,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp763176"></a>Memory Pool Subsystem Changes</h3> + <h3 class="title"><a id="idp1334816"></a>Memory Pool Subsystem Changes</h3> </div> </div> </div> @@ -770,7 +768,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp765792"></a>Mutex Subsystem Changes</h3> + <h3 class="title"><a id="idp1360960"></a>Mutex Subsystem Changes</h3> </div> </div> </div> @@ -798,7 +796,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp766552"></a>Transaction Subsystem Changes</h3> + <h3 class="title"><a id="idp1353088"></a>Transaction Subsystem Changes</h3> </div> </div> </div> @@ -831,7 +829,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp763560"></a>Test Suite Changes</h3> + <h3 class="title"><a id="idp1345456"></a>Test Suite Changes</h3> </div> </div> </div> @@ -849,7 +847,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp776568"></a>Utility Changes</h3> + <h3 class="title"><a id="idp1371840"></a>Utility Changes</h3> </div> </div> </div> @@ -882,7 +880,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp766936"></a>Configuration, Documentation, Sample Apps, Portability and Build Changes</h3> + <h3 class="title"><a id="idp1373456"></a>Configuration, Documentation, Sample Apps, Portability and Build Changes</h3> </div> </div> </div> @@ -925,7 +923,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp780312"></a>Example Changes</h3> + <h3 class="title"><a id="idp1345232"></a>Example Changes</h3> </div> </div> </div> @@ -948,7 +946,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp781208"></a>Miscellaneous Bug Fixes</h3> + <h3 class="title"><a id="idp1376368"></a>Miscellaneous Bug Fixes</h3> </div> </div> </div> @@ -966,7 +964,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp782744"></a>Deprecated Features</h3> + <h3 class="title"><a id="idp1377904"></a>Deprecated Features</h3> </div> </div> </div> @@ -984,7 +982,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp785040"></a>Known Bugs</h3> + <h3 class="title"><a id="idp1379824"></a>Known Bugs</h3> </div> </div> </div> @@ -1039,9 +1037,7 @@ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </td> + <td width="40%" align="right" valign="top"> Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </td> </tr> </table> </div> diff --git a/docs/installation/changelog_5_3.html b/docs/installation/changelog_5_3.html index 279170da..399aa047 100644 --- a/docs/installation/changelog_5_3.html +++ b/docs/installation/changelog_5_3.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_xa_mvcc.html" title="Berkeley DB X/Open Compliant XA Resource Manager and Transaction Snapshots" /> - <link rel="next" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="next" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> </head> <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="upgrade_11gr2_53_xa_mvcc.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_52_toc.html">Next</a></td> </tr> </table> @@ -42,82 +40,77 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp594928">Changes between 11.2.5.3.15 and 11.2.5.3.21</a> + <a href="changelog_5_3.html#idp1207192">Database or Log File On-Disk Format Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp608376">Database or Log File On-Disk Format Changes</a> + <a href="changelog_5_3.html#idp1200256">New Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp590024">New Features</a> + <a href="changelog_5_3.html#idp1206088">Database Environment Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp594216">Database Environment Changes</a> + <a href="changelog_5_3.html#idp1211048">Access Method Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp607088">Access Method Changes</a> + <a href="changelog_5_3.html#idp1208744">SQL API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp616640">SQL API Changes</a> + <a href="changelog_5_3.html#idp1199152">Java-specific API changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp610088">Java-specific API changes</a> + <a href="changelog_5_3.html#idp1208832">Replication Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp616728">Replication Changes</a> + <a href="changelog_5_3.html#idp1199992">Locking Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp594560">Locking Subsystem Changes</a> + <a href="changelog_5_3.html#idp1217800">Logging Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp635880">Logging Subsystem Changes</a> + <a href="changelog_5_3.html#idp1209392">Memory Pool Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp625488">Memory Pool Subsystem Changes</a> + <a href="changelog_5_3.html#idp1226336">Mutex Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp632288">Mutex Subsystem Changes</a> + <a href="changelog_5_3.html#idp1218216">Transaction Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp636296">Transaction Subsystem Changes</a> + <a href="changelog_5_3.html#idp1231856">Utility Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp625872">Utility Changes</a> + <a href="changelog_5_3.html#idp1226152">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp632040">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> - </span> - </dt> - <dt> - <span class="sect2"> - <a href="changelog_5_3.html#idp641456">Known Bugs</a> + <a href="changelog_5_3.html#idp1235024">Known Bugs</a> </span> </dt> </dl> @@ -131,90 +124,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp594928"></a>Changes between 11.2.5.3.15 and 11.2.5.3.21</h3> - </div> - </div> - </div> - <div class="orderedlist"> - <ol type="1"> - <li> - <p> - Fixed incompatibility problems of Java DPL with JDK7, so DPL will now work with JDK7. [#20586] - </p> - </li> - <li> - <p> - Added a flag to allow database locking to be disabled from the SQL API. [#20928] - </p> - </li> - <li> - <p> - Fixed a bug that could allocate a heap data page in a region after the region creation has been undone. [#20939] - </p> - </li> - <li> - <p> - Redundant whitespaces are now ignored in DB_CONFIG lines pertaining to directories, e.g. set_data_dir. [#20158] - </p> - </li> - <li> - <p> - Fixed a bug that caused DB_ENV->backup to stop early if DB_BACKUP_FILES was not set and a non-DB file was in the data directory. [#21076] - </p> - </li> - <li> - <p> - Fixed a rare race condition that could cause a crash if two processes opened the same database at the same time. [#21041] - </p> - </li> - <li> - <p> - Fixed missing cross compiling capability for the JDBC driver. [#21101] - </p> - </li> - <li> - <p> - Allow the same system/machine to host both a master and a replica database through the use of relative pathnames. [#21105] - </p> - </li> - <li> - <p> - Fixed a bug in the Java API where EnvironmentConfig.setCreateDir would fail to configure the environment. [#21127] - </p> - </li> - <li> - <p> - Fixed an assert failure in btreeCompare when allocating memory in the wrong thread was causing a memory leak. [#21232] - </p> - </li> - <li> - <p> - Fixed a bug in the Java API where concurrent operations that change the database schema could lead to a hang. [#21265] - </p> - </li> - <li> - <p> - Added JDBC code to the code base and updated the windows build files to include the JDBC solution. [#21294] - </p> - </li> - <li> - <p> - Fixed a bug where the heap's region size was not getting swapped correctly in mixed-endian environments. [#21295] - </p> - </li> - <li> - <p> - Fixed a bug in the db_sql_jdbc project file for vs2010 that was preventing it from building correctly. [#21332] - </p> - </li> - </ol> - </div> - </div> - <div class="sect2" lang="en" xml:lang="en"> - <div class="titlepage"> - <div> - <div> - <h3 class="title"><a id="idp608376"></a>Database or Log File On-Disk Format Changes</h3> + <h3 class="title"><a id="idp1207192"></a>Database or Log File On-Disk Format Changes</h3> </div> </div> </div> @@ -237,7 +147,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp590024"></a>New Features</h3> + <h3 class="title"><a id="idp1200256"></a>New Features</h3> </div> </div> </div> @@ -325,7 +235,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp594216"></a>Database Environment Changes</h3> + <h3 class="title"><a id="idp1206088"></a>Database Environment Changes</h3> </div> </div> </div> @@ -353,7 +263,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp607088"></a>Access Method Changes</h3> + <h3 class="title"><a id="idp1211048"></a>Access Method Changes</h3> </div> </div> </div> @@ -451,7 +361,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp616640"></a>SQL API Changes</h3> + <h3 class="title"><a id="idp1208744"></a>SQL API Changes</h3> </div> </div> </div> @@ -514,7 +424,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp610088"></a>Java-specific API changes</h3> + <h3 class="title"><a id="idp1199152"></a>Java-specific API changes</h3> </div> </div> </div> @@ -542,7 +452,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp616728"></a>Replication Changes</h3> + <h3 class="title"><a id="idp1208832"></a>Replication Changes</h3> </div> </div> </div> @@ -590,7 +500,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp594560"></a>Locking Subsystem Changes</h3> + <h3 class="title"><a id="idp1199992"></a>Locking Subsystem Changes</h3> </div> </div> </div> @@ -608,7 +518,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp635880"></a>Logging Subsystem Changes</h3> + <h3 class="title"><a id="idp1217800"></a>Logging Subsystem Changes</h3> </div> </div> </div> @@ -631,7 +541,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp625488"></a>Memory Pool Subsystem Changes</h3> + <h3 class="title"><a id="idp1209392"></a>Memory Pool Subsystem Changes</h3> </div> </div> </div> @@ -669,7 +579,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp632288"></a>Mutex Subsystem Changes</h3> + <h3 class="title"><a id="idp1226336"></a>Mutex Subsystem Changes</h3> </div> </div> </div> @@ -692,7 +602,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp636296"></a>Transaction Subsystem Changes</h3> + <h3 class="title"><a id="idp1218216"></a>Transaction Subsystem Changes</h3> </div> </div> </div> @@ -710,7 +620,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp625872"></a>Utility Changes</h3> + <h3 class="title"><a id="idp1231856"></a>Utility Changes</h3> </div> </div> </div> @@ -726,11 +636,6 @@ Fixed a bug that could cause recovery to fail if DB->compact moved the meta data page of a HASH subdatabase. [#20708] </p> </li> - <li> - <p> - Fixed two problems with db_hotbackup's handling of transaction logs. A hotbackup would always try to open the logs in the environment home, even if a log directory had been specified. The second fix corrected an error path, in which the memory was freed by the wrong function, possibly causing a guard byte error. [#21313] - </p> - </li> </ol> </div> </div> @@ -738,7 +643,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp632040"></a>Configuration, Documentation, Sample Apps, Portability and Build Changes</h3> + <h3 class="title"><a id="idp1226152"></a>Configuration, Documentation, Sample Apps, Portability and Build Changes</h3> </div> </div> </div> @@ -756,7 +661,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp641456"></a>Known Bugs</h3> + <h3 class="title"><a id="idp1235024"></a>Known Bugs</h3> </div> </div> </div> @@ -796,9 +701,7 @@ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </td> + <td width="40%" align="right" valign="top"> Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </td> </tr> </table> </div> diff --git a/docs/installation/changelog_6_0.html b/docs/installation/changelog_6_0.html new file mode 100644 index 00000000..75186780 --- /dev/null +++ b/docs/installation/changelog_6_0.html @@ -0,0 +1,1028 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Berkeley DB Library Version 12.1.6.0 Change Log</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="drop_sup60.html" title="Dropped Support" /> + <link rel="next" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Berkeley DB Library Version 12.1.6.0 Change Log</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="drop_sup60.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="upgrade_53_toc.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="changelog_6_0"></a>Berkeley DB Library Version 12.1.6.0 Change Log</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1103464">Database or Log File On-Disk Format Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1085208">New Features</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1091952">Database Environment Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1109616">Concurrent Data Store Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1092040">Access Method Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1102752">API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1105448">SQL-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1118096">Tcl-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1103848">Java-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1108320">C#-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1118512">Replication Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1110216">Locking Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1117712">Logging Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1110304">Memory Pool Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1100424">Mutex Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1117416">Transaction Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1129976">Test Suite Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1127624">Utility Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1137784">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1130360">Example Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1140648">Miscellaneous Bug Fixes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1142544">Deprecated Features</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1143680">Known Bugs</a> + </span> + </dt> + </dl> + </div> + <p> + This is the changelog for Berkeley DB + 12<span class="emphasis"><em>c</em></span> Release 1 (library + version 12.1.6.0). + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1103464"></a>Database or Log File On-Disk Format Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + The log file format changed in 12.1.6.0. + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1085208"></a>New Features</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Added an alternate storage format called blobs, which improves the read and update performance of very large data items. Interface available through C, C#, C++ and Java APIs. [#19332] + </p> + </li> + <li> + <p> + Added several pragmas to the SQL layer that configure and give information on HA SQL applications, such as the number of sites in the replication group, or configuring election priority of a site. [#20227] + </p> + </li> + <li> + <p> + Added a BDBSQL_CONCURRENT_CONNECTIONS flag to the SQL API to allow database locking to be disabled. Useful when there are only readers in the database. [#20928] + </p> + </li> + <li> + <p> + When running Replication Manager in multiple processes, if the replication process quits and there is an available subordinate process, the subordinate process automatically takes over as the replication process. [#20969] + </p> + </li> + <li> + <p> + Added replication views/partial replication feature. Feature available through C, C#, C++ and Java APIs. [#21062] + </p> + </li> + <li> + <p> + DPL enhancements to work with JDK7. [#21101] + </p> + </li> + <li> + <p> + Added encryption support for the Android JDBC driver. [#21129] + </p> + </li> + <li> + <p> + Applications which use snapshot isolation and long-running transactions will, in many instances, see reduced use of the cache. This leads to improved performance by reducing the need for temporary freezer files. [#21324] + </p> + </li> + <li> + <p> + Added mpool stat fields st_mvcc_resued, st_oddfsize_detect and st_oddfsize_resolve to C#. [#21325] + </p> + </li> + <li> + <p> + Added support database partitioning in C# APIs. [#21474] + </p> + </li> + <li> + <p> + Added a per-thread cache for the locker struct which stores lock identifiers, such as transaction ids or the locker id returned by DB_ENV->lock_id(). This can improve concurrency of programs which use DB_ENV->set_thread_count(). [#21591] + </p> + </li> + <li> + <p> + Port utilities to Windows Mobile. [#21636] + </p> + </li> + <li> + <p> + Expose 3 new repmgr stat values and a new DB_REPMGR_SITE flag value to C# and Java APIs. [#21687] + </p> + </li> + <li> + <p> + Added support for localizing error messages in UTF-8 characters, and added a section about how to build localized library and an ICU example in Programmer's Reference Guide. [#21280] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1091952"></a>Database Environment Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Redundant whitespaces are now ignored in DB_CONFIG lines pertaining to directories. [#20158] + </p> + </li> + <li> + <p> + Fixed bugs when attempting to open non-DB files as if they were databases. If encryption was active, an assertion failure would occur. If encryption was not active, the error message "BDB0178 Encrypted database: no encryption flag" would incorrectly imply that a password was required. [#21408] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1109616"></a>Concurrent Data Store Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + None + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1092040"></a>Access Method Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug that could allocate a heap data page in a region after the region creation has been undone. [#20939] + </p> + </li> + <li> + <p> + Fixed a bug in heap that prevented it from working in mixed-endian configurations. [#21016] + </p> + </li> + <li> + <p> + Enhance the search performance for Btree access method when the keys share a common prefix. [#21216] + </p> + </li> + <li> + <p> + Fixed bugs with the byte swapping of heap pages. Now heap databases can be moved between little-endian and big-endian architectures. [#21387] + </p> + </li> + <li> + <p> + Fix a race condition where a cursor in the process of being cleaned up could be accessed by another thread of control. [#21714] + </p> + </li> + <li> + <p> + Duplicating the position of a cursor on a partitioned database will no longer result in a crash. [#22195] + </p> + </li> + <li> + <p> + Fixed an assertion error when closing a joined cursor. [#22398] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1102752"></a>API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Change the sequence's cachesize and the delta parameter of DB_SEQUENCE->get to be of type u_int32_t instead of int32_t. [#21552] + </p> + </li> + <li> + <p> + Fixed a bug with the DB_MPOOLFILE->set_maxsize API. In previous releases the file was allowed to grow one page larger than the configured limit. [#21867] + </p> + </li> + <li> + <p> + Change the comparison function in DB->set_bt_compare, DB->set_dup_compare and DB->set_h_compare to accept an extra 'size_t *locp' parameter. [#22235] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1105448"></a>SQL-specific API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Added the PRAGMA large_record_opt, which when enabled can improve the read and update performance of very large records. [#19332] + </p> + </li> + <li> + <p> + Added support for multi-process access to the database in SQL HA applications. [#21050] + </p> + </li> + <li> + <p> + In-memory databases can now be created without passing the flag SQLITE_OPEN_CREATE. [#21456] + </p> + </li> + <li> + <p> + Fix a bug in the SQL API where setting the page size to 64 K would cause an error. Also fixed an associated memory leak in SQL online backup. [#21460] + </p> + </li> + <li> + <p> + Add bdbsql_log_buffer pragma to allow setting of log buffer size. [#21471] + </p> + </li> + <li> + <p> + Upgraded SQLite to version 3.7.13. [#21641] + </p> + </li> + <li> + <p> + Fixed a mutex leak with multi-prcess access to the database in SQL HA applications. [#21714] + </p> + </li> + <li> + <p> + Fixed a bug that could cause jdbc build to fail on ARM-Linux using gnueabi gcc. [#22123] + </p> + </li> + <li> + <p> + Upgraded SQLite to version 3.7.16.2. [#22349] + </p> + </li> + <li> + <p> + Upgraded ADO.NET to version 1.0.85.0. [#22405] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1118096"></a>Tcl-specific API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Support blob storage APIs in Tcl. [#19332] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1103848"></a>Java-specific API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug where EnvironmentConfig.setCreateDir() was not correctly configuring the environment. [#21127] + </p> + </li> + <li> + <p> + Fixed a bug where Database.verify() was not correctly configuring the db. [#22401] + </p> + </li> + <li> + <p> + Fixed a false error message that could be printed when creating a transaction on a replication client in Java. [#21671] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1108320"></a>C#-specific API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Clean up many C# build warnings. [#22285] + </p> + </li> + <li> + <p> + Fixed SWIG typemap defintions for C# interface. [#18509] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1118512"></a>Replication Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed several assertion failures that could result when using failchk and replication. [#19765] + </p> + </li> + <li> + <p> + Provide an error when the local site defined during internal initialization is inconsistent with an earlier definition. [#20870] + </p> + </li> + <li> + <p> + Fixed a bug where replication clients were incorrectly flushing the log when the DB_TXN_WRITE_NOSYNC flag was specified. [#20964] + </p> + </li> + <li> + <p> + Fixed a bug where a valid invocation of the DB_ENV->repmgr_start() method would fail after a previous invocation that supplied an invalid nthreads parameter value. A BDB3640 error was being incorrectly generated. [#21289] + </p> + </li> + <li> + <p> + Fixed a bug where the calculation of the number of required master lease grants enforced that a transaction must be present on a strict majority of replication group sites. It is sufficient that a transaction be present on at least half of the replication group sites, which in some cases reduces the number of required lease grants. [#21329] + </p> + </li> + <li> + <p> + Fixed a recovery issue on the client where an incorrect checkpoint was being selected causing recovery to go to an incorrect point. [#21342] + </p> + </li> + <li> + <p> + Fixed a bug that could result in a crash due to an incorrect re-request on a site that just won an election. [#21344] + </p> + </li> + <li> + <p> + Fixed a bug where logs would never get archived if there are 2 sites and various combinations of failures. [#21448] + </p> + </li> + <li> + <p> + Fixed a bug where we were not detecting the fact that DB_TXN_SNAPSHOT was being used with an HA client. Clients are by definition read only, so snapshot transactions are not permitted. [#21601] + </p> + </li> + <li> + <p> + Fixed a bug where the determination of whether or not a site is peer was incorrectly determined. [#21722] + </p> + </li> + <li> + <p> + Fixed a bug where a Replication Manager master could stop functioning after accepting an obsolete group membership site list from another site. [#21804] + </p> + </li> + <li> + <p> + Reduce the multiple data streams that can sometimes occur if rerequest times are shorter than the time it takes to switch log files or perform a checkpoint at a client site. [#21843] + </p> + </li> + <li> + <p> + Fixed a bug that a site is removed unexpectedly from the replication group when the replication group loses the old master's confirmation of adding the site during a master change. [#21875] + </p> + </li> + <li> + <p> + Fixed a bug where a master site could crash when removing a site if the removed site closes its connections before the master completes its final steps of the operation. [#22050] + </p> + </li> + <li> + <p> + Fixed a bug where an election never happens after the loss of the master when master leases are in use. [#22120] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1110216"></a>Locking Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug that could cause a trap if a lock timeout occured while opening a database. [#21098] + </p> + </li> + <li> + <p> + Fixed a hang which could occur if there were no more space for lockers. [#21774] + </p> + </li> + <li> + <p> + Fixed a potential race condition when building the deadlock detection graph which, under rare conditions, might cause a invalid address fault. [#22261] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1117712"></a>Logging Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug that DB_ENV->log_get_config did not work correctly when it was called before DB_ENV->open. [#21359] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1110304"></a>Memory Pool Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug in the DB_ENV->get_cache_max API that caused it to return an incorrect value and a bug in the DB_ENV->set_cachesize API that caused incorrect behavior when changing the size of an existing cache. [#21146] + </p> + </li> + <li> + <p> + Fixed a race condition occurring when trying to get information about a file and the file is being extended by the OS. [#21193] + </p> + </li> + <li> + <p> + Corrected error messages in several memory pool configuration functions. [#21779] + </p> + </li> + <li> + <p> + Fixed several memory leak items identified by Purify runs. [#22283] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1100424"></a>Mutex Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed an undefined symbol error (MUTEX_IS_OWNED) when configuring with --enable-diagnostic --disable-mutexsupport. [#21145] + </p> + </li> + <li> + <p> + Fix a bug where we were not properly aligning mutexes in DB_PRIVATE regions when the application configured an alignment. [#21491] + </p> + </li> + <li> + <p> + Fix a race condition between DB_ENV->failchk() and the allocation of a mutex. [#21796] + </p> + </li> + <li> + <p> + Limit the default mutex spin count to be at most 200, to avoid excessive spinning on systems with hundreds of hyperthreads. [#21463] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1117416"></a>Transaction Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + None + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1129976"></a>Test Suite Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Added support for get/set_heapsize. [#21510] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1127624"></a>Utility Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug where calling DB->set_partition with a key array required users to keep the memory array valid until after the database was opened. [#18350] + </p> + </li> + <li> + <p> + Fixed a bug that caused DB_ENV->backup to stop early if DB_BACKUP_FILES was not set and a non-DB file was in the data directory. [#21076] + </p> + </li> + <li> + <p> + Fixed a problem with db_hotbackup's -F option, which could cause a segmentation violation. Also replaced an unclear error message. [#21184] + </p> + </li> + <li> + <p> + Fixed three problems with db_hotbackup's backup of transaction logs. A hot backup did not use any configured log directory, but would try to open the logs in the environment home. The second fix corrected an error path, in which the memory was freed by the wrong function, possibly causing a guard byte error. The third fix fixed the issue that a wrong message would be displayed when only "-l" was specified. [#21313] + </p> + </li> + <li> + <p> + Fixed a spurious "No such file or directory" (ENOENT) error when running db_archive in an environment with an empty queue database. [#21541] + </p> + </li> + <li> + <p> + Fixed bugs in compaction of large keys in the upper levels of btrees. [#21569] + </p> + </li> + <li> + <p> + Most utilities no longer operate on replication clients which are being automatically initialized. The DB_REP_LOCKOUT error is now returned. [#21593] + </p> + </li> + <li> + <p> + Fixed a resource leak in the db->verify() function for btrees. The bug would slow down verification and possibly cause it to run out of memory. [##21917] + </p> + </li> + <li> + <p> + Removed a potential hang when compacting databases with many duplicates. [#21975] + </p> + </li> + <li> + <p> + Fixed a bug where we were not returning an error when trying to compact a heap database. [#22063] + </p> + </li> + <li> + <p> + Fixed a bug in the error handling of db_log_verify which would cause a segmenation violation if there were not enough space to create its temporary databases. [#22187] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1137784"></a>Configuration, Documentation, Sample Apps, Portability and Build Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fix an odbc configure issue which was causing ODBC build failure with SQL API. [#21490] + </p> + </li> + <li> + <p> + Disabled encryption by default in SQL API on Linux, completed build options for encryption in SQL and SQL JDBC on Linux, Windows and Android, and updated build process for the three platforms in Installation Guide. [#21872] + </p> + </li> + <li> + <p> + Use "-xO2" as the default optimization level for the Sun Workshop compiler. [#22057] + </p> + </li> + <li> + <p> + Fix an "opcode not supported" error on MIPS platforms whose assembler defaults to the MIPS1 instruction set. [#22065] + </p> + </li> + <li> + <p> + Provide a consistent way to turn on/off encryption for db,sql,jdbc libraries on Unix. [#22158] + </p> + </li> + <li> + <p> + Added the compile option CONFIG_TEST when using debug mode in the db_csharp Windows project, to be consistent with the db Windows project. [#22300] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1130360"></a>Example Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Port the C bulk example to C++. [#19541] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1140648"></a>Miscellaneous Bug Fixes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a race condition that could cause a crash if 2 processes opened the same SQL database at the same time. [#21041] + </p> + </li> + <li> + <p> + Fixed an assert failure in the btree comparison function which caused memory to be allocated to the wrong thread. [#21232] + </p> + </li> + <li> + <p> + Fixed a race condition in the SQL handle cache locking code. [#21265] + </p> + </li> + <li> + <p> + Fixed a bug in the SQL code that prevented the table from being created when BDBSQL_FILE_PER_TABLE is defined. [#21417] + </p> + </li> + <li> + <p> + Fixed a bug that some fields of the partition key DBTs returned from DB->get_partition_keys may not be initialized. [#21474] + </p> + </li> + <li> + <p> + Fixed a bug that prevented a sub-database from being created under the directory identified in DB->set_create_dir. [#21603] + </p> + </li> + <li> + <p> + Fixed a bug where dbenv->mp_mtxcount was not being used correctly. [#21768] + </p> + </li> + <li> + <p> + Cleaned a few variable initialization problems that were causing failures on 64-bit Windows. [#21850] + </p> + </li> + <li> + <p> + Improved the randomness of the 20 byte unique fileid generator on Windows. [#22470] + </p> + </li> + <li> + <p> + Fixed a possible assertion failure in the XA Transaction Manager feature. [#22450] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1142544"></a>Deprecated Features</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Tornado 2.0 is not supported, and VxWorks versions older than 6.9 are not supported. [#21877] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1143680"></a>Known Bugs</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Prepared transactions may not remove databases. An error EINVAL message will be returned by TXN->prepare() if the transaction removed any databases. + </p> + </li> + <li> + <p> + Databases containing BLOBs are not portable between machines of opposite endianness. + </p> + </li> + <li> + <p> + The latest version of the ADO.NET driver uses a new database connection close function that does not clean up the database completely, leaving transactions active. In our build projects that we distribute we added the preprocessor definition INTEROP_LEGACY_CLOSE so the older version will be used. Removing this can cause hangs. + </p> + </li> + <li> + <p> + The db_log_verify utility does not currently implement support for the "-D" option. Also, the "-d" option does not work for an environment with multiple databases. For environments with sub-databases, some unexpected warnings will be thrown. [#22136] + </p> + </li> + <li> + <p> + Aborting a prepared transaction that removes a database or does operations on a blob cannot undo the operations (although the call to txn->prepare throws an error if a user tries to do that). [#22226] + </p> + </li> + <li> + <p> + Using the DB_FAILCHK flag with just the DB_RECOVER flag can cause processes to hang. DB_RECOVER will cause the environment to be rebuilt, and when DB_FAILCHK is specified, it runs fail check as the last step in the open. It is done afer the environment has been rebuilt. There isnt anything for fail check to really do in this case. The hang can occur if a separate process also uses this combination which would mean the environment is rebuilt again and it could conflict with the first process if it is doing the fail check. [#22419] + </p> + </li> + <li> + <p> + A rare race condition in the XA transaction manager can return the error XAER_PROTO in a one-phase commit. [#22450] + </p> + </li> + </ol> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="drop_sup60.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="upgrade_53_toc.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Dropped Support </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/changelog_6_1.html b/docs/installation/changelog_6_1.html new file mode 100644 index 00000000..14fd4359 --- /dev/null +++ b/docs/installation/changelog_6_1.html @@ -0,0 +1,1105 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Berkeley DB Library Version 12.1.6.1 Change Log</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="prev" href="dropsupp61.html" title="Dropped Support" /> + <link rel="next" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Berkeley DB Library Version 12.1.6.1 Change Log</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="dropsupp61.html">Prev</a> </td> + <th width="60%" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + <td width="20%" align="right"> <a accesskey="n" href="upgrade_60_toc.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="changelog_6_1"></a>Berkeley DB Library Version 12.1.6.1 Change Log</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp987784">Changes between 12.1.6.1.20 and 12.1.6.1.23</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp988168">Changes between 12.1.6.1.19 and 12.1.6.1.20</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp973896">Database or Log File On-Disk Format Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1005736">New Features/Improvements</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1006120">Database Environment Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp991992">Concurrent Data Store Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1006184">Access Method Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1001712">API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1016544">SQL-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1006600">Tcl-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1021880">Java-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1023576">C#-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1024704">C++-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1022296">Replication Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1005576">Locking Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1028536">Logging Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1029168">Memory Pool Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1027200">Mutex Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1034480">Transaction Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1029552">Test Suite Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1031736">Utility Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1039888">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1039640">Example Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1039136">Miscellaneous Bug Fixes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1041536">Platform Certification Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1040680">Deprecated Features</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1043736">Known Bugs</a> + </span> + </dt> + </dl> + </div> + <p> + This is the changelog for Berkeley DB + 12<span class="emphasis"><em>c</em></span> Release 1 (library + version 12.1.6.1). + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp987784"></a>Changes between 12.1.6.1.20 and 12.1.6.1.23</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a recovery bug that could cause files to end up in the wrong directory when using logs created in 5.3 or earlier. [#24169] + </p> + </li> + <li> + <p> + Creating a table in SQL will no longer fail if the database connection was opened without the SQLITE_OPEN_CREATE flag. [#24115] + </p> + </li> + <li> + <p> + Fixed a bug where an error message was not displayed back to the user correctly when sequence creation failed. [#24103] + </p> + </li> + <li> + <p> + Fixed a bug where BDB was not handling tables with multiple BLOB columns when using the SQL API. [#24092] + </p> + </li> + <li> + <p> + SQL sequence names are now case insensitive except when surrounded by quotation marks. [#23964] + </p> + </li> + <li> + <p> + Avoid incrementing the statistic DB_LOG_STAT.st_scount ("Total log file flushes") when DB_LOG_NOSYNC is in effect. [#23945] + </p> + </li> + <li> + <p> + Fixed a bug that may lead to crash when opening multiple environments in a multi-threaded program. [#23913] + </p> + </li> + <li> + <p> + Improved the way we mark a password as consumed. [#23876] + </p> + </li> + <li> + <p> + Fixed the error "BDB2074 No space available in latch table" for configurations using plain pthreads mutexes and DB_ENV->set_thread_count(). Susceptible configurations include the definition of HAVE_MUTEX_PTHREADS in db_config.h but do not define HAVE_MUTEX_HYBRID. [#23831] + </p> + </li> + <li> + <p> + Fixed a crash when MVCC and snapshot isolation are used and the system is under heavy load. [#23815] + </p> + </li> + <li> + <p> + Fixed a problem with closing a panicked environment, in which an infinite loop was possible. [#23814] + </p> + </li> + <li> + <p> + Removed Java 5 targets from Windows builds and javadoc production. [#23811] + </p> + </li> + <li> + <p> + Support for client-to-client replication of BLOB data during internal initialization has been disabled. [#23748] + </p> + </li> + <li> + <p> + Fixed a bug that may cause self-deadlock during database compaction. [#23725] + </p> + </li> + <li> + <p> + Fixed a bug in the recovery of a truncated hash database. [#23772] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp988168"></a>Changes between 12.1.6.1.19 and 12.1.6.1.20</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a sqlite3odbc bug which may return an out-of-memory error when calling SQLGetData() on empty long columns. [#22777] + </p> + </li> + <li> + <p> + Enabling BLOB support and master leases will no longer result in unexpected DB_REP_LEASE_EXPIRED errors. [#23275] + </p> + </li> + <li> + <p> + Fixed a race condition when BLOB support is enabled with replication where message handling could fail with an ENOENT error. [#23275] + </p> + </li> + <li> + <p> + Existing SQL databases will have to be reindexed after upgrading to this release. No actions are required for non-SQL databases. Check the upgrade documentation for more details. [#23469] + </p> + </li> + <li> + <p> + Fixed a known bug in SQL where ORDER BY could return results out of order if an index is used to answer the query. [#23469] + </p> + </li> + <li> + <p> + Fixed a bug that causes a crash when opening a corrupted environment with encryption and DB_REGISTER. [#23643] + </p> + </li> + <li> + <p> + Fixed a bug that causes a crash when opening a corrupted environment with DB_FAILCHK using a BDB compiled with DIAGNOSTIC defined. [#23643] + </p> + </li> + <li> + <p> + Fixed a bug where closing a panicked environment raised an access violation and crashed the program. [#23679] + </p> + </li> + <li> + <p> + Fixed a bug where db_verify did not verify multiple files correctly. [#23692] + </p> + </li> + <li> + <p> + Fixed a bug that causes a site joining a replication group to hang or to only partially complete the internal steps necessary to join the replication group. [#23750] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp973896"></a>Database or Log File On-Disk Format Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + The log file format changed in 12.1.6.1. + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1005736"></a>New Features/Improvements</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Demonstrated in a sample app how to use thread-specific structures to associate a DB_EVENT_REP_PERM_FAILED event with the transaction that caused it. [#17686] + </p> + </li> + <li> + <p> + Replication Manager Preferred Master is a new option for 2-site replication groups. One site is the preferred master, which assumes the master role as much of the time as its availability permits. A preferred master replication group guarantees that transactions committed on the preferred master site will never be rolled back while also providing client failover. [#20230] + </p> + </li> + <li> + <p> + A new flag DB_FORCESYNCENV is provided for DB_ENV->close(), which forces flushing the memory mapped regions before unmapping them. [#21176] + </p> + </li> + <li> + <p> + A new API is provided to limit the Replication Manager incoming queue based on the amount of heap memory it uses. [#21481] + </p> + </li> + <li> + <p> + BLOB support is now available for environments configured for replication. [#22359] + </p> + </li> + <li> + <p> + A new version of DB_ENV->failchk() helps supports multi-process environments which use DB_REGISTER rather than a monitoring process. It is turned on with --enable-failchk_broadcast. [#22419] + </p> + </li> + <li> + <p> + Added support for Visual Studio 2012. [#22477] + </p> + </li> + <li> + <p> + CPU time needed for database backups is now reduced. [#22967] + </p> + </li> + <li> + <p> + Added BDB utilities for the Android platform. [#23079] + </p> + </li> + <li> + <p> + Added --enable-error_history support. This diagnostic tool prints a stack trace when a panic occurs. [#23119] + </p> + </li> + <li> + <p> + The new log configuration option DB_LOG_NOSYNC has been added to avoid flushing the transaction log in order to stabilize storage. This can be useful when durability across system crashes is unnecessary and all the transactions in the environment specify either the DB_TXN_NOSYNC or DB_TXN_WRITE_NOSYNC flag. This configuration setting may be made by DB_ENV->log_set_config() or a DB_CONFIG line "db_log_nosync [on|off]". [#23191] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1006120"></a>Database Environment Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a problem with DB_LOCKDOWN which would cause an mlock error ENOMEM on some operating systems. [#21379] + </p> + </li> + <li> + <p> + DB_ENV->close() now detaches from the environment's mmap and shared memory regions even when a panic error (DB_RUNRECOVERY) has been returned. DB_ENV->open(DB_REGISTER) detects whether a panic has occurred in the environment. If so it returns DB_RUNRECOVERY. Prior to this, the panic state was not detected, which might have caused a hang. [#22805] + </p> + </li> + <li> + <p> + Ensure that the size of memory mapped backing files are a multiple of the system pagesize. Previously the files were aligned up to 8KB boundaries, which was not adequate for systems with a 64KB pagesize. [#23290] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp991992"></a>Concurrent Data Store Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + -None + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1006184"></a>Access Method Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug that left behind obsolete queue extents. [#21988] + </p> + </li> + <li> + <p> + Fixed a bug that occurred if the range keys did not fit within one database page during database partition opening. [#22280] + </p> + </li> + <li> + <p> + Corrected a buffer mutex deadlock involving off-page duplicate sets and less than full transactional isolation levels. [#22532] + </p> + </li> + <li> + <p> + Fixed a byte swapping bug that could corrupt the header of heap database pages. [#23318] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1001712"></a>API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Make flag checking in sequence stat print API consistent with the other stat print APIs. [#22513] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1016544"></a>SQL-specific API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug that was preventing old log files from being removed while using the SQL API. [#22521] + </p> + </li> + <li> + <p> + Updated SQL API build to be compatible with SQLite 3.8.3.1. [#23178] + </p> + </li> + <li> + <p> + Updated ADO.NET API to be compatible with System.Data.SQLite 1.0.91.0. [#23446] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1006600"></a>Tcl-specific API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Exposed flag DB_SET_MUTEX_FAILCHK_TIMEOUT in Tcl API. [#23163] + </p> + </li> + <li> + <p> + Added msgfile and msgfile_close in the Tcl API. [#31881]. + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1021880"></a>Java-specific API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Exposed DB->set_msgfile(), DB_ENV->set_msgfile() and all xxx_stat_print() in Java API.[#22691] + </p> + </li> + <li> + <p> + Exposed flags DB_REPMGR_CONF_PREFMAS_MASTER and DB_REPMGR_CONF_PREFMAS_CLIENT in Java API. [#23163] + </p> + </li> + <li> + <p> + Exposed new flag DB_LOG_NOSYNC in Java API. [#23191] + </p> + </li> + <li> + <p> + Updated DPL changes from BDB JE. [#23251] + </p> + </li> + <li> + <p> + Exposed new flag DB_EVENT_REP_INQUEUE_FULL in Java API. [#23280] + </p> + </li> + <li> + <p> + Fixed a bug that partition directories could not be set correctly via Java API. [#23410] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1023576"></a>C#-specific API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + The class LockDetectMode has been removed. It was duplicating functionality provided in other classes and not being used. [#21248] + </p> + </li> + <li> + <p> + Exposed DB_STAT_ALLOC in PrintLockingSystemStats(), PrintLoggingSystemStats(), PrintMPoolSystemStats(), PrintMutexSystemStats(), PrintStats() and PrintTransactionSystemStats(). [#22513] + </p> + </li> + <li> + <p> + Exposed DB->set_msgcall(), DB->set_msgfile(), DB_ENV->set_msgcall() and DB_ENV->set_msgfile() to C# API. [#22799] + </p> + </li> + <li> + <p> + Exposed flags DB_REPMGR_CONF_PREFMAS_MASTER and DB_REPMGR_CONF_PREFMAS_CLIENT in C# API. [#23163] + </p> + </li> + <li> + <p> + Exposed new flag DB_LOG_NOSYNC in C# API. [#23191] + </p> + </li> + <li> + <p> + Exposed new flag DB_EVENT_REP_INQUEUE_FULL in C# API. [#23280] + </p> + </li> + <li> + <p> + Changed definition of all structs to make SWIG 2.0.12 can generate code successfully. [#23295] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1024704"></a>C++-specific API Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug that db_stl library could not build using gcc-4.7 or later versions. [#22615] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1022296"></a>Replication Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug where, after some rare multiple-site failure scenarios including transaction rollbacks, Replication Manager could have incorrectly determined that new transactions fulfilled the acknowledgement policy. [#16624] + </p> + </li> + <li> + <p> + Acknowledgements are counted more precisely when an unelectable client is first joining the replication group and also when a master has been set to be unelectable. [#20825] + </p> + </li> + <li> + <p> + If there is already a replication process running, do not require a flag value when calling DB_ENV->repmgr_start() to start a subordinate process. [#20980] + </p> + </li> + <li> + <p> + Fixed a bug that a site could not rejoin the replication group on Windows after being removed from the group. [#22460] + </p> + </li> + <li> + <p> + When a removed site rejoins a two-site replication group with DB_REPMGR_CONF_2SITE_STRICT turned off, defer its election so that the rejoining site does not prematurely elect itself master with only its own vote when the other site is already master. [#22683] + </p> + </li> + <li> + <p> + Fixed a bug where a Replication Manager subordinate process could fail its automatic takeover as the replication process because it is unnecessarily waiting for acknowledgements from other sites before the connections to these sites are properly established. [#22998] + </p> + </li> + <li> + <p> + Fixed a bug where a client synchronization could get stuck because certain error paths were failing to release an internal lockout. [#23169] + </p> + </li> + <li> + <p> + Fixed a bug where replication group-aware log archiving might have unnecessarily kept log files after certain connection sequences between sites. [#23420] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1005576"></a>Locking Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + None + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1028536"></a>Logging Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Avoid incrementing the statistic DB_LOG_STAT.st_scount ("Total log file flushes") when DB_LOG_NOSYNC is in effect. [#23945] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1029168"></a>Memory Pool Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + None + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1027200"></a>Mutex Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Removed an environment handle mutex which was no longer needed. [#23099] + </p> + </li> + <li> + <p> + Removed the last source files of the defunct fcntl mutex implementation. [#23119] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1034480"></a>Transaction Subsystem Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + None + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1029552"></a>Test Suite Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + None + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1031736"></a>Utility Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + None + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1039888"></a>Configuration, Documentation, Sample Apps, Portability and Build Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a bug that ex_rep_base could not quit gracefully after receiving 'exit' command. [#16871] + </p> + </li> + <li> + <p> + Extended the ex_rep_mgr Replication Manager sample application to demonstrate the use of a thread-specific structure to associate a DB_EVENT_REP_PERM_FAILED event with its originating transaction. [#17686] + </p> + </li> + <li> + <p> + Parameter "-module" is removed from task libsqilte_jni in JDBC makefile. So libsqlite_jni library could be built in '.dylib' format on Mac OS X. [#22937] + </p> + </li> + <li> + <p> + Additional information about the cause of an error may now be displayed by configuring with --enable-error_history. [#23119] + </p> + </li> + <li> + <p> + Add one public error code 'DB_META_CHKSUM_FAIL'. [#23304] + </p> + </li> + <li> + <p> + Added build support on latest MinGW. [#23332] + </p> + </li> + <li> + <p> + A configuration warning 'Ignoring --with-cryptography flag value' is added for the non-crypto package. [#23333] + </p> + </li> + <li> + <p> + Parameter LIBSQLSO_LIBS is added to the task libsqlso_target to workaround a linking issue with the gcc 4.8.1 distributed by Ubuntu. [#23372] + </p> + </li> + <li> + <p> + Extended the Mac OS X section in the chapter 7 of the installation guide. [#23388] + </p> + </li> + <li> + <p> + Fixed PHP module to consistently use the ZEND_REGISTER_RESOURCE macro, preventing a build failure with PHP 5.5. Updated INSTALL file to note the changed location of sample output. [#23391] + </p> + </li> + <li> + <p> + Fixed a few typos in the JDBC/ODBC sections of the Windows/Unix installation guide. [#23404] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1039640"></a>Example Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Added an example using BDB SQL with the JDBC driver and ADF. [#22569] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1039136"></a>Miscellaneous Bug Fixes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Fixed a byte swapping bug with log file operations on blob files. [#22215] + </p> + </li> + <li> + <p> + Fixed test failures on QNX with small mutex regions. [#22310] + </p> + </li> + <li> + <p> + Database containing BLOBS are now portable between machines of opposite endianness. [#22455] + </p> + </li> + <li> + <p> + Added a -D option to display output for db_dump and db_printlog. This value takes priority over DB_ENV->set_data_len() if that was called to set the length. [#22485] + </p> + </li> + <li> + <p> + Updates to PHP API to handle functional changes in PHP 5.4. [#22549] + </p> + </li> + <li> + <p> + Fixed heap databases so they can work on both big and little endian machines. [#22929] + </p> + </li> + <li> + <p> + Restructure the blob delete code to improve performance. [#22935] + </p> + </li> + <li> + <p> + Properly clean up blob meta database after aborting the creation of its parent database. [#23000] + </p> + </li> + <li> + <p> + Fixed memory alignment issues with the DB_MPOOL stats. [#23150] + </p> + </li> + <li> + <p> + Fixed a byte swapping bug with heap blob log records. [#23319] + </p> + </li> + <li> + <p> + Fixed two race condition bugs with DB_ENV->failchk(). [#23347] + </p> + </li> + <li> + <p> + Fixed memory alignment issue on Solaris. [#23571] + </p> + </li> + <li> + <p> + Fixed a bug that using Visual Studio 2010 and JDK 1.5 could generate corrupted jar files. [#23574] + </p> + </li> + <li> + <p> + Fixed a bug that specifying --with-cryptography=yes did not build the jdbc library correctly. [#23606] + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1041536"></a>Platform Certification Changes</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Berkeley DB no longer tests or certifies Windows XP or Windows 2003. + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1040680"></a>Deprecated Features</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + The DB_AUTO_COMMIT flag is present in the DB_SEQUENCE APIs for Java and C#. This flg is no longer meaningful for these APIs and will be deprecated in the next release. + </p> + </li> + </ol> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1043736"></a>Known Bugs</h3> + </div> + </div> + </div> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + [#23469] (Fixed in 12.1.6.1.20 -- see above.) The SQL ORDER BY command on the primary key of a table can in rare cases return the results out of order if an index search is used in executing the query. For example: Create a single column table. Insert two rows with identical values. A query on the row id and the column will produce results in a different order depending on whether an index is used. + </p> + </li> + </ol> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="dropsupp61.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_61_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="upgrade_60_toc.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Dropped Support </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/compare_func.html b/docs/installation/compare_func.html new file mode 100644 index 00000000..8aaaf400 --- /dev/null +++ b/docs/installation/compare_func.html @@ -0,0 +1,84 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Comparison Function Signature Change</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="seq_datatype.html" title="Sequence Datatype Changes" /> + <link rel="next" href="license_change60.html" title="License Change" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Comparison Function Signature Change</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="seq_datatype.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="license_change60.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="compare_func"></a>Comparison Function Signature Change</h2> + </div> + </div> + </div> + <p> + A new parameter has been added to the comparison + callback set by the following methods: + </p> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <a href="../api_reference/C/dbset_bt_compare.html" class="olink">DB->set_bt_compare()</a> + </li> + <li> + <a href="../api_reference/C/dbset_dup_compare.html" class="olink">DB->set_dup_compare()</a> + </li> + <li> + <a href="../api_reference/C/dbset_h_compare.html" class="olink">DB->set_h_compare()</a> + </li> + </ul> + </div> + <p> + The new parameter is the + <code class="literal">locp</code> parameter, and it is the last + parameter required in the callback's signature. It is + intended for internal use only. In customer code, the + parameter must be set to <code class="literal">NULL</code>. + </p> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="seq_datatype.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="license_change60.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Sequence Datatype Changes </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> License Change</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/cross_compile_unix.html b/docs/installation/cross_compile_unix.html index 5cc833f4..088852d9 100644 --- a/docs/installation/cross_compile_unix.html +++ b/docs/installation/cross_compile_unix.html @@ -14,17 +14,17 @@ <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">Cross-Compiling on Unix</th> + <th colspan="3" align="center">Cross-Compiling on + Unix</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="build_unix_flags.html">Prev</a> </td> - <th width="60%" align="center">Chapter 7. - Building Berkeley DB for UNIX/POSIX - </th> + <th width="60%" align="center">Chapter 7. Building Berkeley DB for UNIX/POSIX + </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_install.html">Next</a></td> </tr> </table> @@ -34,32 +34,35 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="cross_compile_unix"></a>Cross-Compiling on Unix</h2> + <h2 class="title" style="clear: both"><a id="cross_compile_unix"></a>Cross-Compiling on + Unix</h2> </div> </div> </div> - <p> - The purpose of cross-compiling is to build a Berkeley DB library on - one platform that is to be used on a different platform. This - section demonstrates how to build a library compatible with the ARM - platform from a 32-bit x86 Linux platform. You will need to adjust - the build tools and options to match your particular platforms. + <p> + The purpose of cross-compiling is to build a Berkeley DB + library on one platform that is to be used on a different + platform. This section demonstrates how to build a library + compatible with the ARM platform from a 32-bit x86 Linux + platform. You will need to adjust the build tools and options + to match your particular platforms. </p> <div class="orderedlist"> <ol type="1"> <li> <p> - Download, install, and test a toolchain that can build the - desired target binaries. In this example, we use the - <code class="literal">arm-linux-gnueabi-gcc</code> package. + Download, install, and test a toolchain that can + build the desired target binaries. In this example, we + use the <code class="literal">arm-linux-gnueabi-gcc</code> + package. </p> </li> <li> - <p> - Decide on your configuration options, and set up your - environment to use the appropriate compiler and compiler - tools. It is often easiest to set this up as a small shell - script. For example: + <p> + Decide on your configuration options, and set up + your environment to use the appropriate compiler and + compiler tools. It is often easiest to set this up as + a small shell script. For example: </p> <pre class="programlisting">#!/bin/sh -f env \ @@ -76,32 +79,36 @@ STRIP=/usr/bin/arm-linux-gnueabi-strip \ --enable-stripped_messages \ --prefix=$HOME/ARM-linux/install \ $* </pre> - <p> - The <code class="literal">--build</code> flag indicates the system on - which you are compiling and the <code class="literal">--host</code> - flag indicates the target platform. Adjust or omit the - <code class="literal">--enable</code> and <code class="literal">--prefix</code> - flag settings as dictated by your own needs. + <p> + The <code class="literal">--build</code> flag indicates the + system on which you are compiling and the + <code class="literal">--host</code> flag indicates the + target platform. Adjust or omit the + <code class="literal">--enable</code> and + <code class="literal">--prefix</code> flag settings as + dictated by your own needs. </p> </li> <li> <p> Unpack your Berkeley DB distribution and go to the - <code class="literal">build_unix</code> directory. Alternatively, you - may create a more appropriately-named directory at the same - level and build in it. For example, - <code class="literal">build_arm</code>. + <code class="literal">build_unix</code> directory. + Alternatively, you may create a more + appropriately-named directory at the same level and + build in it. For example, + <code class="literal">build_arm</code>. </p> </li> <li> - <p> - In your build directory, configure by executing your - script, then <code class="literal">make</code> and - <code class="literal">make install</code>. Review any compiler - warnings and fix if necessary, repeating the - <code class="literal">configure</code> and <code class="literal">make</code> - steps until you are satisfied. The resulting libraries and - executables can then be transferred to your target system. + <p> + In your build directory, configure by executing + your script, then <code class="literal">make</code> and + <code class="literal">make install</code>. Review any + compiler warnings and fix if necessary, repeating the + <code class="literal">configure</code> and + <code class="literal">make</code> steps until you are + satisfied. The resulting libraries and executables can + then be transferred to your target system. </p> </li> </ol> @@ -118,11 +125,13 @@ $* </pre> <td width="40%" align="right"> <a accesskey="n" href="build_unix_install.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Changing compile or load options </td> + <td width="40%" align="left" valign="top">Changing compile or load + options </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Installing Berkeley DB</td> + <td width="40%" align="right" valign="top"> Installing Berkeley + DB</td> </tr> </table> </div> diff --git a/docs/installation/debug.html b/docs/installation/debug.html index a91b70e3..fba56d02 100644 --- a/docs/installation/debug.html +++ b/docs/installation/debug.html @@ -14,13 +14,11 @@ <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 3. - Debugging Applications - </th> + <th colspan="3" align="center">Chapter 3. Debugging Applications </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="install_multiple.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="debug"></a>Chapter 3. - Debugging Applications - </h2> + <h2 class="title"><a id="debug"></a>Chapter 3. Debugging Applications </h2> </div> </div> </div> @@ -69,32 +65,32 @@ <dl> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1304224">Augmenting the Log for Debugging</a> + <a href="debug_printlog.html#idp164880">Augmenting the Log for Debugging</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1194048">Extracting Committed Transactions and Transaction Status</a> + <a href="debug_printlog.html#idp136104">Extracting Committed Transactions and Transaction Status</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1341784">Extracting Transaction Histories</a> + <a href="debug_printlog.html#idp166064">Extracting Transaction Histories</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm986800">Extracting File Histories</a> + <a href="debug_printlog.html#idp171384">Extracting File Histories</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1437640">Extracting Page Histories</a> + <a href="debug_printlog.html#idp183288">Extracting Page Histories</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm680600">Other log processing tools</a> + <a href="debug_printlog.html#idp184088">Other log processing tools</a> </span> </dt> </dl> @@ -109,87 +105,89 @@ </div> </div> </div> + <p> + Because Berkeley DB is an embedded library, debugging + applications that use Berkeley DB is both harder and easier + than debugging a separate server. Debugging can be harder + because when a problem arises, it is not always readily + apparent whether the problem is in the application, is in the + database library, or is a result of an unexpected interaction + between the two. Debugging can be easier because it is easier + to track down a problem when you can review a stack trace + rather than deciphering interprocess communication messages. + This chapter is intended to assist you with debugging + applications and reporting bugs to us so that we can provide + you with the correct answer or fix as quickly as possible. + </p> <p> - Because Berkeley DB is an embedded library, debugging applications that - use Berkeley DB is both harder and easier than debugging a separate - server. Debugging can be harder because when a problem arises, it is - not always readily apparent whether the problem is in the application, - is in the database library, or is a result of an unexpected interaction - between the two. Debugging can be easier because it is easier to track - down a problem when you can review a stack trace rather than - deciphering interprocess communication messages. This chapter is - intended to assist you with debugging applications and reporting bugs - to us so that we can provide you with the correct answer or fix as - quickly as possible. -</p> - <p> - When you encounter a problem, there are a few general actions you can - take: -</p> + When you encounter a problem, there are a few general + actions you can take: + </p> <div class="variablelist"> <dl> <dt> <span class="term">Review the Berkeley DB error output:</span> </dt> <dd> - <p> - If an error output mechanism has been configured in the - Berkeley DB environment, additional run-time error messages - are made available to the applications. If you are not - using an environment, it is well worth modifying your - application to create one so that you can get more detailed - error messages. See - <a class="xref" href="debug_runtime.html" title="Run-time error information">Run-time error information</a> - for more information on configuring Berkeley DB to output these - error messages. - </p> + <p> + If an error output mechanism has been + configured in the Berkeley DB environment, + additional run-time error messages are made + available to the applications. If you are not + using an environment, it is well worth modifying + your application to create one so that you can get + more detailed error messages. See <a class="xref" href="debug_runtime.html" title="Run-time error information">Run-time error information</a> for more + information on configuring Berkeley DB to output + these error messages. + </p> </dd> <dt> - <span class="term">Review the options available for the <a href="../api_reference/C/envset_verbose.html" class="olink">DB_ENV->set_verbose()</a> method:</span> + <span class="term">Review the options available for the + <a href="../api_reference/C/envset_verbose.html" class="olink">DB_ENV->set_verbose()</a> method:</span> </dt> <dd> <p> - Look to see if it offers any additional informational - and/or debugging messages that might help you understand - the problem. - </p> + Look to see if it offers any additional + informational and/or debugging messages that might + help you understand the problem. + </p> </dd> <dt> <span class="term">Add run-time diagnostics:</span> </dt> <dd> - <p> - You can configure and build Berkeley DB to perform run-time - diagnostics. (By default, these checks are not done - because they can seriously impact performance.) See - <a class="xref" href="debug_compile.html" title="Compile-time configuration">Compile-time configuration</a> - for more information. - </p> + <p> + You can configure and build Berkeley DB to + perform run-time diagnostics. (By default, these + checks are not done because they can seriously + impact performance.) See <a class="xref" href="debug_compile.html" title="Compile-time configuration">Compile-time configuration</a> for more + information. + </p> </dd> <dt> <span class="term">Apply all available patches:</span> </dt> <dd> <p> - Before reporting a problem in Berkeley DB, please upgrade - to the latest Berkeley DB release, if possible, or at least - make sure you have applied any updates available for your - release from the - <a class="ulink" href="http://www.oracle.com/technetwork/database/berkeleydb/downloads/index.html" target="_top"> - Berkeley DB web site - </a>. - </p> + Before reporting a problem in Berkeley DB, + please upgrade to the latest Berkeley DB release, + if possible, or at least make sure you have + applied any updates available for your release + from the <a class="ulink" href="http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index.html" target="_top"> + Berkeley DB web site </a>. + </p> </dd> <dt> <span class="term">Run the test suite:</span> </dt> <dd> - <p> - If you see repeated failures or failures of simple test - cases, run the Berkeley DB test suite to determine whether - the distribution of Berkeley DB you are using was built and - configured correctly. - </p> + <p> + If you see repeated failures or failures of + simple test cases, run the Berkeley DB test suite + to determine whether the distribution of Berkeley + DB you are using was built and configured + correctly. + </p> </dd> </dl> </div> diff --git a/docs/installation/debug_compile.html b/docs/installation/debug_compile.html index 52482f37..dd44f29d 100644 --- a/docs/installation/debug_compile.html +++ b/docs/installation/debug_compile.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="debug.html">Prev</a> </td> - <th width="60%" align="center">Chapter 3. - Debugging Applications - </th> + <th width="60%" align="center">Chapter 3. Debugging Applications </th> <td width="20%" align="right"> <a accesskey="n" href="debug_runtime.html">Next</a></td> </tr> </table> @@ -38,44 +36,61 @@ </div> </div> </div> - <p>There are three compile-time configuration options that assist in -debugging Berkeley DB and Berkeley DB applications:</p> + <p> + There are three compile-time configuration options that + assist in debugging Berkeley DB and Berkeley DB + applications: + </p> <div class="variablelist"> <dl> <dt> <span class="term"> - <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-debug">--enable-debug</a> + <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-debug">--enable-debug</a> </span> </dt> - <dd>If you want to build Berkeley DB with <span class="bold"><strong>-g</strong></span> as the C and C++ compiler -flag, enter --enable-debug as an argument to configure. This will create -Berkeley DB with debugging symbols, as well as load various Berkeley DB routines -that can be called directly from a debugger to display database page -content, cursor queues, and so forth. (Note that the <span class="bold"><strong>-O</strong></span> -optimization flag will still be specified. To compile with only the -<span class="bold"><strong>-g</strong></span>, explicitly set the <code class="literal">CFLAGS</code> environment variable -before configuring.)</dd> + <dd> + If you want to build Berkeley DB with <span class="bold"><strong>-g</strong></span> as the C and C++ + compiler flag, enter --enable-debug as an argument to + configure. This will create Berkeley DB with debugging + symbols, as well as load various Berkeley DB routines + that can be called directly from a debugger to display + database page content, cursor queues, and so forth. + (Note that the <span class="bold"><strong>-O</strong></span> + optimization flag will still be specified. To compile + with only the <span class="bold"><strong>-g</strong></span>, + explicitly set the <code class="literal">CFLAGS</code> + environment variable before configuring.) + </dd> <dt> <span class="term"> - <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-diagnostic">--enable-diagnostic</a> + <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-diagnostic">--enable-diagnostic</a> </span> </dt> - <dd>If you want to build Berkeley DB with debugging run-time sanity checks and with -DIAGNOSTIC #defined during compilation, enter --enable-diagnostic as an -argument to configure. This will cause a number of special checks to be -performed when Berkeley DB is running. This flag should not be defined when -configuring to build production binaries because it degrades performance.</dd> + <dd> + If you want to build Berkeley DB with debugging + run-time sanity checks and with DIAGNOSTIC #defined + during compilation, enter --enable-diagnostic as an + argument to configure. This will cause a number of + special checks to be performed when Berkeley DB is + running. This flag should not be defined when + configuring to build production binaries because it + degrades performance. + </dd> <dt> <span class="term"> - <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-umrw">--enable-umrw</a> + <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-umrw">--enable-umrw</a> </span> </dt> - <dd>When compiling Berkeley DB for use in run-time memory consistency checkers -(in particular, programs that look for reads and writes of uninitialized -memory), use --enable-umrw as an argument to configure. This -guarantees, among other things, that Berkeley DB will completely initialize -allocated pages rather than initializing only the minimum necessary -amount.</dd> + <dd> + When compiling Berkeley DB for use in run-time + memory consistency checkers (in particular, programs + that look for reads and writes of uninitialized + memory), use --enable-umrw as an argument to + configure. This guarantees, among other things, that + Berkeley DB will completely initialize allocated pages + rather than initializing only the minimum necessary + amount. + </dd> </dl> </div> </div> @@ -90,9 +105,7 @@ amount.</dd> <td width="40%" align="right"> <a accesskey="n" href="debug_runtime.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 3. - Debugging Applications - </td> + <td width="40%" align="left" valign="top">Chapter 3. Debugging Applications </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/debug_printlog.html b/docs/installation/debug_printlog.html index d28e6dae..493df2c1 100644 --- a/docs/installation/debug_printlog.html +++ b/docs/installation/debug_printlog.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="debug_runtime.html">Prev</a> </td> - <th width="60%" align="center">Chapter 3. - Debugging Applications - </th> + <th width="60%" align="center">Chapter 3. Debugging Applications </th> <td width="20%" align="right"> <a accesskey="n" href="build_android_intro.html">Next</a></td> </tr> </table> @@ -42,93 +40,95 @@ <dl> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1304224">Augmenting the Log for Debugging</a> + <a href="debug_printlog.html#idp164880">Augmenting the Log for Debugging</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1194048">Extracting Committed Transactions and Transaction Status</a> + <a href="debug_printlog.html#idp136104">Extracting Committed Transactions and Transaction Status</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1341784">Extracting Transaction Histories</a> + <a href="debug_printlog.html#idp166064">Extracting Transaction Histories</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm986800">Extracting File Histories</a> + <a href="debug_printlog.html#idp171384">Extracting File Histories</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1437640">Extracting Page Histories</a> + <a href="debug_printlog.html#idp183288">Extracting Page Histories</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm680600">Other log processing tools</a> + <a href="debug_printlog.html#idp184088">Other log processing tools</a> </span> </dt> </dl> </div> - <p> - If you are running with transactions and logging, the <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility can - be a useful debugging aid. The <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility will display the contents - of your log files in a human readable (and machine-readable) format. -</p> - <p> - The <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility will attempt to display any and all log files present - in a designated db_home directory. For each log record, the - <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility will display a line of the form: -</p> + <p> + If you are running with transactions and logging, the + <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility can be a useful debugging aid. The <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility + will display the contents of your log files in a human + readable (and machine-readable) format. + </p> + <p> + The <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility will attempt to display any and all log + files present in a designated db_home directory. For each log + record, the <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility will display a line of the form: + </p> <pre class="programlisting"> -[22][28]db_big: rec: 43 txnid 80000963 prevlsn [21][10483281] -</pre> - <p> - The opening numbers in square brackets are the <span class="emphasis"><em>log sequence - number</em></span> (<span class="emphasis"><em>LSN</em></span>) of the log record - being displayed. The first number indicates the log file in which the - record appears, and the second number indicates the offset in that file - of the record. -</p> - <p> - The first character string identifies the particular log operation - being reported. The log records corresponding to particular operations - are described following. The rest of the line consists of name/value - pairs. -</p> - <p> - The rec field indicates the record type (this is used to dispatch - records in the log to appropriate recovery functions). -</p> +[22][28]db_big: rec: 43 txnid 80000963 prevlsn [21][10483281]</pre> + <p> + The opening numbers in square brackets are the + <span class="emphasis"><em>log sequence number</em></span> + (<span class="emphasis"><em>LSN</em></span>) of the log record being + displayed. The first number indicates the log file in which + the record appears, and the second number indicates the offset + in that file of the record. + </p> + <p> + The first character string identifies the particular log + operation being reported. The log records corresponding to + particular operations are described following. The rest of the + line consists of name/value pairs. + </p> + <p> + The rec field indicates the record type (this is used to + dispatch records in the log to appropriate recovery + functions). + </p> <p> - The txnid field identifies the transaction for which this record was - written. A txnid of 0 means that the record was written outside the - context of any transaction. You will see these most frequently for - checkpoints. -</p> + The txnid field identifies the transaction for which this + record was written. A txnid of 0 means that the record was + written outside the context of any transaction. You will see + these most frequently for checkpoints. + </p> <p> - Finally, the prevlsn contains the LSN of the last record for this - transaction. By following prevlsn fields, you can accumulate all the - updates for a particular transaction. During normal abort processing, - this field is used to quickly access all the records for a particular - transaction. -</p> + Finally, the prevlsn contains the LSN of the last record + for this transaction. By following prevlsn fields, you can + accumulate all the updates for a particular transaction. + During normal abort processing, this field is used to quickly + access all the records for a particular transaction. + </p> <p> - After the initial line identifying the record type, each field of the - log record is displayed, one item per line. There are several fields - that appear in many different records and a few fields that appear only - in some records. -</p> + After the initial line identifying the record type, each + field of the log record is displayed, one item per line. There + are several fields that appear in many different records and a + few fields that appear only in some records. + </p> <p> - The following table presents each currently written log record type - with a brief description of the operation it describes. Any of these - record types may have the string "_debug" appended if they were written - because <a href="../api_reference/C/dbset_flags.html#dbset_flags_DB_TXN_NOT_DURABLE" class="olink">DB_TXN_NOT_DURABLE</a> was specified and the - system was configured with - <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-diagnostic">--enable-diagnostic</a>. -</p> + The following table presents each currently written log + record type with a brief description of the operation it + describes. Any of these record types may have the string + "_debug" appended if they were written because + <a href="../api_reference/C/dbset_flags.html#dbset_flags_DB_TXN_NOT_DURABLE" class="olink">DB_TXN_NOT_DURABLE</a> was specified and the system was + configured with <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-diagnostic">--enable-diagnostic</a>. + </p> <div class="informaltable"> <table border="1" width="80%"> <colgroup> @@ -144,43 +144,56 @@ <tbody> <tr> <td>bam_adj</td> - <td>Used when we insert/remove an index into/from the page header of a Btree page.</td> + <td>Used when we insert/remove an index + into/from the page header of a Btree + page.</td> </tr> <tr> <td>bam_cadjust</td> - <td>Keeps track of record counts in a Btree or Recno database.</td> + <td>Keeps track of record counts in a Btree or + Recno database.</td> </tr> <tr> <td>bam_cdel</td> - <td>Used to mark a record on a page as deleted.</td> + <td>Used to mark a record on a page as + deleted.</td> </tr> <tr> <td>bam_curadj</td> - <td>Used to adjust a cursor location when a nearby record changes in a Btree database.</td> + <td>Used to adjust a cursor location when a + nearby record changes in a Btree + database.</td> </tr> <tr> <td>bam_merge</td> - <td>Used to merge two Btree database pages during compaction.</td> + <td>Used to merge two Btree database pages + during compaction.</td> </tr> <tr> <td>bam_pgno</td> - <td>Used to replace a page number in a Btree record.</td> + <td>Used to replace a page number in a Btree + record.</td> </tr> <tr> <td>bam_rcuradj</td> - <td>Used to adjust a cursor location when a nearby record changes in a Recno database.</td> + <td>Used to adjust a cursor location when a + nearby record changes in a Recno + database.</td> </tr> <tr> <td>bam_relink</td> - <td>Fix leaf page prev/next chain when a page is removed.</td> + <td>Fix leaf page prev/next chain when a page + is removed.</td> </tr> <tr> <td>bam_repl</td> - <td>Describes a replace operation on a record.</td> + <td>Describes a replace operation on a + record.</td> </tr> <tr> <td>bam_root</td> - <td>Describes an assignment of a root page.</td> + <td>Describes an assignment of a root + page.</td> </tr> <tr> <td>bam_rsplit</td> @@ -192,27 +205,35 @@ </tr> <tr> <td>crdel_inmem_create</td> - <td>Record the creation of an in-memory named database.</td> + <td>Record the creation of an in-memory named + database.</td> </tr> <tr> <td>crdel_inmem_remove</td> - <td>Record the removal of an in-memory named database.</td> + <td>Record the removal of an in-memory named + database.</td> </tr> <tr> <td>crdel_inmem_rename</td> - <td>Record the rename of an in-memory named database.</td> + <td>Record the rename of an in-memory named + database.</td> </tr> <tr> <td>crdel_metasub</td> - <td>Describes the creation of a metadata page for a subdatabase.</td> + <td>Describes the creation of a metadata page + for a subdatabase.</td> </tr> <tr> <td>db_addrem</td> - <td>Add or remove an item from a page of duplicates.</td> + <td>Add or remove an item from a page of + duplicates.</td> </tr> <tr> <td>db_big</td> - <td>Add an item to an overflow page (<span class="emphasis"><em>overflow pages</em></span> contain items too large to place on the main page)</td> + <td>Add an item to an overflow page + (<span class="emphasis"><em>overflow pages</em></span> + contain items too large to place on the main + page)</td> </tr> <tr> <td>db_cksum</td> @@ -224,35 +245,45 @@ </tr> <tr> <td>db_noop</td> - <td>This marks an operation that did nothing but update the LSN on a page.</td> + <td>This marks an operation that did nothing + but update the LSN on a page.</td> </tr> <tr> <td>db_ovref</td> - <td>Increment or decrement the reference count for a big item.</td> + <td>Increment or decrement the reference count + for a big item.</td> </tr> <tr> <td>db_pg_alloc</td> - <td>Indicates we allocated a page to a database.</td> + <td>Indicates we allocated a page to a + database.</td> </tr> <tr> <td>db_pg_free</td> - <td>Indicates we freed a page (freed pages are added to a freelist and reused).</td> + <td>Indicates we freed a page (freed pages are + added to a freelist and reused).</td> </tr> <tr> <td>db_pg_freedata</td> - <td>Indicates we freed a page that still contained data entries (freed pages are added to a freelist and reused.)</td> + <td>Indicates we freed a page that still + contained data entries (freed pages are added + to a freelist and reused.)</td> </tr> <tr> <td>db_pg_init</td> - <td>Indicates we reinitialized a page during a truncate.</td> + <td>Indicates we reinitialized a page during a + truncate.</td> </tr> <tr> <td>db_pg_sort</td> - <td>Sort the free page list and free pages at the end of the file.</td> + <td>Sort the free page list and free pages at + the end of the file.</td> </tr> <tr> <td>dbreg_register</td> - <td>Records an open of a file (mapping the filename to a log-id that is used in subsequent log operations).</td> + <td>Records an open of a file (mapping the + filename to a log-id that is used in + subsequent log operations).</td> </tr> <tr> <td>fop_create</td> @@ -272,39 +303,53 @@ </tr> <tr> <td>fop_write</td> - <td>Write bytes to an object in the file system.</td> + <td>Write bytes to an object in the file + system.</td> </tr> <tr> <td>ham_chgpg</td> - <td>Used to adjust a cursor location when a Hash page is removed, and its elements are moved to a different Hash page.</td> + <td>Used to adjust a cursor location when a + Hash page is removed, and its elements are + moved to a different Hash page.</td> </tr> <tr> <td>ham_copypage</td> - <td>Used when we empty a bucket page, but there are overflow pages for the bucket; one needs to be copied back into the actual bucket.</td> + <td>Used when we empty a bucket page, but there + are overflow pages for the bucket; one needs + to be copied back into the actual + bucket.</td> </tr> <tr> <td>ham_curadj</td> - <td>Used to adjust a cursor location when a nearby record changes in a Hash database.</td> + <td>Used to adjust a cursor location when a + nearby record changes in a Hash + database.</td> </tr> <tr> <td>ham_groupalloc</td> - <td>Allocate some number of contiguous pages to the Hash database.</td> + <td>Allocate some number of contiguous pages to + the Hash database.</td> </tr> <tr> <td>ham_insdel</td> - <td>Insert/delete an item on a Hash page.</td> + <td>Insert/delete an item on a Hash + page.</td> </tr> <tr> <td>ham_metagroup</td> - <td>Update the metadata page to reflect the allocation of a sequence of contiguous pages.</td> + <td>Update the metadata page to reflect the + allocation of a sequence of contiguous + pages.</td> </tr> <tr> <td>ham_newpage</td> - <td>Adds or removes overflow pages from a Hash bucket.</td> + <td>Adds or removes overflow pages from a Hash + bucket.</td> </tr> <tr> <td>ham_replace</td> - <td>Handle updates to records that are on the main page.</td> + <td>Handle updates to records that are on the + main page.</td> </tr> <tr> <td>ham_splitdata</td> @@ -312,25 +357,28 @@ </tr> <tr> <td>heap_addrem</td> - <td>Add or remove an entry from a Heap database.</td> + <td>Add or remove an entry from a Heap + database.</td> </tr> <tr> <td>heap_pg_alloc</td> - <td>Indicates we allocated a page to a Heap database.</td> + <td>Indicates we allocated a page to a Heap + database.</td> </tr> <tr> <td>heap_trunc_meta</td> - <td>Records the truncation of the meta page in a Heap - database.</td> + <td>Records the truncation of the meta page in + a Heap database.</td> </tr> <tr> <td>heap_trunc_page</td> - <td>Records the truncation of a data page in a Heap - database.</td> + <td>Records the truncation of a data page in a + Heap database.</td> </tr> <tr> <td>qam_add</td> - <td>Describes the actual addition of a new record to a Queue.</td> + <td>Describes the actual addition of a new + record to a Queue.</td> </tr> <tr> <td>qam_del</td> @@ -338,15 +386,19 @@ </tr> <tr> <td>qam_delext</td> - <td>Delete a record in a Queue with extents.</td> + <td>Delete a record in a Queue with + extents.</td> </tr> <tr> <td>qam_incfirst</td> - <td>Increments the record number that refers to the first record in the database.</td> + <td>Increments the record number that refers to + the first record in the database.</td> </tr> <tr> <td>qam_mvptr</td> - <td>Indicates we changed the reference to either or both of the first and current records in the file.</td> + <td>Indicates we changed the reference to + either or both of the first and current + records in the file.</td> </tr> <tr> <td>txn_child</td> @@ -362,7 +414,8 @@ </tr> <tr> <td>txn_regop</td> - <td>Logs a regular (non-child) transaction commit.</td> + <td>Logs a regular (non-child) transaction + commit.</td> </tr> <tr> <td>txn_xa_regop</td> @@ -375,126 +428,128 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1304224"></a>Augmenting the Log for Debugging</h3> + <h3 class="title"><a id="idp164880"></a>Augmenting the Log for Debugging</h3> </div> </div> </div> <p> - When debugging applications, it is sometimes useful to log not only - the actual operations that modify pages, but also the underlying - Berkeley DB functions being executed. This form of logging can add - significant bulk to your log, but can permit debugging application - errors that are almost impossible to find any other way. To turn - on these log messages, specify the --enable-debug_rop and - --enable-debug_wop configuration options when - configuring Berkeley DB. See - <a class="xref" href="build_unix_conf.html" title="Configuring Berkeley DB">Configuring Berkeley DB</a> for more information. - </p> + When debugging applications, it is sometimes useful to + log not only the actual operations that modify pages, but + also the underlying Berkeley DB functions being executed. + This form of logging can add significant bulk to your log, + but can permit debugging application errors that are + almost impossible to find any other way. To turn on these + log messages, specify the --enable-debug_rop and + --enable-debug_wop configuration options when configuring + Berkeley DB. See <a class="xref" href="build_unix_conf.html" title="Configuring Berkeley DB">Configuring Berkeley DB</a> for more + information. + </p> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1194048"></a>Extracting Committed Transactions and Transaction Status</h3> + <h3 class="title"><a id="idp136104"></a>Extracting Committed Transactions and Transaction Status</h3> </div> </div> </div> <p> - Sometimes, it is helpful to use the human-readable log output to - determine which transactions committed and aborted. The awk - script, commit.awk, (found in the db_printlog directory of the - Berkeley DB distribution) allows you to do just that. The - following command, where log_output is the output of db_printlog, - will display a list of the transaction IDs of all committed - transactions found in the log: - </p> + Sometimes, it is helpful to use the human-readable log + output to determine which transactions committed and + aborted. The awk script, commit.awk, (found in the + db_printlog directory of the Berkeley DB distribution) + allows you to do just that. The following command, where + log_output is the output of db_printlog, will display a + list of the transaction IDs of all committed transactions + found in the log: + </p> <pre class="programlisting">awk -f commit.awk log_output</pre> <p> - If you need a complete list of both committed and aborted transactions, - then the script status.awk will produce it. The syntax is as - follows: - </p> + If you need a complete list of both committed and + aborted transactions, then the script status.awk will + produce it. The syntax is as follows: </p> <pre class="programlisting">awk -f status.awk log_output</pre> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1341784"></a>Extracting Transaction Histories</h3> + <h3 class="title"><a id="idp166064"></a>Extracting Transaction Histories</h3> </div> </div> </div> - <p> - Another useful debugging aid is to print out the complete history - of a transaction. The awk script txn.awk allows you to do that. - The following command line, where log_output is the output of the - <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility and txnlist is a comma-separated list of transaction - IDs, will display all log records associated with the designated - transaction ids: - </p> + <p> + Another useful debugging aid is to print out the + complete history of a transaction. The awk script txn.awk + allows you to do that. The following command line, where + log_output is the output of the <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility and txnlist + is a comma-separated list of transaction IDs, will display + all log records associated with the designated transaction + ids: + </p> <pre class="programlisting">awk -f txn.awk TXN=txnlist log_output</pre> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm986800"></a>Extracting File Histories</h3> + <h3 class="title"><a id="idp171384"></a>Extracting File Histories</h3> </div> </div> </div> - <p> - The awk script fileid.awk allows you to extract all log records - that refer to a designated file. The syntax for the fileid.awk - script is the following, where log_output is the output of - db_printlog and fids is a comma-separated list of fileids: - </p> + <p> + The awk script fileid.awk allows you to extract all log + records that refer to a designated file. The syntax for + the fileid.awk script is the following, where log_output + is the output of db_printlog and fids is a comma-separated + list of fileids: + </p> <pre class="programlisting">awk -f fileid.awk PGNO=fids log_output</pre> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm1437640"></a>Extracting Page Histories</h3> + <h3 class="title"><a id="idp183288"></a>Extracting Page Histories</h3> </div> </div> </div> <p> - The awk script pgno.awk allows you to extract all log records that - refer to designated page numbers. However, because this script - will extract records with the designated page numbers for all - files, it is most useful in conjunction with the fileid script. - The syntax for the pgno.awk script is the following, where - log_output is the output of db_printlog and pgnolist is a - comma-separated list of page numbers: - </p> + The awk script pgno.awk allows you to extract all log + records that refer to designated page numbers. However, + because this script will extract records with the + designated page numbers for all files, it is most useful + in conjunction with the fileid script. The syntax for the + pgno.awk script is the following, where log_output is the + output of db_printlog and pgnolist is a comma-separated + list of page numbers: + </p> <pre class="programlisting">awk -f pgno.awk PGNO=pgnolist log_output</pre> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm680600"></a>Other log processing tools</h3> + <h3 class="title"><a id="idp184088"></a>Other log processing tools</h3> </div> </div> </div> <p> - The awk script count.awk prints out the number of log records - encountered that belonged to some transaction (that is, the number - of log records excluding those for checkpoints and - non-transaction-protected operations). - </p> - <p> - The script range.awk will extract a subset of a log. This is - useful when the output of <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility is too large to be - reasonably manipulated with an editor or other tool. The syntax - for range.awk is the following, where - <span class="bold"><strong>sf</strong></span> and - <span class="bold"><strong>so</strong></span> represent the LSN of the - beginning of the sublog you want to extract, and - <span class="bold"><strong>ef</strong></span> and - <span class="bold"><strong>eo</strong></span> represent the LSN of the end of - the sublog you want to extract: - </p> + The awk script count.awk prints out the number of log + records encountered that belonged to some transaction + (that is, the number of log records excluding those for + checkpoints and non-transaction-protected operations). + </p> + <p> + The script range.awk will extract a subset of a log. + This is useful when the output of <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog</a> utility is too + large to be reasonably manipulated with an editor or other + tool. The syntax for range.awk is the following, where + <span class="bold"><strong>sf</strong></span> and <span class="bold"><strong>so</strong></span> represent the LSN of the + beginning of the sublog you want to extract, and <span class="bold"><strong>ef</strong></span> and <span class="bold"><strong>eo</strong></span> + represent the LSN of the end of the + sublog you want to extract: + </p> <pre class="programlisting"> awk -f range.awk START_FILE=sf START_OFFSET=so END_FILE=ef \ END_OFFSET=eo log_output </pre> </div> @@ -514,7 +569,8 @@ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 4. Building Berkeley DB for Android</td> + <td width="40%" align="right" valign="top"> Chapter 4. Building Berkeley DB for + Android</td> </tr> </table> </div> diff --git a/docs/installation/debug_runtime.html b/docs/installation/debug_runtime.html index 58a5beec..0708f684 100644 --- a/docs/installation/debug_runtime.html +++ b/docs/installation/debug_runtime.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="debug_compile.html">Prev</a> </td> - <th width="60%" align="center">Chapter 3. - Debugging Applications - </th> + <th width="60%" align="center">Chapter 3. Debugging Applications </th> <td width="20%" align="right"> <a accesskey="n" href="debug_printlog.html">Next</a></td> </tr> </table> @@ -38,32 +36,44 @@ </div> </div> </div> - <p>Normally, when an error occurs in the Berkeley DB library, an integer value -(either a Berkeley DB specific value or a system <code class="literal">errno</code> value) is -returned by Berkeley DB. In some cases, however, this value may be -insufficient to completely describe the cause of the error, especially -during initial application debugging.</p> - <p>Most Berkeley DB errors will result in additional information being written -to a standard file descriptor or output stream. Additionally, Berkeley DB can -be configured to pass these verbose error messages to an application -function. There are four methods intended to provide applications with -additional error information: -<a href="../api_reference/C/envset_errcall.html" class="olink">DB_ENV->set_errcall()</a>, <a href="../api_reference/C/envset_errfile.html" class="olink">DB_ENV->set_errfile()</a>, -<a href="../api_reference/C/envset_errpfx.html" class="olink">DB_ENV->set_errpfx()</a> and <a href="../api_reference/C/envset_verbose.html" class="olink">DB_ENV->set_verbose()</a>.</p> - <p>The Berkeley DB error-reporting facilities do not slow performance or -significantly increase application size, and may be run during normal -operation as well as during debugging. Where possible, we recommend -these options always be configured and the output saved in the -filesystem. We have found that this often saves time when debugging -installation or other system-integration problems.</p> - <p>In addition, there are three methods to assist applications in -displaying their own error messages: <a href="../api_reference/C/envstrerror.html" class="olink">db_strerror()</a>, <a href="../api_reference/C/enverr.html" class="olink">DB_ENV->err()</a>, -and <code class="methodname">DB_ENV->errx()</code>. The first is a superset of -the ANSI C strerror function, and returns a descriptive string for any -error return from the Berkeley DB library. The <a href="../api_reference/C/enverr.html" class="olink">DB_ENV->err()</a> and -<code class="methodname">DB_ENV->errx()</code> methods use the error message configuration options -described previously to format and display error messages to appropriate -output devices.</p> + <p> + Normally, when an error occurs in the Berkeley DB library, + an integer value (either a Berkeley DB specific value or a + system <code class="literal">errno</code> value) is returned by Berkeley + DB. In some cases, however, this value may be insufficient to + completely describe the cause of the error, especially during + initial application debugging. + </p> + <p> + Most Berkeley DB errors will result in additional + information being written to a standard file descriptor or + output stream. Additionally, Berkeley DB can be configured to + pass these verbose error messages to an application function. + There are four methods intended to provide applications with + additional error information: <a href="../api_reference/C/envset_errcall.html" class="olink">DB_ENV->set_errcall()</a>, + <a href="../api_reference/C/envset_errfile.html" class="olink">DB_ENV->set_errfile()</a>, <a href="../api_reference/C/envset_errpfx.html" class="olink">DB_ENV->set_errpfx()</a> and <a href="../api_reference/C/envset_verbose.html" class="olink">DB_ENV->set_verbose()</a>. + </p> + <p> + The Berkeley DB error-reporting facilities do not slow + performance or significantly increase application size, and + may be run during normal operation as well as during + debugging. Where possible, we recommend these options always + be configured and the output saved in the filesystem. We have + found that this often saves time when debugging installation + or other system-integration problems. + </p> + <p> + In addition, there are three methods to assist applications + in displaying their own error messages: <a href="../api_reference/C/envstrerror.html" class="olink">db_strerror()</a>, + <a href="../api_reference/C/enverr.html" class="olink">DB_ENV->err()</a>, and <code class="methodname">DB_ENV->errx()</code>. The + first is a superset of the ANSI C strerror function, and + returns a descriptive string for any error return from the + Berkeley DB library. The <a href="../api_reference/C/enverr.html" class="olink">DB_ENV->err()</a> and + <code class="methodname">DB_ENV->errx()</code> methods use the + error message configuration options described previously to + format and display error messages to appropriate output + devices. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/drop_sup60.html b/docs/installation/drop_sup60.html new file mode 100644 index 00000000..1523549f --- /dev/null +++ b/docs/installation/drop_sup60.html @@ -0,0 +1,65 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Dropped Support</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="sun_opt.html" title="Sun Workshop Compiler Optimization Level" /> + <link rel="next" href="changelog_6_0.html" title="Berkeley DB Library Version 12.1.6.0 Change Log" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Dropped Support</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="sun_opt.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="changelog_6_0.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="drop_sup60"></a>Dropped Support</h2> + </div> + </div> + </div> + <p> + Berkeley DB no longer supports Tornado 2.0 or versions + of VxWorks earlier than 6.9. + </p> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="sun_opt.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="changelog_6_0.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Sun Workshop Compiler Optimization + Level </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Berkeley DB Library Version 12.1.6.0 Change Log</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/dropsupp61.html b/docs/installation/dropsupp61.html new file mode 100644 index 00000000..938aad2c --- /dev/null +++ b/docs/installation/dropsupp61.html @@ -0,0 +1,64 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Dropped Support</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="prev" href="remlockdetect.html" title="Removed C# Class" /> + <link rel="next" href="changelog_6_1.html" title="Berkeley DB Library Version 12.1.6.1 Change Log" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Dropped Support</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="remlockdetect.html">Prev</a> </td> + <th width="60%" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + <td width="20%" align="right"> <a accesskey="n" href="changelog_6_1.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="dropsupp61"></a>Dropped Support</h2> + </div> + </div> + </div> + <p> + Berkeley DB no longer tests or certifies Windows XP or + Windows 2003. + </p> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="remlockdetect.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_61_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="changelog_6_1.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Removed C# Class </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Berkeley DB Library Version 12.1.6.1 Change Log</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/fcbc_notif.html b/docs/installation/fcbc_notif.html new file mode 100644 index 00000000..3db452dd --- /dev/null +++ b/docs/installation/fcbc_notif.html @@ -0,0 +1,129 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Failchk Broadcast Notifications</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="prev" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="next" href="log_nosync.html" title="New Logging Option" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Failchk Broadcast Notifications</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="upgrade_61_toc.html">Prev</a> </td> + <th width="60%" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + <td width="20%" align="right"> <a accesskey="n" href="log_nosync.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="fcbc_notif"></a>Failchk Broadcast Notifications</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="fcbc_notif.html#idp971040">New Parameter Value</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="fcbc_notif.html#idp920240">New Events</a> + </span> + </dt> + </dl> + </div> + <p> + The <a href="../api_reference/C/envfailchk.html" class="olink">DB_ENV->failchk()</a> method now has a new option to notify + environment processes of an application failure as soon + as possible. This option causes any thread waiting on a + mutex owned by a crashed process to return <a href="../programmer_reference/program_errorret.html#program_errorret.DB_RUNRECOVERY" class="olink"> + DB_RUNRECOVERY</a> instead of hanging. + </p> + <p> + This option is enabled at compile time with the new + configure option + <a class="link" href="build_unix_conf.html#build_unix_conf.--enable-failchk_broadcast"> + --enable-failchk_broadcast</a>. + When enabled, this option provides a new timeout. It also + provides new events that notify the application when a + thread is about to return <a href="../programmer_reference/program_errorret.html#program_errorret.DB_RUNRECOVERY" class="olink"> + DB_RUNRECOVERY</a>. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp971040"></a>New Parameter Value</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li><a href="../api_reference/C/envset_timeout.html#set_timeout_DB_SET_MUTEX_FAILCHK_TIMEOUT" class="olink">DB_SET_MUTEX_FAILCHK_TIMEOUT</a> — + A new <code class="literal">timeout</code> parameter value for the + <a href="../api_reference/C/envset_timeout.html" class="olink">DB_ENV->set_timeout()</a> method to indicate how long a thread + will wait for a mutex lock before checking whether + <a href="../api_reference/C/envfailchk.html" class="olink">DB_ENV->failchk()</a> has marked the mutex as failed. + </li> + </ul> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp920240"></a>New Events</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <a href="../api_reference/C/envevent_notify.html#event_notify_DB_EVENT_FAILCHK_PANIC" class="olink">DB_EVENT_FAILCHK_PANIC</a> + </li> + <li> + <a href="../api_reference/C/envevent_notify.html#event_notify_DB_EVENT_MUTEX_DIED" class="olink">DB_EVENT_MUTEX_DIED</a> + </li> + </ul> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="upgrade_61_toc.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_61_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="log_nosync.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> New Logging Option</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/index.html b/docs/installation/index.html index 1f212b7d..c835e6e4 100644 --- a/docs/installation/index.html +++ b/docs/installation/index.html @@ -12,7 +12,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> @@ -30,18 +30,18 @@ <div class="titlepage"> <div> <div> - <h1 class="title"><a id="idm665000"></a>Berkeley DB Installation and Build Guide</h1> + <h1 class="title"><a id="idm51394232"></a>Berkeley DB Installation and Build Guide</h1> </div> <div> <div class="legalnotice"> - <a id="idm1159184"></a> + <a id="idp53200"></a> <p class="legalnotice-title"> <b>Legal Notice</b> </p> </div> </div> <div> - <p class="pubdate">5/11/2012</p> + <p class="pubdate">2/17/2015</p> </div> </div> <hr /> @@ -100,16 +100,15 @@ </dd> <dt> <span class="chapter"> - <a href="install.html">2. - System Installation Notes - </a> + <a href="install.html">2. System Installation Notes </a> </span> </dt> <dd> <dl> <dt> <span class="sect1"> - <a href="install.html#install_file">File utility /etc/magic information</a> + <a href="install.html#install_file">File utility /etc/magic + information</a> </span> </dt> <dd> @@ -140,9 +139,7 @@ </dd> <dt> <span class="chapter"> - <a href="debug.html">3. - Debugging Applications - </a> + <a href="debug.html">3. Debugging Applications </a> </span> </dt> <dd> @@ -171,32 +168,32 @@ <dl> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1304224">Augmenting the Log for Debugging</a> + <a href="debug_printlog.html#idp164880">Augmenting the Log for Debugging</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1194048">Extracting Committed Transactions and Transaction Status</a> + <a href="debug_printlog.html#idp136104">Extracting Committed Transactions and Transaction Status</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1341784">Extracting Transaction Histories</a> + <a href="debug_printlog.html#idp166064">Extracting Transaction Histories</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm986800">Extracting File Histories</a> + <a href="debug_printlog.html#idp171384">Extracting File Histories</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm1437640">Extracting Page Histories</a> + <a href="debug_printlog.html#idp183288">Extracting Page Histories</a> </span> </dt> <dt> <span class="sect2"> - <a href="debug_printlog.html#idm680600">Other log processing tools</a> + <a href="debug_printlog.html#idp184088">Other log processing tools</a> </span> </dt> </dl> @@ -205,42 +202,50 @@ </dd> <dt> <span class="chapter"> - <a href="build_android_intro.html">4. Building Berkeley DB for Android</a> + <a href="build_android_intro.html">4. Building Berkeley DB for + Android</a> </span> </dt> <dd> <dl> <dt> <span class="sect1"> - <a href="build_android_intro.html#build_android">Building the Drop-In Replacement for Android</a> + <a href="build_android_intro.html#build_android">Building the Drop-In Replacement + for Android</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> - <a href="build_android_intro.html#build_android_migrate">Migrating from SQLite to Berkeley DB</a> + <a href="build_android_intro.html#build_android_migrate">Migrating from SQLite to + Berkeley DB</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> - <a href="build_android_jdbc.html">Building the Android JDBC Driver</a> + <a href="build_android_jdbc.html">Building the Android JDBC + Driver</a> </span> </dt> <dt> <span class="sect1"> - <a href="build_android_config.html">Android Configuration Options</a> + <a href="build_android_config.html">Android Configuration + Options</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="build_android_adfmobile.html">Using the JDBC Driver in ADF Mobile for Android</a> </span> </dt> </dl> </dd> <dt> <span class="chapter"> - <a href="build_win.html">5. - Building Berkeley DB for Windows - </a> + <a href="build_win.html">5. Building Berkeley DB for Windows </a> </span> </dt> <dd> @@ -254,22 +259,27 @@ <dl> <dt> <span class="sect2"> - <a href="build_win.html#idm1531520">Visual C++ .NET 2010</a> + <a href="build_win.html#idp283736">Visual C++ .NET 2012</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_win.html#idp270168">Visual C++ .NET 2010</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win.html#idm232112">Visual C++ .NET 2008</a> + <a href="build_win.html#idp285656">Visual C++ .NET 2008</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win.html#idm67456">Visual C++ .NET 2005</a> + <a href="build_win.html#idp292968">Visual C++ .NET 2005</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win.html#idm1085168">Build results</a> + <a href="build_win.html#idp295544">Build results</a> </span> </dt> </dl> @@ -283,7 +293,7 @@ <dl> <dt> <span class="sect2"> - <a href="win_build64.html#idm80112">x64 build with Visual Studio 2005 or newer</a> + <a href="win_build64.html#idp269712">x64 build with Visual Studio 2005 or newer</a> </span> </dt> </dl> @@ -322,18 +332,22 @@ <dl> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1386992">Binary Compatibility With SQLite</a> + <a href="build_win_sql.html#idp339096">Binary Compatibility With SQLite</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1146112">Setting Preprocessor Flags - </a> + <a href="build_win_sql.html#idp335872">Setting Encryption</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1193168">Enabling Extensions</a> + <a href="build_win_sql.html#idp265480">Changing Compile Options</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_win_sql.html#idp224800">Enabling Extensions</a> </span> </dt> <dt> @@ -348,18 +362,22 @@ </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm313872">Using the JDBC Driver</a> + <a href="build_win_sql.html#idp339720">Using the JDBC Driver</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm1594400">Building the ODBC Driver</a> + <a href="build_win_sql.html#idp367344">Using the JDBC Driver in ADF/JDeveloper</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_sql.html#idm313808"> Using the ADO.NET Driver - </a> + <a href="build_win_sql.html#idp375344">Building the ODBC Driver</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_win_sql.html#idp416760"> Using the ADO.NET Driver </a> </span> </dt> </dl> @@ -381,29 +399,33 @@ </dt> <dt> <span class="sect1"> - <a href="build_win_small.html">Building a small memory footprint library</a> + <a href="build_win_small.html">Building a small memory + footprint library</a> </span> </dt> <dt> <span class="sect1"> - <a href="build_win_test.html">Running the test suite under Windows</a> + <a href="build_win_test.html">Running the test suite under + Windows</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> - <a href="build_win_test.html#idp126120">Building the software needed by the tests</a> + <a href="build_win_test.html#idp458352">Building the software needed + by the tests</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_test.html#idp137576">Running the test suite under Windows</a> + <a href="build_win_test.html#idp389880">Running the test suite under Windows</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_win_test.html#build_win_test_sql">Building the software needed by the SQL tests</a> + <a href="build_win_test.html#build_win_test_sql">Building the software + needed by the SQL tests</a> </span> </dt> </dl> @@ -422,33 +444,32 @@ </dd> <dt> <span class="chapter"> - <a href="build_wince.html">6. - Building Berkeley DB for Windows Mobile - </a> + <a href="build_wince.html">6. Building Berkeley DB for Windows Mobile </a> </span> </dt> <dd> <dl> <dt> <span class="sect1"> - <a href="build_wince.html#build_wince_intro">Building for Windows Mobile</a> + <a href="build_wince.html#build_wince_intro">Building for Windows + Mobile</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> - <a href="build_wince.html#idm516512">Building Berkeley DB for Windows Mobile</a> + <a href="build_wince.html#idp475008">Building Berkeley DB for Windows Mobile</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_wince.html#idp180744">Changing Build Configuration Type</a> + <a href="build_wince.html#idp520696">Changing Build Configuration Type</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_wince.html#idp156256">Building Berkeley DB for different target platforms</a> + <a href="build_wince.html#build_wince_intro.add_platform">Building Berkeley DB for different target platforms</a> </span> </dt> </dl> @@ -463,13 +484,37 @@ <a href="build_wince_faq.html">Windows Mobile FAQ</a> </span> </dt> + <dt> + <span class="sect1"> + <a href="build_winec_intro.html">Building for Windows + Embedded Compact 7</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="build_winec_intro.html#idp578472">Building Berkeley DB for Windows Embedded Compact 7</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_winec_intro.html#idp570016">Changing Build Configuration Type</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="build_winec_intro.html#idp588240">Troubleshooting Common Build Errors</a> + </span> + </dt> + </dl> + </dd> </dl> </dd> <dt> <span class="chapter"> - <a href="build_unix.html">7. - Building Berkeley DB for UNIX/POSIX - </a> + <a href="build_unix.html">7. Building Berkeley DB for UNIX/POSIX + </a> </span> </dt> <dd> @@ -495,7 +540,8 @@ </dt> <dt> <span class="sect1"> - <a href="build_unix_sql.html">Configuring the SQL Interface</a> + <a href="build_unix_sql.html">Configuring the SQL + Interface</a> </span> </dt> <dd> @@ -507,7 +553,7 @@ </dt> <dt> <span class="sect2"> - <a href="build_unix_sql.html#idp249752">Enabling Extensions</a> + <a href="build_unix_sql.html#idp698856">Enabling Extensions</a> </span> </dt> <dt> @@ -517,12 +563,12 @@ </dt> <dt> <span class="sect2"> - <a href="build_unix_sql.html#idp327120">Using the JDBC Driver</a> + <a href="build_unix_sql.html#idp704816">Using the JDBC Driver</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_unix_sql.html#idp349152">Building the ODBC Driver</a> + <a href="build_unix_sql.html#idp736952">Building the ODBC Driver</a> </span> </dt> <dt> @@ -539,17 +585,20 @@ </dt> <dt> <span class="sect1"> - <a href="build_unix_flags.html">Changing compile or load options</a> + <a href="build_unix_flags.html">Changing compile or load + options</a> </span> </dt> <dt> <span class="sect1"> - <a href="cross_compile_unix.html">Cross-Compiling on Unix</a> + <a href="cross_compile_unix.html">Cross-Compiling on + Unix</a> </span> </dt> <dt> <span class="sect1"> - <a href="build_unix_install.html">Installing Berkeley DB</a> + <a href="build_unix_install.html">Installing Berkeley + DB</a> </span> </dt> <dt> @@ -559,7 +608,8 @@ </dt> <dt> <span class="sect1"> - <a href="build_unix_test.html">Running the test suite under UNIX</a> + <a href="build_unix_test.html">Running the test suite under + UNIX</a> </span> </dt> <dd> @@ -630,9 +680,7 @@ </dd> <dt> <span class="chapter"> - <a href="build_vxworks.html">8. - Building Berkeley DB for VxWorks - </a> + <a href="build_vxworks.html">8. Building Berkeley DB for VxWorks </a> </span> </dt> <dd> @@ -646,7 +694,8 @@ <dl> <dt> <span class="sect2"> - <a href="build_vxworks.html#idp182480">Building With Wind River Workbench using the Makefile</a> + <a href="build_vxworks.html#idp922392">Building With Wind + River Workbench using the Makefile</a> </span> </dt> </dl> @@ -660,17 +709,17 @@ <dl> <dt> <span class="sect2"> - <a href="build_vxworks_notes.html#idp491336">Building and Running the Demo Program</a> + <a href="build_vxworks_notes.html#idp934576">Building and Running the Demo Program</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_vxworks_notes.html#idp518216">Building and Running the Utility Programs</a> + <a href="build_vxworks_notes.html#idp896400">Building and Running the Utility Programs</a> </span> </dt> <dt> <span class="sect2"> - <a href="build_vxworks_notes.html#idp518576">Support for Replication Manager</a> + <a href="build_vxworks_notes.html#idp923512">Support for Replication Manager</a> </span> </dt> </dl> @@ -684,9 +733,526 @@ </dd> <dt> <span class="chapter"> - <a href="upgrade_53_toc.html">9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </a> + <a href="upgrade_61_toc.html">9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect1"> + <a href="upgrade_61_toc.html#upgrade_61_intro">Introduction</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="fcbc_notif.html">Failchk Broadcast Notifications</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="fcbc_notif.html#idp971040">New Parameter Value</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="fcbc_notif.html#idp920240">New Events</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="log_nosync.html">New Logging Option</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="log_nosync.html#idp954784">New Parameter Value</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="repmgr_prefmas.html">Replication Manager Preferred Master + Mode</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="repmgr_prefmas.html#idp972776">New Parameter Values</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="repmgr_inqueue.html">Replication Manager Incoming Queue + Size Limit</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="repmgr_inqueue.html#idp979760">New Functions</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="repmgr_inqueue.html#idp973032">New Event</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="blobdb_format.html">New Database Format for BLOBs</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="sqlite_ver61.html">Updated SQLite Version</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="sqlite_ver61.html#sqlite_db_upgrade_61">Upgrading SQL databases to releases after 6.1.19</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="remlockdetect.html">Removed C# Class</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="dropsupp61.html">Dropped Support</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="changelog_6_1.html">Berkeley DB Library Version 12.1.6.1 Change Log</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp987784">Changes between 12.1.6.1.20 and 12.1.6.1.23</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp988168">Changes between 12.1.6.1.19 and 12.1.6.1.20</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp973896">Database or Log File On-Disk Format Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1005736">New Features/Improvements</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1006120">Database Environment Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp991992">Concurrent Data Store Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1006184">Access Method Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1001712">API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1016544">SQL-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1006600">Tcl-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1021880">Java-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1023576">C#-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1024704">C++-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1022296">Replication Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1005576">Locking Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1028536">Logging Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1029168">Memory Pool Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1027200">Mutex Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1034480">Transaction Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1029552">Test Suite Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1031736">Utility Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1039888">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1039640">Example Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1039136">Miscellaneous Bug Fixes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1041536">Platform Certification Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1040680">Deprecated Features</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1043736">Known Bugs</a> + </span> + </dt> + </dl> + </dd> + </dl> + </dd> + <dt> + <span class="chapter"> + <a href="upgrade_60_toc.html">10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect1"> + <a href="upgrade_60_toc.html#upgrade_60_intro">Introduction</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="blob-support.html">Binary Large Object Support</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp865296">New Functions</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp998896">New Flags Accepted by Blob Streaming Interfaces</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp1063832">Other New Flags</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp1064912">New Pragma</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="rep_views.html">Replication Views</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="rep_views.html#idp988640">New Function</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="rep_views.html#idp1072824">New Flag</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="bdbsql_ha_more_options.html">Enhanced BDB SQL Replication Options</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="bdbsql_ha_more_options.html#idp1049920">New Pragmas</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="rep_auto_takeover.html">Replication Manager Automatic Takeover</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="rep_auto_takeover.html#idp1079576">New Event</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="sql_logbuf.html">New Berkeley DB SQL API Pragma</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="sql_logbuf.html#idp1083784">New Pragma</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="bdb_sql_encryption.html">UNIX/POSIX SQL Encryption Default</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="seq_datatype.html">Sequence Datatype Changes</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="compare_func.html">Comparison Function Signature Change</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="license_change60.html">License Change</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="sqlite_ver60.html">Updated SQLite Version</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="sun_opt.html">Sun Workshop Compiler Optimization + Level</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="drop_sup60.html">Dropped Support</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="changelog_6_0.html">Berkeley DB Library Version 12.1.6.0 Change Log</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1103464">Database or Log File On-Disk Format Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1085208">New Features</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1091952">Database Environment Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1109616">Concurrent Data Store Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1092040">Access Method Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1102752">API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1105448">SQL-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1118096">Tcl-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1103848">Java-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1108320">C#-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1118512">Replication Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1110216">Locking Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1117712">Logging Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1110304">Memory Pool Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1100424">Mutex Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1117416">Transaction Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1129976">Test Suite Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1127624">Utility Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1137784">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1130360">Example Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1140648">Miscellaneous Bug Fixes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1142544">Deprecated Features</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1143680">Known Bugs</a> + </span> + </dt> + </dl> + </dd> + </dl> + </dd> + <dt> + <span class="chapter"> + <a href="upgrade_53_toc.html">11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </a> </span> </dt> <dd> @@ -710,17 +1276,17 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_conn_status.html#idp506032">New Function</a> + <a href="upgrade_11gr2_53_conn_status.html#idp1160632">New Function</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_conn_status.html#idp531112">New Class</a> + <a href="upgrade_11gr2_53_conn_status.html#idp1116080">New Class</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_conn_status.html#idp564984">Deprecated Function</a> + <a href="upgrade_11gr2_53_conn_status.html#idp1164288">Deprecated Function</a> </span> </dt> </dl> @@ -734,7 +1300,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_excl.html#idp567208">New Functions</a> + <a href="upgrade_11gr2_53_excl.html#idp1166512">New Functions</a> </span> </dt> </dl> @@ -748,7 +1314,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_heap_regionsize.html#idp570008">New Functions</a> + <a href="upgrade_11gr2_53_heap_regionsize.html#idp1093968">New Functions</a> </span> </dt> </dl> @@ -762,22 +1328,22 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp571040">New Functions</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1170128">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp560912">Flags Accepted by DB_ENV->backup()</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1175656">Flags Accepted by DB_ENV->backup()</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp578624">Flags Accepted by DB_ENV->dbbackup()</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1177648">Flags Accepted by DB_ENV->dbbackup()</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp584448">Enumerations Accepted by DB_ENV->set_backup_config()</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1183112">Enumerations Accepted by DB_ENV->set_backup_config()</a> </span> </dt> </dl> @@ -796,7 +1362,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_meta_dir.html#idp593384">New Functions</a> + <a href="upgrade_11gr2_53_meta_dir.html#idp1192152">New Functions</a> </span> </dt> </dl> @@ -815,7 +1381,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_sql_pragma.html#idp599768">New PRAGMAs</a> + <a href="upgrade_11gr2_53_sql_pragma.html#idp1198640">New PRAGMAs</a> </span> </dt> </dl> @@ -829,12 +1395,12 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_sql_rep.html#idp593704">PRAGMAs With Permanent Effects</a> + <a href="upgrade_11gr2_53_sql_rep.html#idp1192472">PRAGMAs With Permanent Effects</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_sql_rep.html#idp600544">PRAGMAs That Can Now Operate on Existing Databases</a> + <a href="upgrade_11gr2_53_sql_rep.html#idp1199416">PRAGMAs That Can Now Operate on Existing Databases</a> </span> </dt> </dl> @@ -853,82 +1419,77 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp594928">Changes between 11.2.5.3.15 and 11.2.5.3.21</a> + <a href="changelog_5_3.html#idp1207192">Database or Log File On-Disk Format Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp608376">Database or Log File On-Disk Format Changes</a> + <a href="changelog_5_3.html#idp1200256">New Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp590024">New Features</a> + <a href="changelog_5_3.html#idp1206088">Database Environment Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp594216">Database Environment Changes</a> + <a href="changelog_5_3.html#idp1211048">Access Method Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp607088">Access Method Changes</a> + <a href="changelog_5_3.html#idp1208744">SQL API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp616640">SQL API Changes</a> + <a href="changelog_5_3.html#idp1199152">Java-specific API changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp610088">Java-specific API changes</a> + <a href="changelog_5_3.html#idp1208832">Replication Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp616728">Replication Changes</a> + <a href="changelog_5_3.html#idp1199992">Locking Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp594560">Locking Subsystem Changes</a> + <a href="changelog_5_3.html#idp1217800">Logging Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp635880">Logging Subsystem Changes</a> + <a href="changelog_5_3.html#idp1209392">Memory Pool Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp625488">Memory Pool Subsystem Changes</a> + <a href="changelog_5_3.html#idp1226336">Mutex Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp632288">Mutex Subsystem Changes</a> + <a href="changelog_5_3.html#idp1218216">Transaction Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp636296">Transaction Subsystem Changes</a> + <a href="changelog_5_3.html#idp1231856">Utility Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp625872">Utility Changes</a> + <a href="changelog_5_3.html#idp1226152">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp632040">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> - </span> - </dt> - <dt> - <span class="sect2"> - <a href="changelog_5_3.html#idp641456">Known Bugs</a> + <a href="changelog_5_3.html#idp1235024">Known Bugs</a> </span> </dt> </dl> @@ -937,9 +1498,7 @@ </dd> <dt> <span class="chapter"> - <a href="upgrade_52_toc.html">10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </a> + <a href="upgrade_52_toc.html">12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </a> </span> </dt> <dd> @@ -968,7 +1527,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_rep_dbt_readonly.html#idp654424">New Flag</a> + <a href="upgrade_11gr2_52_rep_dbt_readonly.html#idp1248208">New Flag</a> </span> </dt> </dl> @@ -982,12 +1541,12 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_dyn_env.html#idp611120">New Functions</a> + <a href="upgrade_11gr2_52_dyn_env.html#idp1243744">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_dyn_env.html#idp659088">Deprecated Functions</a> + <a href="upgrade_11gr2_52_dyn_env.html#idp1252704">Deprecated Functions</a> </span> </dt> </dl> @@ -1006,37 +1565,37 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp676752">Upgrading</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1270248">Upgrading</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp657144">New Functions</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1250760">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp655568">Modified Functions</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1249616">Modified Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp602496">New Events</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1129176">New Events</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp684960">Removed Functions</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1278544">Removed Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp650072">New Parameters</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1245336">New Parameters</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp671784">New Structure</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1265176">New Structure</a> </span> </dt> </dl> @@ -1050,17 +1609,17 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_heap.html#idp683880">New Functions</a> + <a href="upgrade_11gr2_52_heap.html#idp1277464">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_heap.html#idp677456">Modified Functions</a> + <a href="upgrade_11gr2_52_heap.html#idp1270952">Modified Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_heap.html#idp678808">New Definition</a> + <a href="upgrade_11gr2_52_heap.html#idp1272304">New Definition</a> </span> </dt> </dl> @@ -1074,7 +1633,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_mvcc_sql.html#idp698336">New Pragmas</a> + <a href="upgrade_11gr2_52_mvcc_sql.html#idp1291928">New Pragmas</a> </span> </dt> </dl> @@ -1093,7 +1652,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_rep_sql.html#idp709672">New Pragmas</a> + <a href="upgrade_11gr2_52_rep_sql.html#idp1303192">New Pragmas</a> </span> </dt> </dl> @@ -1107,21 +1666,22 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_repmgr_channels.html#idp704400">New Functions</a> + <a href="upgrade_11gr2_52_repmgr_channels.html#idp1249368">New Functions</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> - <a href="upgrade_11gr2_52_seq_sql.html">Sequence Support in the SQL Layer</a> + <a href="upgrade_11gr2_52_seq_sql.html">Sequence Support in the + SQL Layer</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_seq_sql.html#idp710392">New Functions</a> + <a href="upgrade_11gr2_52_seq_sql.html#idp1303976">New Functions</a> </span> </dt> </dl> @@ -1135,17 +1695,17 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_xa.html#idp720184">Constraints</a> + <a href="upgrade_11gr2_52_xa.html#idp1314200">Constraints</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_xa.html#idp725120">New Flag</a> + <a href="upgrade_11gr2_52_xa.html#idp1319928">New Flag</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_xa.html#idp729168">Modified Function</a> + <a href="upgrade_11gr2_52_xa.html#idp1324040">Modified Function</a> </span> </dt> </dl> @@ -1164,112 +1724,112 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp719568">Database or Log File On-Disk Format Changes</a> + <a href="changelog_5_2.html#idp1313480">Database or Log File On-Disk Format Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp725640">New Features</a> + <a href="changelog_5_2.html#idp1320448">New Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp731112">Database Environment Changes</a> + <a href="changelog_5_2.html#idp1304040">Database Environment Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp742672">Concurrent Data Store Changes</a> + <a href="changelog_5_2.html#idp1337840">Concurrent Data Store Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp736048">Access Method Changes</a> + <a href="changelog_5_2.html#idp1331240">Access Method Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp736464">SQL API Changes</a> + <a href="changelog_5_2.html#idp1319744">SQL API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp719112">C API Changes</a> + <a href="changelog_5_2.html#idp1312960">C API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp743448">Tcl-specific API Changes</a> + <a href="changelog_5_2.html#idp1338616">Tcl-specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp749040">C#-specific API Changes</a> + <a href="changelog_5_2.html#idp1313048">C#-specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp741376">Replication Changes</a> + <a href="changelog_5_2.html#idp1336544">Replication Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp743864">Locking Subsystem Changes</a> + <a href="changelog_5_2.html#idp1339000">Locking Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp749456">Logging Subsystem Changes</a> + <a href="changelog_5_2.html#idp1352672">Logging Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp763176">Memory Pool Subsystem Changes</a> + <a href="changelog_5_2.html#idp1334816">Memory Pool Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp765792">Mutex Subsystem Changes</a> + <a href="changelog_5_2.html#idp1360960">Mutex Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp766552">Transaction Subsystem Changes</a> + <a href="changelog_5_2.html#idp1353088">Transaction Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp763560">Test Suite Changes</a> + <a href="changelog_5_2.html#idp1345456">Test Suite Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp776568">Utility Changes</a> + <a href="changelog_5_2.html#idp1371840">Utility Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp766936">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> + <a href="changelog_5_2.html#idp1373456">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp780312">Example Changes</a> + <a href="changelog_5_2.html#idp1345232">Example Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp781208">Miscellaneous Bug Fixes</a> + <a href="changelog_5_2.html#idp1376368">Miscellaneous Bug Fixes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp782744">Deprecated Features</a> + <a href="changelog_5_2.html#idp1377904">Deprecated Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp785040">Known Bugs</a> + <a href="changelog_5_2.html#idp1379824">Known Bugs</a> </span> </dt> </dl> @@ -1278,9 +1838,7 @@ </dd> <dt> <span class="chapter"> - <a href="upgrade_51_toc.html">11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </a> + <a href="upgrade_51_toc.html">13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </a> </span> </dt> <dd> @@ -1319,122 +1877,122 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp799888">Database or Log File On-Disk Format Changes</a> + <a href="changelog_5_1.html#idp1395416">Database or Log File On-Disk Format Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp792216">New Features</a> + <a href="changelog_5_1.html#idp1335544">New Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp787976">Database Environment Changes</a> + <a href="changelog_5_1.html#idp1322264">Database Environment Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp806432">Concurrent Data Store Changes</a> + <a href="changelog_5_1.html#idp1402240">Concurrent Data Store Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp727768">Access Method Changes</a> + <a href="changelog_5_1.html#idp1322352">Access Method Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp795776">API Changes</a> + <a href="changelog_5_1.html#idp1395912">API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp802264">SQL-Specific API Changes</a> + <a href="changelog_5_1.html#idp1398072">SQL-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp803624">Tcl-Specific API Changes</a> + <a href="changelog_5_1.html#idp1399432">Tcl-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp799176">Java-Specific API Changes</a> + <a href="changelog_5_1.html#idp1394704">Java-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp734296">C#-Specific API Changes</a> + <a href="changelog_5_1.html#idp1391096">C#-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp807320">Direct Persistence Layer (DPL), Bindings and Collections API</a> + <a href="changelog_5_1.html#idp1412856">Direct Persistence Layer (DPL), Bindings and Collections API</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp816672">Replication Changes</a> + <a href="changelog_5_1.html#idp1412472">Replication Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp827552">Locking Subsystem Changes</a> + <a href="changelog_5_1.html#idp1423304">Locking Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp839224">Logging Subsystem Changes</a> + <a href="changelog_5_1.html#idp1436016">Logging Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp822992">Memory Pool Subsystem Changes</a> + <a href="changelog_5_1.html#idp1418744">Memory Pool Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp827368">Mutex Subsystem Changes</a> + <a href="changelog_5_1.html#idp1423120">Mutex Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp836200">Transaction Subsystem Changes</a> + <a href="changelog_5_1.html#idp1431840">Transaction Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp813832">Test Suite Changes</a> + <a href="changelog_5_1.html#idp1409688">Test Suite Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp834616">Utility Changes</a> + <a href="changelog_5_1.html#idp1430312">Utility Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp837928">Configuration, Documentation, Sample Apps, Portability, and Build Changes</a> + <a href="changelog_5_1.html#idp1433952">Configuration, Documentation, Sample Apps, Portability, and Build Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp828192">Example Changes</a> + <a href="changelog_5_1.html#idp1423944">Example Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp848592">Miscellaneous Bug Fixes</a> + <a href="changelog_5_1.html#idp1445752">Miscellaneous Bug Fixes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp846464">Deprecated Features</a> + <a href="changelog_5_1.html#idp1443624">Deprecated Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp847112">Known Bugs</a> + <a href="changelog_5_1.html#idp1444272">Known Bugs</a> </span> </dt> </dl> @@ -1443,9 +2001,7 @@ </dd> <dt> <span class="chapter"> - <a href="upgrade_11gr2_toc.html">12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </a> + <a href="upgrade_11gr2_toc.html">14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </a> </span> </dt> <dd> @@ -1499,22 +2055,22 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp872512">Changes between 11.2.5.0.26 and 11.2.5.0.32</a> + <a href="changelog_5_0.html#idp1469256">Changes between 11.2.5.0.26 and 11.2.5.0.32</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp863208">Changes between 11.2.5.0.21 and 11.2.5.0.26</a> + <a href="changelog_5_0.html#idp1470160">Changes between 11.2.5.0.21 and 11.2.5.0.26</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp851296">Changes between 4.8 and 11.2.5.0.21</a> + <a href="changelog_5_0.html#idp1448240">Changes between 4.8 and 11.2.5.0.21</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp883672">Known Bugs</a> + <a href="changelog_5_0.html#idp1481264">Known Bugs</a> </span> </dt> </dl> @@ -1523,7 +2079,7 @@ </dd> <dt> <span class="chapter"> - <a href="upgrade_4_8_toc.html">13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</a> + <a href="upgrade_4_8_toc.html">15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</a> </span> </dt> <dd> @@ -1562,183 +2118,183 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp908504"> + <a href="changelog_4_8.html#idp1293368"> Changes between 4.8.26 and 4.8.28:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp853904"> + <a href="changelog_4_8.html#idp1497568"> Known bugs in 4.8 </a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp885088"> + <a href="changelog_4_8.html#idp1482176"> Changes between 4.8.24 and 4.8.26:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp907544"> + <a href="changelog_4_8.html#idp1475624"> Changes between 4.8.21 and 4.8.24:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp853432"> + <a href="changelog_4_8.html#idp1553248"> Changes between 4.7 and 4.8.21:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp944680"> + <a href="changelog_4_8.html#idp1542376"> Database or Log File On-Disk Format Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp875992"> + <a href="changelog_4_8.html#idp1323496"> New Features:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp945096"> + <a href="changelog_4_8.html#idp1471240"> Database Environment Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp953944"> + <a href="changelog_4_8.html#idp1552400"> Concurrent Data Store Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp954344"> + <a href="changelog_4_8.html#idp1552800"> General Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp964688"> + <a href="changelog_4_8.html#idp1562416"> Btree Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp962400"> + <a href="changelog_4_8.html#idp1560192"> Hash Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp972744"> + <a href="changelog_4_8.html#idp1570528"> Queue Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp973816"> + <a href="changelog_4_8.html#idp1478984"> Recno Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp959840"> + <a href="changelog_4_8.html#idp1558464"> C-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp964968"> + <a href="changelog_4_8.html#idp1562696"> C++-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp985536"> + <a href="changelog_4_8.html#idp1583472"> Java-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp978792"> + <a href="changelog_4_8.html#idp1577104"> Direct Persistence Layer (DPL), Bindings and Collections API:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp979064"> + <a href="changelog_4_8.html#idp1576792"> Tcl-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp991048"> + <a href="changelog_4_8.html#idp1588984"> RPC-specific Client/Server Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp992632"> + <a href="changelog_4_8.html#idp1576880"> Replication Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp988920"> + <a href="changelog_4_8.html#idp1586856"> XA Resource Manager Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp994464"> + <a href="changelog_4_8.html#idp1592504"> Locking Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp987808"> + <a href="changelog_4_8.html#idp1585688"> Logging Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1005064"> + <a href="changelog_4_8.html#idp1603104"> Memory Pool Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1005456"> + <a href="changelog_4_8.html#idp1592944"> Mutex Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp987512"> + <a href="changelog_4_8.html#idp1585392"> Test Suite Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp996512"> + <a href="changelog_4_8.html#idp1594608"> Transaction Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1018456"> + <a href="changelog_4_8.html#idp1588800"> Utility Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1020896"> + <a href="changelog_4_8.html#idp1618888"> Configuration, Documentation, Sample Application, Portability and Build Changes:</a> </span> </dt> @@ -1748,9 +2304,7 @@ Configuration, Documentation, Sample Application, Portability and Build Changes: </dd> <dt> <span class="chapter"> - <a href="test.html">14. - Test Suite - </a> + <a href="test.html">16. Test Suite </a> </span> </dt> <dd> @@ -1764,12 +2318,12 @@ Configuration, Documentation, Sample Application, Portability and Build Changes: <dl> <dt> <span class="sect2"> - <a href="test.html#idp1045528">Running SQL Test Suite on Unix</a> + <a href="test.html#idp1643968">Running SQL Test Suite on Unix</a> </span> </dt> <dt> <span class="sect2"> - <a href="test.html#idp1036640">Running SQL Test Suite on Windows</a> + <a href="test.html#idp1634688">Running SQL Test Suite on Windows</a> </span> </dt> </dl> diff --git a/docs/installation/install.html b/docs/installation/install.html index 8c6471d5..706234d8 100644 --- a/docs/installation/install.html +++ b/docs/installation/install.html @@ -14,13 +14,11 @@ <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 2. - System Installation Notes - </th> + <th colspan="3" align="center">Chapter 2. System Installation Notes </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="ch01s02.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="install"></a>Chapter 2. - System Installation Notes - </h2> + <h2 class="title"><a id="install"></a>Chapter 2. System Installation Notes </h2> </div> </div> </div> @@ -47,7 +43,8 @@ <dl> <dt> <span class="sect1"> - <a href="install.html#install_file">File utility /etc/magic information</a> + <a href="install.html#install_file">File utility /etc/magic + information</a> </span> </dt> <dd> @@ -80,7 +77,8 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="install_file"></a>File utility /etc/magic information</h2> + <h2 class="title" style="clear: both"><a id="install_file"></a>File utility /etc/magic + information</h2> </div> </div> </div> @@ -104,28 +102,28 @@ </dl> </div> <p> - The <code class="literal">file</code>(1) utility is a UNIX utility that - examines and classifies files, based on information found in its - database of file types, the /etc/magic file. The following - information may be added to your system's /etc/magic file to enable - <code class="literal">file</code>(1) to correctly identify Berkeley DB - database files. + The <code class="literal">file</code>(1) utility is a UNIX utility + that examines and classifies files, based on information found + in its database of file types, the /etc/magic file. The + following information may be added to your system's /etc/magic + file to enable <code class="literal">file</code>(1) to correctly + identify Berkeley DB database files. </p> <p> - The <code class="literal">file</code>(1) utility <code class="literal">magic</code>(5) - information for the standard System V UNIX implementation of the - <code class="literal">file</code>(1) utility is included in the Berkeley DB - distribution for both big-endian (for example, Sparc) - and little-endian (for example, x86) architectures. - See <a class="xref" href="install.html#big-endian" title="Big-endian magic information">Big-endian magic information</a> - and <a class="xref" href="install.html#little-endian" title="Little-endian magic information">Little-endian magic information</a> + The <code class="literal">file</code>(1) utility + <code class="literal">magic</code>(5) information for the standard + System V UNIX implementation of the <code class="literal">file</code>(1) + utility is included in the Berkeley DB distribution for both + big-endian (for example, Sparc) and little-endian (for + example, x86) architectures. See <a class="xref" href="install.html#big-endian" title="Big-endian magic information">Big-endian magic information</a> and <a class="xref" href="install.html#little-endian" title="Little-endian magic information">Little-endian magic information</a> respectively for this information. </p> <p> - The <code class="literal">file</code>(1) utility <code class="literal">magic</code>(5) - information for Release 3.X of Ian Darwin's implementation of the - file utility (as distributed by FreeBSD and most Linux - distributions) is included in the Berkeley DB distribution. This + The <code class="literal">file</code>(1) utility + <code class="literal">magic</code>(5) information for Release 3.X of + Ian Darwin's implementation of the file utility (as + distributed by FreeBSD and most Linux distributions) is + included in the Berkeley DB distribution. This <code class="literal">magic.txt</code> information is correct for both big-endian and little-endian architectures. See the next section for this information. @@ -200,7 +198,7 @@ 12 belong 0x00040988 Berkeley DB >16 belong >0 (Log, version %d, big-endian) 12 lelong 0x00040988 Berkeley DB ->16 lelong >0 (Log, version %d, little-endian) </pre> +>16 lelong >0 (Log, version %d, little-endian) </pre> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> @@ -219,7 +217,7 @@ # Hash and Btree 2.X and later databases store the metadata in # host byte order. -0 long 0x00053162 Berkeley DB 1.85/1.86 (Btree, +0 long 0x00053162 Berkeley DB 1.85/1.86 (Btree, >4 long 0x00000002 version 2, >4 long 0x00000003 version 3, >0 long 0x00053162 native byte-order) diff --git a/docs/installation/install_multiple.html b/docs/installation/install_multiple.html index b9b74a0f..2adf7f65 100644 --- a/docs/installation/install_multiple.html +++ b/docs/installation/install_multiple.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="install.html">Prev</a> </td> - <th width="60%" align="center">Chapter 2. - System Installation Notes - </th> + <th width="60%" align="center">Chapter 2. System Installation Notes </th> <td width="20%" align="right"> <a accesskey="n" href="debug.html">Next</a></td> </tr> </table> @@ -38,39 +36,53 @@ </div> </div> </div> - <p>In some cases it may be necessary to build applications which include -multiple versions of Berkeley DB. Examples include applications which include -software from other vendors, or applications running on a system where -the system C library itself uses Berkeley DB. In such cases, the two versions -of Berkeley DB may be incompatible, that is, they may have different external -and internal interfaces, and may even have different underlying database -formats.</p> - <p>To create a Berkeley DB library whose symbols won't collide with other Berkeley DB -libraries (or other application or library modules, for that matter), -configure Berkeley DB using the <a class="link" href="build_unix_conf.html#build_unix_conf.--with-uniquename=NAME">--with-uniquename=NAME</a> configuration option, -and then build Berkeley DB as usual. (Note that -<a class="link" href="build_unix_conf.html#build_unix_conf.--with-uniquename=NAME">--with-uniquename=NAME</a> only affects the Berkeley DB C language library build; -loading multiple versions of the C++ or Java APIs will require -additional work.) The modified symbol names are hidden from the -application in the Berkeley DB header files, that is, there is no need for -the application to be aware that it is using a special library build as -long as it includes the appropriate Berkeley DB header file.</p> - <p>If "NAME" is not specified when configuring with -<a class="link" href="build_unix_conf.html#build_unix_conf.--with-uniquename=NAME">--with-uniquename=NAME</a>, a default value built from the major and minor -numbers of the Berkeley DB release will be used. It is rarely necessary to -specify NAME; using the major and minor release numbers will ensure that -only one copy of the library will be loaded into the application unless -two distinct versions really are necessary.</p> - <p>When distributing any library software that uses Berkeley DB, or any software -which will be recompiled by users for their systems, we recommend two -things: First, include the Berkeley DB release as part of your release. This -will insulate your software from potential Berkeley DB API changes as well as -simplifying your coding because you will only have to code to a single -version of the Berkeley DB API instead of adapting at compile time to whatever -version of Berkeley DB happens to be installed on the target system. Second, -use <a class="link" href="build_unix_conf.html#build_unix_conf.--with-uniquename=NAME">--with-uniquename=NAME</a> when configuring Berkeley DB, because that will insure that -you do not unexpectedly collide with other application code or a library -already installed on the target system.</p> + <p> + In some cases it may be necessary to build applications + which include multiple versions of Berkeley DB. Examples + include applications which include software from other + vendors, or applications running on a system where the system + C library itself uses Berkeley DB. In such cases, the two + versions of Berkeley DB may be incompatible, that is, they may + have different external and internal interfaces, and may even + have different underlying database formats. + </p> + <p> + To create a Berkeley DB library whose symbols won't collide + with other Berkeley DB libraries (or other application or + library modules, for that matter), configure Berkeley DB using + the <a class="link" href="build_unix_conf.html#build_unix_conf.--with-uniquename=NAME">--with-uniquename=NAME</a> + configuration option, and + then build Berkeley DB as usual. (Note that <a class="link" href="build_unix_conf.html#build_unix_conf.--with-uniquename=NAME">--with-uniquename=NAME</a> + only affects the Berkeley DB C language library build; loading multiple versions of the + C++ or Java APIs will require additional work.) The modified + symbol names are hidden from the application in the Berkeley + DB header files, that is, there is no need for the application + to be aware that it is using a special library build as long + as it includes the appropriate Berkeley DB header file. + </p> + <p> + If "NAME" is not specified when configuring with <a class="link" href="build_unix_conf.html#build_unix_conf.--with-uniquename=NAME">--with-uniquename=NAME</a>, + a default value built from the major and minor numbers of the Berkeley DB + release will be used. It is rarely necessary to specify NAME; using the major + and minor release numbers will ensure that only one copy of + the library will be loaded into the application unless two + distinct versions really are necessary. + </p> + <p> + When distributing any library software that uses Berkeley + DB, or any software which will be recompiled by users for + their systems, we recommend two things: First, include the + Berkeley DB release as part of your release. This will + insulate your software from potential Berkeley DB API changes + as well as simplifying your coding because you will only have + to code to a single version of the Berkeley DB API instead of + adapting at compile time to whatever version of Berkeley DB + happens to be installed on the target system. Second, use + <a class="link" href="build_unix_conf.html#build_unix_conf.--with-uniquename=NAME">--with-uniquename=NAME</a> + when configuring Berkeley DB, because that will insure that you do + not unexpectedly collide with other application code or a library already + installed on the target system. + </p> </div> <div class="navfooter"> <hr /> @@ -83,15 +95,11 @@ already installed on the target system.</p> <td width="40%" align="right"> <a accesskey="n" href="debug.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 2. - System Installation Notes - </td> + <td width="40%" align="left" valign="top">Chapter 2. System Installation Notes </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 3. - Debugging Applications - </td> + <td width="40%" align="right" valign="top"> Chapter 3. Debugging Applications </td> </tr> </table> </div> diff --git a/docs/installation/introduction.html b/docs/installation/introduction.html index ceba9c39..87fdabb0 100644 --- a/docs/installation/introduction.html +++ b/docs/installation/introduction.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> @@ -54,26 +54,25 @@ </dl> </div> <p> - Welcome to the Berkeley DB. This manual describes how to - configure, build and install Berkeley DB. Installation of DB - for all of the platforms it officially supports is described in - this manual. Upgrade instructions and release notes for newer - versions of this product are described here. For infomation on - upgrading from historical versions, see the - - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/upgrading/index.html" target="_top"> - Berkeley DB Upgrade Guide. - </a> - </p> - <p> - Note that some operating systems and distributions might - provide DB, either by default or as part of an installation - option. If so, those platforms will have installation - instructions for DB specific to them. In this situation, you should - see the documentation for your operating system or distribution - provider for information on how to get DB on your - platform. - </p> + Welcome to the Berkeley DB. This manual describes how to + configure, build and install Berkeley DB. Installation of + DB for all of the platforms it officially supports is + described in this manual. Upgrade instructions and release + notes for newer versions of this product are described here. + For infomation on upgrading from historical versions, see the + + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/upgrading/index.html" target="_top"> + Berkeley DB Upgrade Guide. </a> + </p> + <p> + Note that some operating systems and distributions might + provide DB, either by default or as part of an + installation option. If so, those platforms will have + installation instructions for DB specific to them. In this + situation, you should see the documentation for your operating + system or distribution provider for information on how to get + DB on your platform. + </p> <div class="sect1" lang="en" xml:lang="en"> <div class="titlepage"> <div> @@ -82,51 +81,47 @@ </div> </div> </div> - <p> - Berkeley DB is an open-source product, and as such it is - usually offered in source-code format. This means that - placing DB on your platform requires you to configure - the build scripts, compile it, and then install the product - onto your host system. The exception to this are Microsoft - Windows platforms for which a binary installer is - available. Note that for Windows platforms, you can still - compile the product from source if you desire. - </p> - <p> - For *nix systems, including the BSD and Linux systems, - the usual <code class="literal">configure</code>, <code class="literal">make</code> - and <code class="literal">make install</code> installation - process is used to place DB on your platform. - </p> - <p> - For information on building and installing Berkeley DB on: - </p> + <p> + Berkeley DB is an open-source product, and as such it is + usually offered in source-code format. This means that + placing DB on your platform requires you to configure + the build scripts, compile it, and then install the + product onto your host system. The exception to this are + Microsoft Windows platforms for which a binary installer + is available. Note that for Windows platforms, you can + still compile the product from source if you desire. + </p> + <p> + For *nix systems, including the BSD and Linux systems, + the usual <code class="literal">configure</code>, + <code class="literal">make</code> and <code class="literal">make + install</code> installation process is used to + place DB on your platform. + </p> + <p> + For information on building and installing Berkeley DB + on: + </p> <div class="itemizedlist"> <ul type="disc"> <li> <p> - Microsoft Windows, see <a class="xref" href="build_win.html" title="Chapter 5. Building Berkeley DB for Windows"> - Building Berkeley DB for Windows - </a> - or <a class="xref" href="build_wince.html" title="Chapter 6. Building Berkeley DB for Windows Mobile"> - Building Berkeley DB for Windows Mobile - </a>. - </p> + Microsoft Windows, see <a class="xref" href="build_win.html" title="Chapter 5. Building Berkeley DB for Windows"> Building Berkeley DB for Windows </a> + or <a class="xref" href="build_wince.html" title="Chapter 6. Building Berkeley DB for Windows Mobile"> Building Berkeley DB for Windows Mobile </a>. + </p> </li> <li> - <p> - Unix/POSIX — including Linux, BSD, Apple iOS (known as iPhone OS previously), and Mac OS X — see - <a class="xref" href="build_unix.html" title="Chapter 7. Building Berkeley DB for UNIX/POSIX"> - Building Berkeley DB for UNIX/POSIX - </a>. - </p> + <p> + Unix/POSIX — including Linux, BSD, Apple + iOS (known as iPhone OS previously), and Mac OS X + — see <a class="xref" href="build_unix.html" title="Chapter 7. Building Berkeley DB for UNIX/POSIX"> Building Berkeley DB for UNIX/POSIX + </a>. + </p> </li> <li> <p> - VxWorks, see <a class="xref" href="build_vxworks.html" title="Chapter 8. Building Berkeley DB for VxWorks"> - Building Berkeley DB for VxWorks - </a>. - </p> + VxWorks, see <a class="xref" href="build_vxworks.html" title="Chapter 8. Building Berkeley DB for VxWorks"> Building Berkeley DB for VxWorks </a>. + </p> </li> </ul> </div> diff --git a/docs/installation/license_change60.html b/docs/installation/license_change60.html new file mode 100644 index 00000000..8905b58a --- /dev/null +++ b/docs/installation/license_change60.html @@ -0,0 +1,72 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>License Change</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="compare_func.html" title="Comparison Function Signature Change" /> + <link rel="next" href="sqlite_ver60.html" title="Updated SQLite Version" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">License Change</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="compare_func.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="sqlite_ver60.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="license_change60"></a>License Change</h2> + </div> + </div> + </div> + <p> + Starting with the 6.0 / 12c releases, all Berkeley DB + products are licensed under the GNU AFFERO GENERAL PUBLIC + LICENSE (AGPL), version 3. This license is published by + the Free Software Foundation (FSF) <a class="ulink" href="http://www.gnu.org/licenses/agpl.html" target="_top">(1)</a> + and approved by the Open Source + Initiative <a class="ulink" href="http://opensource.org/licenses/AGPL-3.0" target="_top">(2) + </a>. Please review the terms of the license + to ensure compliance before upgrading to the 12c release. + Previous releases of Berkeley DB software will continue to + be distributed under the Sleepycat license. + </p> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="compare_func.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="sqlite_ver60.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Comparison Function Signature Change </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Updated SQLite Version</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/log_nosync.html b/docs/installation/log_nosync.html new file mode 100644 index 00000000..ec2a5f67 --- /dev/null +++ b/docs/installation/log_nosync.html @@ -0,0 +1,96 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>New Logging Option</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="prev" href="fcbc_notif.html" title="Failchk Broadcast Notifications" /> + <link rel="next" href="repmgr_prefmas.html" title="Replication Manager Preferred Master Mode" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">New Logging Option</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="fcbc_notif.html">Prev</a> </td> + <th width="60%" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + <td width="20%" align="right"> <a accesskey="n" href="repmgr_prefmas.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="log_nosync"></a>New Logging Option</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="log_nosync.html#idp954784">New Parameter Value</a> + </span> + </dt> + </dl> + </div> + <p> + A new logging configuration option has been added which + does not flush the transaction log from the operating + system cache to stable storage when a transaction commits + or the logging system switches log files. This can further + improve performance when all of the applications in an + environment use less-than-durable transactions + (<a href="../api_reference/C/envset_flags.html#envset_flags_DB_TXN_NOSYNC" class="olink">DB_TXN_NOSYNC</a> and <a href="../api_reference/C/envset_flags.html#set_flags_DB_TXN_WRITE_NOSYNC" class="olink">DB_TXN_WRITE_NOSYNC</a>). + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp954784"></a>New Parameter Value</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li><a href="../api_reference/C/envlog_set_config.html#log_set_config_DB_LOG_NOSYNC" class="olink">DB_LOG_NOSYNC</a> — A new + <code class="literal">flags</code> + parameter value for the <a href="../api_reference/C/envlog_set_config.html" class="olink">DB_ENV->log_set_config()</a> method. + </li> + </ul> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="fcbc_notif.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_61_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="repmgr_prefmas.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Failchk Broadcast Notifications </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Replication Manager Preferred Master + Mode</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/moreinfo.html b/docs/installation/moreinfo.html index f41ff6aa..09e91260 100644 --- a/docs/installation/moreinfo.html +++ b/docs/installation/moreinfo.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> @@ -45,72 +45,60 @@ </dt> </dl> </div> - <p> - Beyond this manual, you may also find the following sources of information useful when building a - DB application: + <p> + Beyond this manual, you may also find the following + sources of information useful when building a DB + application: </p> <div class="itemizedlist"> <ul type="disc"> <li> <p> - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/gsg_txn/C/index.html" target="_top"> - Getting Started with Transaction Processing for C + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/gsg_txn/C/index.html" target="_top"> Getting Started with Transaction Processing for C </a> </p> </li> <li> <p> - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/gsg_db_rep/C/index.html" target="_top"> - Berkeley DB Getting Started with Replicated Applications for C - </a> + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/gsg_db_rep/C/index.html" target="_top"> Berkeley DB Getting Started with Replicated Applications for C + </a> </p> </li> <li> <p> - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/api_reference/C/frame_main.html" target="_top"> - Berkeley DB C API Reference Guide - </a> - </p> + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/api_reference/C/frame_main.html" target="_top"> Berkeley DB C API Reference Guide </a> + </p> </li> <li> <p> - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/api_reference/CXX/frame_main.html" target="_top"> - Berkeley DB C++ API Reference Guide - </a> - </p> + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/api_reference/CXX/frame_main.html" target="_top"> Berkeley DB C++ API Reference Guide </a> + </p> </li> <li> <p> - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/api_reference/STL/frame_main.html" target="_top"> - Berkeley DB STL API Reference Guide - </a> - </p> + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/api_reference/STL/frame_main.html" target="_top"> Berkeley DB STL API Reference Guide </a> + </p> </li> <li> <p> - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/api_reference/TCL/frame_main.html" target="_top"> - Berkeley DB TCL API Reference Guide - </a> - </p> + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/api_reference/TCL/frame_main.html" target="_top"> Berkeley DB TCL API Reference Guide </a> + </p> </li> <li> <p> - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/programmer_reference/index.html" target="_top"> - Berkeley DB Programmer's Reference Guide + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/programmer_reference/index.html" target="_top"> Berkeley DB Programmer's Reference Guide </a> </p> </li> <li> <p> - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/upgrading/index.html" target="_top"> - Berkeley DB Upgrade Guide - </a> + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/upgrading/index.html" target="_top"> + Berkeley DB Upgrade Guide </a> </p> </li> <li> <p> - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/bdb-sql/index.html" target="_top"> - Berkeley DB Getting Started with the SQL APIs + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/bdb-sql/index.html" target="_top"> Berkeley DB Getting Started with the SQL APIs </a> </p> </li> @@ -131,7 +119,7 @@ downloads, visit - <a class="ulink" href="http://www.oracle.com/technetwork/database/berkeleydb/downloads/index.html" target="_top">http://www.oracle.com/technetwork/database/berkeleydb/downloads/index.html</a>. + <a class="ulink" href="http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index.html" target="_top">http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index.html</a>. </p> </span> <div class="sect2" lang="en" xml:lang="en"> diff --git a/docs/installation/preface.html b/docs/installation/preface.html index 67de3643..a647b5e3 100644 --- a/docs/installation/preface.html +++ b/docs/installation/preface.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> @@ -63,13 +63,13 @@ </dl> </div> <p> - Welcome to Berkeley DB (DB). This document describes how to - build, install and upgrade Berkeley DB - </p> - <p> - This document reflects Berkeley DB 11<span class="emphasis"><em>g</em></span> Release 2, which - provides DB library version 11.2.5.3. - </p> + Welcome to Berkeley DB (DB). This document describes how + to build, install and upgrade Berkeley DB + </p> + <p> + This document reflects Berkeley DB 12<span class="emphasis"><em>c</em></span> Release 1, which provides + DB library version 12.1.6.1. + </p> <div class="sect1" lang="en" xml:lang="en"> <div class="titlepage"> <div> @@ -78,23 +78,26 @@ </div> </div> </div> + <p> + The following typographical conventions are used within + in this manual: + </p> + <p> + Variable or non-literal text is presented in + <span class="emphasis"><em>italics</em></span>. For example: "Go to your + <span class="emphasis"><em>DB_INSTALL</em></span> directory." + </p> <p> - The following typographical conventions are used within in this manual: - </p> - <p> - Variable or non-literal text is presented in <span class="emphasis"><em>italics</em></span>. For example: - "Go to your <span class="emphasis"><em>DB_INSTALL</em></span> directory." - </p> - <p> - Program examples are displayed in a <code class="classname">monospaced font</code> on a shaded background. - For example: - </p> + Program examples are displayed in a + <code class="classname">monospaced font</code> on a shaded + background. For example: + </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> - <p> - Finally, notes of interest are represented using a note block such - as this. - </p> + <p> + Finally, notes of interest are represented using a + note block such as this. + </p> </div> </div> </div> diff --git a/docs/installation/remlockdetect.html b/docs/installation/remlockdetect.html new file mode 100644 index 00000000..61cc077d --- /dev/null +++ b/docs/installation/remlockdetect.html @@ -0,0 +1,65 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Removed C# Class</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="prev" href="sqlite_ver61.html" title="Updated SQLite Version" /> + <link rel="next" href="dropsupp61.html" title="Dropped Support" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Removed C# Class</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="sqlite_ver61.html">Prev</a> </td> + <th width="60%" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + <td width="20%" align="right"> <a accesskey="n" href="dropsupp61.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="remlockdetect"></a>Removed C# Class</h2> + </div> + </div> + </div> + <p> + The <code class="literal">LockDetectMode</code> C# class has been + removed as redundant. The same functionality is available + in other classes. + </p> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="sqlite_ver61.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_61_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="dropsupp61.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Updated SQLite Version </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Dropped Support</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/rep_auto_takeover.html b/docs/installation/rep_auto_takeover.html new file mode 100644 index 00000000..76d6afa8 --- /dev/null +++ b/docs/installation/rep_auto_takeover.html @@ -0,0 +1,95 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Replication Manager Automatic Takeover</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="bdbsql_ha_more_options.html" title="Enhanced BDB SQL Replication Options" /> + <link rel="next" href="sql_logbuf.html" title="New Berkeley DB SQL API Pragma" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Replication Manager Automatic Takeover</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="bdbsql_ha_more_options.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="sql_logbuf.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="rep_auto_takeover"></a>Replication Manager Automatic Takeover</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="rep_auto_takeover.html#idp1079576">New Event</a> + </span> + </dt> + </dl> + </div> + <p> + When running Replication Manager in multiple processes, + if the replication process terminates successfully and + there is an available subordinate process, a subordinate + process now automatically takes over as the new + replication process. The new + <code class="literal">DB_EVENT_REP_AUTOTAKEOVER_FAILED</code> + event informs the application when a takeover fails, + leaving the application without a replication process. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1079576"></a>New Event</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <code class="literal">DB_EVENT_REP_AUTOTAKEOVER_FAILED</code> + </li> + </ul> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="bdbsql_ha_more_options.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="sql_logbuf.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Enhanced BDB SQL Replication Options </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> New Berkeley DB SQL API Pragma</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/rep_views.html b/docs/installation/rep_views.html new file mode 100644 index 00000000..2f2d92c4 --- /dev/null +++ b/docs/installation/rep_views.html @@ -0,0 +1,116 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Replication Views</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="blob-support.html" title="Binary Large Object Support" /> + <link rel="next" href="bdbsql_ha_more_options.html" title="Enhanced BDB SQL Replication Options" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Replication Views</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="blob-support.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="bdbsql_ha_more_options.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="rep_views"></a>Replication Views</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="rep_views.html#idp988640">New Function</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="rep_views.html#idp1072824">New Flag</a> + </span> + </dt> + </dl> + </div> + <p> + A replication site can now be created as a replication + view by using the <a href="../api_reference/C/repset_view.html" class="olink">DB_ENV->rep_set_view()</a> method. A replication view + is a read-only copy of some or all of the replicated + databases that cannot become master, participate in + elections, or contribute to transaction durability. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp988640"></a>New Function</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <a href="../api_reference/C/repset_view.html" class="olink">DB_ENV->rep_set_view()</a> + </li> + </ul> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1072824"></a>New Flag</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li><code class="literal">DB_REPMGR_ISVIEW</code> - A new value + for the flags field of the + <code class="literal">DB_REPMGR_SITE</code> structures + returned by the <a href="../api_reference/C/repmgrsite_list.html" class="olink">DB_ENV->repmgr_site_list()</a> method to + indicate that a site is a replication view. + </li> + </ul> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="blob-support.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="bdbsql_ha_more_options.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Binary Large Object Support </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Enhanced BDB SQL Replication Options</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/repmgr_inqueue.html b/docs/installation/repmgr_inqueue.html new file mode 100644 index 00000000..e58f13db --- /dev/null +++ b/docs/installation/repmgr_inqueue.html @@ -0,0 +1,118 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Replication Manager Incoming Queue Size Limit</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="prev" href="repmgr_prefmas.html" title="Replication Manager Preferred Master Mode" /> + <link rel="next" href="blobdb_format.html" title="New Database Format for BLOBs" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Replication Manager Incoming Queue + Size Limit</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="repmgr_prefmas.html">Prev</a> </td> + <th width="60%" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + <td width="20%" align="right"> <a accesskey="n" href="blobdb_format.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="repmgr_inqueue"></a>Replication Manager Incoming Queue + Size Limit</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="repmgr_inqueue.html#idp979760">New Functions</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="repmgr_inqueue.html#idp973032">New Event</a> + </span> + </dt> + </dl> + </div> + <p> + Replication Manager now limits the amount of dynamic memory that + its incoming message queue can consume and provides new functions + to set and get this limit. There is also a new event that is + fired when the incoming message queue first becomes full. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp979760"></a>New Functions</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <a href="../api_reference/C/repmgrset_incoming_queue_max.html" class="olink">DB_ENV->repmgr_set_incoming_queue_max()</a> + </li> + <li> + <a href="../api_reference/C/repmgrget_incoming_queue_max.html" class="olink">DB_ENV->repmgr_get_incoming_queue_max()</a> + </li> + </ul> + </div> + </div> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp973032"></a>New Event</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <a href="../api_reference/C/envevent_notify.html#event_notify_DB_EVENT_REP_INQUEUE_FULL" class="olink">DB_EVENT_REP_INQUEUE_FULL</a> + </li> + </ul> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="repmgr_prefmas.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_61_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="blobdb_format.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Replication Manager Preferred Master + Mode </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> New Database Format for BLOBs</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/repmgr_prefmas.html b/docs/installation/repmgr_prefmas.html new file mode 100644 index 00000000..6afef5ff --- /dev/null +++ b/docs/installation/repmgr_prefmas.html @@ -0,0 +1,104 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Replication Manager Preferred Master Mode</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="prev" href="log_nosync.html" title="New Logging Option" /> + <link rel="next" href="repmgr_inqueue.html" title="Replication Manager Incoming Queue Size Limit" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Replication Manager Preferred Master + Mode</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="log_nosync.html">Prev</a> </td> + <th width="60%" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + <td width="20%" align="right"> <a accesskey="n" href="repmgr_inqueue.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="repmgr_prefmas"></a>Replication Manager Preferred Master + Mode</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="repmgr_prefmas.html#idp972776">New Parameter Values</a> + </span> + </dt> + </dl> + </div> + <p> + Replication Manager now supports preferred master + mode for two-site replication groups. In preferred master mode, + one site is the preferred master site, which operates as the + master as much of the time as its availability permits. The + other site is the client site, which takes over temporarily + as master when the preferred master site is unavailable. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp972776"></a>New Parameter Values</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li><a href="../api_reference/C/repconfig.html#config_DB_REPMGR_CONF_PREFMAS_MASTER" class="olink">DB_REPMGR_CONF_PREFMAS_MASTER</a> — A new + <code class="literal">which</code> + parameter value for the <a href="../api_reference/C/repconfig.html" class="olink">DB_ENV->rep_set_config()</a> method to indicate + that this site is the preferred master site. + </li> + <li><a href="../api_reference/C/repconfig.html#config_DB_REPMGR_CONF_PREFMAS_CLIENT" class="olink">DB_REPMGR_CONF_PREFMAS_CLIENT</a> — A new + <code class="literal">which</code> + parameter value for the <a href="../api_reference/C/repconfig.html" class="olink">DB_ENV->rep_set_config()</a> method to indicate + that this site is the client site in a preferred master + replication group. + </li> + </ul> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="log_nosync.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_61_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="repmgr_inqueue.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">New Logging Option </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Replication Manager Incoming Queue + Size Limit</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/seq_datatype.html b/docs/installation/seq_datatype.html new file mode 100644 index 00000000..e01ac67f --- /dev/null +++ b/docs/installation/seq_datatype.html @@ -0,0 +1,82 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Sequence Datatype Changes</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="bdb_sql_encryption.html" title="UNIX/POSIX SQL Encryption Default" /> + <link rel="next" href="compare_func.html" title="Comparison Function Signature Change" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Sequence Datatype Changes</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="bdb_sql_encryption.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="compare_func.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="seq_datatype"></a>Sequence Datatype Changes</h2> + </div> + </div> + </div> + <p> + The datatype for several pieces of information + associated with sequences has changed from + <code class="literal">int32_t</code> to + <code class="literal">u_int32_t</code>: + </p> + <div class="itemizedlist"> + <ul type="disc"> + <li><a href="../api_reference/C/seqget.html" class="olink">DB_SEQUENCE->get()</a><code class="literal"> delta</code> parameter + </li> + <li><a href="../api_reference/C/seqset_cachesize.html" class="olink">DB_SEQUENCE->set_cachesize()</a><code class="literal"> size</code> + parameter + </li> + <li><a href="../api_reference/C/seqget_cachesize.html" class="olink">DB_SEQUENCE->get_cachesize()</a><code class="literal"> sizep</code> + parameter + </li> + <li><code class="literal"> + st_cache_size</code> field of the + <code class="literal">DB_SEQUENCE_STAT</code> structure + </li> + </ul> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="bdb_sql_encryption.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="compare_func.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">UNIX/POSIX SQL Encryption Default </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Comparison Function Signature Change</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/sql_logbuf.html b/docs/installation/sql_logbuf.html new file mode 100644 index 00000000..9f250523 --- /dev/null +++ b/docs/installation/sql_logbuf.html @@ -0,0 +1,93 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>New Berkeley DB SQL API Pragma</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="rep_auto_takeover.html" title="Replication Manager Automatic Takeover" /> + <link rel="next" href="bdb_sql_encryption.html" title="UNIX/POSIX SQL Encryption Default" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">New Berkeley DB SQL API Pragma</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="rep_auto_takeover.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="bdb_sql_encryption.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="sql_logbuf"></a>New Berkeley DB SQL API Pragma</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="sql_logbuf.html#idp1083784">New Pragma</a> + </span> + </dt> + </dl> + </div> + <p> + The new Berkeley DB SQL API specific pragma + <code class="literal">bdbsql_log_buffer</code> has been added to + set the size of the Berkeley DB in-memory log buffer, in + bytes. This is useful for long-running transactions or + applications producing large amounts of data because a + larger log buffer can increase throughput. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="idp1083784"></a>New Pragma</h3> + </div> + </div> + </div> + <div class="itemizedlist"> + <ul type="disc"> + <li> + <code class="literal">PRAGMA bdbsql_log_buffer[=n]</code> + </li> + </ul> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="rep_auto_takeover.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="bdb_sql_encryption.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Replication Manager Automatic Takeover </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> UNIX/POSIX SQL Encryption Default</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/sqlite_ver60.html b/docs/installation/sqlite_ver60.html new file mode 100644 index 00000000..c256d276 --- /dev/null +++ b/docs/installation/sqlite_ver60.html @@ -0,0 +1,68 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Updated SQLite Version</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="license_change60.html" title="License Change" /> + <link rel="next" href="sun_opt.html" title="Sun Workshop Compiler Optimization Level" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Updated SQLite Version</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="license_change60.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="sun_opt.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="sqlite_ver60"></a>Updated SQLite Version</h2> + </div> + </div> + </div> + <p> + Berkeley DB's SQL interface includes code from SQLite. + The version of SQLite used has been upgraded, so that + Berkeley DB SQL is now compatible with SQLite version + 3.7.16.2. Please see the release notes at <a class="ulink" href="http://sqlite.org/changes.html" target="_top">http://sqlite.org/changes.html</a> for further + information. + </p> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="license_change60.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="sun_opt.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">License Change </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Sun Workshop Compiler Optimization + Level</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/sqlite_ver61.html b/docs/installation/sqlite_ver61.html new file mode 100644 index 00000000..bdd69cb7 --- /dev/null +++ b/docs/installation/sqlite_ver61.html @@ -0,0 +1,190 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Updated SQLite Version</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_61_toc.html" title="Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1" /> + <link rel="prev" href="blobdb_format.html" title="New Database Format for BLOBs" /> + <link rel="next" href="remlockdetect.html" title="Removed C# Class" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Updated SQLite Version</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="blobdb_format.html">Prev</a> </td> + <th width="60%" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + <td width="20%" align="right"> <a accesskey="n" href="remlockdetect.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="sqlite_ver61"></a>Updated SQLite Version</h2> + </div> + </div> + </div> + <div class="toc"> + <dl> + <dt> + <span class="sect2"> + <a href="sqlite_ver61.html#sqlite_db_upgrade_61">Upgrading SQL databases to releases after 6.1.19</a> + </span> + </dt> + </dl> + </div> + <p> + Berkeley DB's SQL interface includes code from SQLite. + The version of SQLite used has been upgraded, so that + Berkeley DB SQL is now compatible with SQLite version + 3.8.3.1. Please see the release notes at <a class="ulink" href="http://sqlite.org/changes.html" target="_top">http://sqlite.org/changes.html</a> for further + information. + </p> + <div class="sect2" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h3 class="title"><a id="sqlite_db_upgrade_61"></a>Upgrading SQL databases to releases after 6.1.19</h3> + </div> + </div> + </div> + <p> + When upgrading from Berkeley DB releases between 5.0 and + 6.1.19 to a release after 6.1.19, you must re-index any SQL + databases. Non-SQL databases do not require any action. + </p> + <div class="sect3" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h4 class="title"><a id="sqlite_db_upgrade_posix"></a>Upgrading SQL databases on POSIX/UNIX Systems</h4> + </div> + </div> + </div> + <p> + The shell script <code class="literal">upgrade61.sh</code> has + been provided to simplify upgrading. Before executing + the script, back up all the databases and shut down any + applications that access the databases. Then execute + the script, passing the path to one or more databases + in the command line, as follows: + </p> + <pre class="programlisting">sh db-x.x.xx/lang/sql/upgrade61.sh <db1.dbsql> <db2.dbsql> ...</pre> + <p> + The upgrade process can be done by hand by executing + the following commands for each database: + </p> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Back up the database and shut down any + applications accessing it. + </p> + </li> + <li> + <p> + Run recovery on the database journal directory as follows: + </p> + <pre class="programlisting">db_recover -f -h <database-journal></pre> + </li> + <li> + <p> + Enter the dbsql shell and execute a SQL REINDEX + command as follows: + </p> + <pre class="programlisting">dbsql <database.dbsql> +dbsql> REINDEX +dbsql> .quit </pre> + </li> + </ol> + </div> + <p> + That completes the upgrade process. + </p> + </div> + <div class="sect3" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h4 class="title"><a id="sqlite_db_upgrade_win"></a>Upgrading SQL databases on Windows Systems</h4> + </div> + </div> + </div> + <p> + The batch script "upgrade61.bat" has been provided to + simplify upgrading. Before executing the script, back + up all the databases and shut down any applications + that access the databases. Then execute the script, + passing the path to one or more databases in the + command line, as follows: + </p> + <pre class="programlisting">db-x.x.xx\lang\sql\upgrade61.bat <db1.dbsql> <db2.dbsql> ...</pre> + <p> + The upgrade process can be done by hand by executing + the following commands for each database: + </p> + <div class="orderedlist"> + <ol type="1"> + <li> + <p> + Back up the database and shut down any + applications accessing it. + </p> + </li> + <li> + <p> + Run recovery on the database journal directory as follows: + </p> + <pre class="programlisting">db_recover.exe -f -h <database-journal></pre> + </li> + <li> + <p> + Enter the dbsql shell and execute a SQL REINDEX + command as follows: + </p> + <pre class="programlisting">dbsql.exe <database.dbsql> +dbsql> REINDEX +dbsql> .quit </pre> + </li> + </ol> + </div> + <p> + That completes the upgrade process. + </p> + </div> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="blobdb_format.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_61_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="remlockdetect.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">New Database Format for BLOBs </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Removed C# Class</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/sun_opt.html b/docs/installation/sun_opt.html new file mode 100644 index 00000000..470656a3 --- /dev/null +++ b/docs/installation/sun_opt.html @@ -0,0 +1,71 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Sun Workshop Compiler Optimization Level</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="upgrade_60_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0" /> + <link rel="prev" href="sqlite_ver60.html" title="Updated SQLite Version" /> + <link rel="next" href="drop_sup60.html" title="Dropped Support" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Sun Workshop Compiler Optimization + Level</th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="sqlite_ver60.html">Prev</a> </td> + <th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + <td width="20%" align="right"> <a accesskey="n" href="drop_sup60.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="sun_opt"></a>Sun Workshop Compiler Optimization + Level</h2> + </div> + </div> + </div> + <p> + Berkeley DB now automatically uses optimization level + <code class="literal">"-xO2"</code> with the Sun Workshop + compiler. Test failures have been observed with higher + optimization levels. This can include the default + <code class="literal">"-O"</code>, which equates to the higher + <code class="literal">"-xO3"</code> optimization level for some + Sun compilers. + </p> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="sqlite_ver60.html">Prev</a> </td> + <td width="20%" align="center"> + <a accesskey="u" href="upgrade_60_toc.html">Up</a> + </td> + <td width="40%" align="right"> <a accesskey="n" href="drop_sup60.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Updated SQLite Version </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Dropped Support</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/test.html b/docs/installation/test.html index 722edaeb..863b5628 100644 --- a/docs/installation/test.html +++ b/docs/installation/test.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> - <title>Chapter 14. Test Suite</title> + <title>Chapter 16. Test Suite</title> <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> @@ -14,13 +14,11 @@ <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 14. - Test Suite - </th> + <th colspan="3" align="center">Chapter 16. Test Suite </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="changelog_4_8.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="test"></a>Chapter 14. - Test Suite - </h2> + <h2 class="title"><a id="test"></a>Chapter 16. Test Suite </h2> </div> </div> </div> @@ -54,12 +50,12 @@ <dl> <dt> <span class="sect2"> - <a href="test.html#idp1045528">Running SQL Test Suite on Unix</a> + <a href="test.html#idp1643968">Running SQL Test Suite on Unix</a> </span> </dt> <dt> <span class="sect2"> - <a href="test.html#idp1036640">Running SQL Test Suite on Windows</a> + <a href="test.html#idp1634688">Running SQL Test Suite on Windows</a> </span> </dt> </dl> @@ -83,111 +79,148 @@ <dl> <dt> <span class="sect2"> - <a href="test.html#idp1045528">Running SQL Test Suite on Unix</a> + <a href="test.html#idp1643968">Running SQL Test Suite on Unix</a> </span> </dt> <dt> <span class="sect2"> - <a href="test.html#idp1036640">Running SQL Test Suite on Windows</a> + <a href="test.html#idp1634688">Running SQL Test Suite on Windows</a> </span> </dt> </dl> </div> - <p>Once you have started tclsh and have loaded the test.tcl source file -(see <a class="xref" href="build_unix_test.html" title="Running the test suite under UNIX">Running the test suite under UNIX</a> and -<a class="xref" href="build_win_test.html" title="Running the test suite under Windows">Running the test suite under Windows</a> for more information), -you are ready to run the test -suite. At the tclsh prompt, to run the standard test suite, enter the -following:</p> + <p> + Once you have started tclsh and have loaded the test.tcl + source file (see <a class="xref" href="build_unix_test.html" title="Running the test suite under UNIX">Running the test suite under + UNIX</a> and <a class="xref" href="build_win_test.html" title="Running the test suite under Windows">Running the test suite under + Windows</a> + for more information), you are ready to run the test suite. At + the tclsh prompt, to run the standard test suite, enter the + following: + </p> <pre class="programlisting">% run_std</pre> - <p>A more exhaustive version of the test suite runs all the tests several -more times, testing encryption, replication, and different page sizes. -After you have a clean run for run_std, you may choose to run this -lengthier set of tests. At the tclsh prompt, enter:</p> + <p> + A more exhaustive version of the test suite runs all the + tests several more times, testing encryption, replication, and + different page sizes. After you have a clean run for run_std, + you may choose to run this lengthier set of tests. At the + tclsh prompt, enter: + </p> <pre class="programlisting">% run_all</pre> - <p>Running the standard tests can take from several hours to a few days to -complete, depending on your hardware, and running all the tests will -take at least twice as long. For this reason, the output from these -commands are redirected to a file in the current directory named -<code class="filename">ALL.OUT</code>. Periodically, a line will be written to the standard -output, indicating what test is being run. When the test suite has -finished, a final message will be written indicating the test suite has -completed successfully or that it has failed. If the run failed, you -should review the <code class="filename">ALL.OUT</code> file to determine which tests failed. -Errors will appear in that file as output lines, beginning with the -string "FAIL".</p> - <p>Tests are run in the directory <code class="filename">TESTDIR</code>, by default. However, -the test files are often large, and you should use a filesystem with at -least several hundred megabytes of free space. To use a different -directory for the test directory, edit the file include.tcl in your -build directory, and change the following line to a more appropriate -value for your system:</p> + <p> + Running the standard tests can take from several hours to a + few days to complete, depending on your hardware, and running + all the tests will take at least twice as long. For this + reason, the output from these commands are redirected to a + file in the current directory named + <code class="filename">ALL.OUT</code>. Periodically, a line will be + written to the standard output, indicating what test is being + run. When the test suite has finished, a final message will be + written indicating the test suite has completed successfully + or that it has failed. If the run failed, you should review + the <code class="filename">ALL.OUT</code> file to determine which tests + failed. Errors will appear in that file as output lines, + beginning with the string "FAIL". + </p> + <p> + Tests are run in the directory <code class="filename">TESTDIR</code>, + by default. However, the test files are often large, and you + should use a filesystem with at least several hundred + megabytes of free space. To use a different directory for the + test directory, edit the file include.tcl in your build + directory, and change the following line to a more appropriate + value for your system: + </p> <pre class="programlisting">set testdir ./TESTDIR</pre> - <p>For example, you might change it to the following:</p> + <p> + For example, you might change it to the following: + </p> <pre class="programlisting">set testdir /var/tmp/db.test</pre> - <p>Alternatively, you can create a symbolic link named TESTDIR in your -build directory to an appropriate location for running the tests. -Regardless of where you run the tests, the TESTDIR directory should be -on a local filesystem. Using a remote filesystem (for example, an NFS -mounted filesystem) will almost certainly cause spurious test -failures.</p> + <p> + Alternatively, you can create a symbolic link named TESTDIR + in your build directory to an appropriate location for running + the tests. Regardless of where you run the tests, the TESTDIR + directory should be on a local filesystem. Using a remote + filesystem (for example, an NFS mounted filesystem) will + almost certainly cause spurious test failures. + </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp1045528"></a>Running SQL Test Suite on Unix</h3> + <h3 class="title"><a id="idp1643968"></a>Running SQL Test Suite on Unix</h3> </div> </div> </div> <p> - Once the test suite is built (see <a class="xref" href="build_unix_test.html#build_unix_test_sql" title="Building SQL Test Suite on Unix">Building SQL Test Suite on Unix</a> for more information), run the entire test suite by executing the following command in the <code class="literal">../build_unix/sql</code> directory: - </p> + Once the test suite is built (see <a class="xref" href="build_unix_test.html#build_unix_test_sql" title="Building SQL Test Suite on Unix">Building SQL Test Suite on Unix</a> for more + information), run the entire test suite by executing the + following command in the + <code class="literal">../build_unix/sql</code> directory: + </p> <pre class="programlisting"> -sh ../../test/sql/bdb-test.sh +sh ../../sql/adapter/bdb-test.sh </pre> <p> -This runs a set of tests and lists the errors each test encountered, if any. A detailed list of the test results is written to <code class="literal">test.log</code>. -</p> - <p>To run an individual test, such as insert.test, execute the following command in the <code class="literal">../build_unix/sql</code> directory: -</p> + This runs a set of tests and lists the errors each test + encountered, if any. A detailed list of the test results + is written to <code class="literal">test.log</code>. + </p> + <p> + To run an individual test, such as insert.test, execute + the following command in the + <code class="literal">../build_unix/sql</code> directory: + </p> <pre class="programlisting"> -./testfixture ../../lang/sql/sqlite/test/insert.test +./textfixture ../../sql/sqlite/test/insert.test </pre> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp1036640"></a>Running SQL Test Suite on Windows</h3> + <h3 class="title"><a id="idp1634688"></a>Running SQL Test Suite on Windows</h3> </div> </div> </div> <p> - After the test suite is built (see <a class="xref" href="build_win_test.html#build_win_test_sql" title="Building the software needed by the SQL tests">Building the software needed by the SQL tests</a> for more information) and before running the entire test suite, go to <code class="literal">../sql/adapter/bdb-test.sh</code> and edit the line: - </p> + After the test suite is built (see <a class="xref" href="build_win_test.html#build_win_test_sql" title="Building the software needed by the SQL tests">Building the software + needed by the SQL tests</a> for more + information) and before running the entire test suite, go + to <code class="literal">../sql/adapter/bdb-test.sh</code> and edit + the line: + </p> <pre class="programlisting"> echo $t: `alarm $TIMEOUT ./testfixture.exe $tpath 2>&1 | tee -a test.log | grep "errors out of" || echo "failed"` </pre> - <p>to</p> + <p> + to + </p> <pre class="programlisting"> echo $t: `alarm $TIMEOUT Win32/Debug/testfixture.exe $tpath 2>&1 | tee -a test.log | grep "errors out of" || echo "failed"` </pre> - <p>Running the test suite requires an Unix emulator, such as Cygwin. In a Cygwin window go to the <code class="literal">../build_windows</code> directory and execute the command: -</p> - <pre class="programlisting"> -sh ../sql/adapter/bdb-test.sh -</pre> - <p>This runs a set of tests and lists errors that each test encountered, if any. A detailed list of the test results is written to <code class="literal">test.log</code>. -</p> - <p>To run an individual test, such as insert.test, execute the following command in the <code class="literal">../build_windows</code> directory: -</p> - <pre class="programlisting"> -Win32/Debug/testfixture.exe ../sql/sqlite/test/insert.test -</pre> + <p> + Running the test suite requires an Unix emulator, such + as Cygwin. In a Cygwin window go to the + <code class="literal">../build_windows</code> directory and + execute the command: + </p> + <pre class="programlisting">sh ../sql/adapter/bdb-test.sh</pre> + <p> + This runs a set of tests and lists errors that each test + encountered, if any. A detailed list of the test results + is written to <code class="literal">test.log</code>. + </p> + <p> + To run an individual test, such as insert.test, execute + the following command in the + <code class="literal">../build_windows</code> directory: + </p> + <pre class="programlisting">Win32/Debug/testfixture.exe ../sql/sqlite/test/insert.test </pre> </div> </div> </div> diff --git a/docs/installation/test_faq.html b/docs/installation/test_faq.html index 9a265cb5..7c522750 100644 --- a/docs/installation/test_faq.html +++ b/docs/installation/test_faq.html @@ -7,13 +7,13 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="test.html" title="Chapter 14. Test Suite" /> - <link rel="prev" href="test.html" title="Chapter 14. Test Suite" /> + <link rel="up" href="test.html" title="Chapter 16. Test Suite" /> + <link rel="prev" href="test.html" title="Chapter 16. Test Suite" /> </head> <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> @@ -21,9 +21,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="test.html">Prev</a> </td> - <th width="60%" align="center">Chapter 14. - Test Suite - </th> + <th width="60%" align="center">Chapter 16. Test Suite </th> <td width="20%" align="right"> </td> </tr> </table> @@ -41,12 +39,17 @@ <ol type="1"> <li> <span class="bold"> - <strong>The test suite has been running for over a day. What's wrong?</strong> + <strong>The test suite has been running for + over a day. What's wrong?</strong> </span> - <p>The test suite can take anywhere from some number of hours to several -days to run, depending on your hardware configuration. As long as the -run is making forward progress and new lines are being written to the -<code class="filename">ALL.OUT</code> files, everything is probably fine.</p> + <p> + The test suite can take anywhere from some number of + hours to several days to run, depending on your + hardware configuration. As long as the run is making + forward progress and new lines are being written to + the <code class="filename">ALL.OUT</code> files, everything is + probably fine. + </p> </li> </ol> </div> @@ -62,9 +65,7 @@ run is making forward progress and new lines are being written to the <td width="40%" align="right"> </td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 14. - Test Suite - </td> + <td width="40%" align="left" valign="top">Chapter 16. Test Suite </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/upgrade_11gr2_51_dpl_recompile.html b/docs/installation/upgrade_11gr2_51_dpl_recompile.html index 5e68da73..27c71c79 100644 --- a/docs/installation/upgrade_11gr2_51_dpl_recompile.html +++ b/docs/installation/upgrade_11gr2_51_dpl_recompile.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_51_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> - <link rel="prev" href="upgrade_51_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> + <link rel="up" href="upgrade_51_toc.html" title="Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> + <link rel="prev" href="upgrade_51_toc.html" title="Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> <link rel="next" href="upgrade_11gr2_51_src_reorg.html" title="Source Tree Rearranged" /> </head> <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="upgrade_51_toc.html">Prev</a> </td> - <th width="60%" align="center">Chapter 11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </th> + <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_51_src_reorg.html">Next</a></td> </tr> </table> @@ -39,12 +37,13 @@ </div> </div> <p> -Applications that use the Java interface's <span class="emphasis"><em>Direct -Persistence Layer</em></span> must be recompiled, due to a change in -the return type of the setter methods in StoreConfig and EvolveConfig -classes. The setter methods now return <code class="literal">this</code> -instead of <code class="literal">void</code>. -</p> + Applications that use the Java interface's <span class="emphasis"><em>Direct + Persistence Layer</em></span> must be recompiled, due to a + change in the return type of the setter methods in StoreConfig + and EvolveConfig classes. The setter methods now return + <code class="literal">this</code> instead of + <code class="literal">void</code>. + </p> </div> <div class="navfooter"> <hr /> @@ -57,9 +56,7 @@ instead of <code class="literal">void</code>. <td width="40%" align="right"> <a accesskey="n" href="upgrade_11gr2_51_src_reorg.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </td> + <td width="40%" align="left" valign="top">Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/upgrade_11gr2_51_mod_db4_unsupp.html b/docs/installation/upgrade_11gr2_51_mod_db4_unsupp.html index 2c329096..bb95b438 100644 --- a/docs/installation/upgrade_11gr2_51_mod_db4_unsupp.html +++ b/docs/installation/upgrade_11gr2_51_mod_db4_unsupp.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_51_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> + <link rel="up" href="upgrade_51_toc.html" title="Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> <link rel="prev" href="upgrade_11gr2_51_sqlite_ver.html" title="SQLite Interface Upgrade" /> <link rel="next" href="changelog_5_1.html" title="Berkeley DB Library Version 11.2.5.1 Change Log" /> </head> <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="upgrade_11gr2_51_sqlite_ver.html">Prev</a> </td> - <th width="60%" align="center">Chapter 11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </th> + <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </th> <td width="20%" align="right"> <a accesskey="n" href="changelog_5_1.html">Next</a></td> </tr> </table> @@ -38,9 +36,10 @@ </div> </div> </div> - <p> -The mod_db4 apache module is no longer included in the release. -</p> + <p> + The mod_db4 apache module is no longer included in the + release. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/upgrade_11gr2_51_sqlite_ver.html b/docs/installation/upgrade_11gr2_51_sqlite_ver.html index cb42d602..6ad3708f 100644 --- a/docs/installation/upgrade_11gr2_51_sqlite_ver.html +++ b/docs/installation/upgrade_11gr2_51_sqlite_ver.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_51_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> + <link rel="up" href="upgrade_51_toc.html" title="Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> <link rel="prev" href="upgrade_11gr2_51_src_reorg.html" title="Source Tree Rearranged" /> <link rel="next" href="upgrade_11gr2_51_mod_db4_unsupp.html" title="Mod_db4 Support Discontinued" /> </head> <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="upgrade_11gr2_51_src_reorg.html">Prev</a> </td> - <th width="60%" align="center">Chapter 11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </th> + <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_51_mod_db4_unsupp.html">Next</a></td> </tr> </table> @@ -39,11 +37,12 @@ </div> </div> <p> -Berkeley DB's SQL interface includes code from SQLite. The version of -SQLite used has been upgraded, so DB SQL is compatible -with SQLite version 3.7.0.1. Please see the release notes at -http://sqlite.org/changes.html for further information. -</p> + Berkeley DB's SQL interface includes code from SQLite. The + version of SQLite used has been upgraded, so DB SQL is + compatible with SQLite version 3.7.0.1. Please see the release + notes at http://sqlite.org/changes.html for further + information. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/upgrade_11gr2_51_src_reorg.html b/docs/installation/upgrade_11gr2_51_src_reorg.html index 692828e6..0bf0ed37 100644 --- a/docs/installation/upgrade_11gr2_51_src_reorg.html +++ b/docs/installation/upgrade_11gr2_51_src_reorg.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_51_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> + <link rel="up" href="upgrade_51_toc.html" title="Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1" /> <link rel="prev" href="upgrade_11gr2_51_dpl_recompile.html" title="DPL Applications must be recompiled" /> <link rel="next" href="upgrade_11gr2_51_sqlite_ver.html" title="SQLite Interface Upgrade" /> </head> <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="upgrade_11gr2_51_dpl_recompile.html">Prev</a> </td> - <th width="60%" align="center">Chapter 11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </th> + <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_51_sqlite_ver.html">Next</a></td> </tr> </table> @@ -39,12 +37,12 @@ </div> </div> <p> -The source code hierarchy has been reorganized. Source files that -belong to Berkeley DB core are now in a top-level directory -named <code class="literal">src</code>. Files related to language interfaces -are in <code class="literal">lang</code>, and all examples are collected -under <code class="literal">examples</code>. -</p> + The source code hierarchy has been reorganized. Source + files that belong to Berkeley DB core are now in a top-level + directory named <code class="literal">src</code>. Files related to + language interfaces are in <code class="literal">lang</code>, and all + examples are collected under <code class="literal">examples</code>. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/upgrade_11gr2_52_bit_cmp_win.html b/docs/installation/upgrade_11gr2_52_bit_cmp_win.html index c58cced6..d2b5c99e 100644 --- a/docs/installation/upgrade_11gr2_52_bit_cmp_win.html +++ b/docs/installation/upgrade_11gr2_52_bit_cmp_win.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_sqlite_ver.html" title="SQLite Interface Upgrade" /> <link rel="next" href="upgrade_11gr2_52_rep_dbt_readonly.html" title="Read Only flag for DBT" /> </head> <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="upgrade_11gr2_52_sqlite_ver.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_rep_dbt_readonly.html">Next</a></td> </tr> </table> @@ -38,13 +36,14 @@ </div> </div> </div> - <p> - Berkeley DB can now be compiled on Windows so that 32 bit and 64 - bit applications can concurrently access a BDB environment. To - enable this feature, build both the 32 bit BDB library and - application and the 64 bit library and application with the flag - <code class="literal">/D HAVE_MIXED_SIZE_ADDRESSING</code>. Note that - private environments are disabled under the compatibility mode. + <p> + Berkeley DB can now be compiled on Windows so that 32 bit + and 64 bit applications can concurrently access a BDB + environment. To enable this feature, build both the 32 bit BDB + library and application and the 64 bit library and application + with the flag <code class="literal">/D HAVE_MIXED_SIZE_ADDRESSING</code>. + Note that private environments are disabled under the + compatibility mode. </p> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_11gr2_52_dyn_env.html b/docs/installation/upgrade_11gr2_52_dyn_env.html index 42bdf82d..e28b53ed 100644 --- a/docs/installation/upgrade_11gr2_52_dyn_env.html +++ b/docs/installation/upgrade_11gr2_52_dyn_env.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_rep_dbt_readonly.html" title="Read Only flag for DBT" /> <link rel="next" href="upgrade_11gr2_52_excl_txn_sql.html" title="Exclusive Transactions in the SQL Layer" /> </head> <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="upgrade_11gr2_52_rep_dbt_readonly.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_excl_txn_sql.html">Next</a></td> </tr> </table> @@ -42,29 +40,30 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_dyn_env.html#idp611120">New Functions</a> + <a href="upgrade_11gr2_52_dyn_env.html#idp1243744">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_dyn_env.html#idp659088">Deprecated Functions</a> + <a href="upgrade_11gr2_52_dyn_env.html#idp1252704">Deprecated Functions</a> </span> </dt> </dl> </div> - <p> - Memory is now allocated incrementally as needed, instead of all at - once during environment initialization, for structures that support - locks, transactions, threads, and mutexes. With this change new - functions have been added that configure how much memory is - allocated initially, and how much that memory is allowed to grow. - The old memory configuration functions have been deprecated. + <p> + Memory is now allocated incrementally as needed, instead of + all at once during environment initialization, for structures + that support locks, transactions, threads, and mutexes. With + this change new functions have been added that configure how + much memory is allocated initially, and how much that memory + is allowed to grow. The old memory configuration functions + have been deprecated. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp611120"></a>New Functions</h3> + <h3 class="title"><a id="idp1243744"></a>New Functions</h3> </div> </div> </div> @@ -101,7 +100,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp659088"></a>Deprecated Functions</h3> + <h3 class="title"><a id="idp1252704"></a>Deprecated Functions</h3> </div> </div> </div> diff --git a/docs/installation/upgrade_11gr2_52_excl_txn_sql.html b/docs/installation/upgrade_11gr2_52_excl_txn_sql.html index 4ade0a8b..3197f05e 100644 --- a/docs/installation/upgrade_11gr2_52_excl_txn_sql.html +++ b/docs/installation/upgrade_11gr2_52_excl_txn_sql.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_dyn_env.html" title="Dynamic Environment Configuration" /> <link rel="next" href="upgrade_11gr2_52_grp_mbr.html" title="Group Membership in Repmgr" /> </head> <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="upgrade_11gr2_52_dyn_env.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_grp_mbr.html">Next</a></td> </tr> </table> @@ -39,13 +37,14 @@ </div> </div> <p> - Issuing the SQL command - <code class="literal">BEGIN TRANSACTION EXCLUSIVE</code> will now cause any - other transactions accessing the database to block, or return a - <code class="literal">SQLITE_BUSY</code> or <code class="literal">SQLITE_LOCK</code> - error, until the exclusive transaction is committed or aborted. - Previously, non-exclusive transactions could execute concurrently - with an exclusive transaction. + Issuing the SQL command <code class="literal">BEGIN TRANSACTION + EXCLUSIVE</code> will now cause any other transactions + accessing the database to block, or return a + <code class="literal">SQLITE_BUSY</code> or + <code class="literal">SQLITE_LOCK</code> error, until the exclusive + transaction is committed or aborted. Previously, non-exclusive + transactions could execute concurrently with an exclusive + transaction. </p> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_11gr2_52_grp_mbr.html b/docs/installation/upgrade_11gr2_52_grp_mbr.html index ef84154c..10a53d96 100644 --- a/docs/installation/upgrade_11gr2_52_grp_mbr.html +++ b/docs/installation/upgrade_11gr2_52_grp_mbr.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_excl_txn_sql.html" title="Exclusive Transactions in the SQL Layer" /> <link rel="next" href="upgrade_11gr2_52_heap.html" title="Heap Access Method" /> </head> <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="upgrade_11gr2_52_excl_txn_sql.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_heap.html">Next</a></td> </tr> </table> @@ -42,76 +40,77 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp676752">Upgrading</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1270248">Upgrading</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp657144">New Functions</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1250760">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp655568">Modified Functions</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1249616">Modified Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp602496">New Events</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1129176">New Events</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp684960">Removed Functions</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1278544">Removed Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp650072">New Parameters</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1245336">New Parameters</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp671784">New Structure</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1265176">New Structure</a> </span> </dt> </dl> </div> <p> - Replication Manager now manages group membership much more closely, - making it much easier for applications to add and remove sites from - a replication group without risk of transaction loss. In order to - accomplish this, the API for configuring group membership has - changed significantly. The + Replication Manager now manages group membership much more + closely, making it much easier for applications to add and + remove sites from a replication group without risk of + transaction loss. In order to accomplish this, the API for + configuring group membership has changed significantly. The <code class="literal">repmgr_set_local_site()</code> and - <code class="literal">repmgr_add_remote_site()</code> methods no longer - exist; they are replaced by a new handle type, - <code class="literal">DB_SITE</code>. The - <code class="literal">repmgr_get_local_site()</code> method has been replaced - by <a href="../api_reference/C/repmgr_site.html" class="olink">DB_ENV->repmgr_site()</a>, which now returns a - <code class="literal">DB_SITE</code> handle instead of a raw host/port - network address. + <code class="literal">repmgr_add_remote_site()</code> methods no + longer exist; they are replaced by a new handle type, + <code class="literal">DB_SITE</code>. The + <code class="literal">repmgr_get_local_site()</code> method has been + replaced by <a href="../api_reference/C/repmgr_site.html" class="olink">DB_ENV->repmgr_site()</a>, which now returns a + <code class="literal">DB_SITE</code> handle instead of a raw + host/port network address. </p> <p> - Replication Manager applications may no longer call the <a href="../api_reference/C/repnsites.html" class="olink">DB_ENV->rep_set_nsites()</a> - method, because the Replication Manager now tracks the number of - sites in the replication group for you. Replication Manager - applications may still call <a href="../api_reference/C/repget_nsites.html" class="olink">DB_ENV->rep_get_nsites()</a>, but only after a - successful call to <a href="../api_reference/C/repmgrstart.html" class="olink">DB_ENV->repmgr_start()</a>. + Replication Manager applications may no longer call the + <a href="../api_reference/C/repnsites.html" class="olink">DB_ENV->rep_set_nsites()</a> method, because the Replication Manager now tracks + the number of sites in the replication group for you. + Replication Manager applications may still call + <a href="../api_reference/C/repget_nsites.html" class="olink">DB_ENV->rep_get_nsites()</a>, but only after a successful call to + <a href="../api_reference/C/repmgrstart.html" class="olink">DB_ENV->repmgr_start()</a>. </p> - <p> - For applications using the replication Base API there is no change, - except that they may now call <a href="../api_reference/C/repnsites.html" class="olink">DB_ENV->rep_set_nsites()</a> to change the group size - even when Master Leases are in use. + <p> + For applications using the replication Base API there is no + change, except that they may now call <a href="../api_reference/C/repnsites.html" class="olink">DB_ENV->rep_set_nsites()</a> to change + the group size even when Master Leases are in use. </p> <p> - The new Replication Manager group membership functionality is - described in the <a href="../programmer_reference/group_membership.html" class="olink">Managing Replication Manager Group Membership</a> chapter in the + The new Replication Manager group membership functionality + is described in the <a href="../programmer_reference/group_membership.html" class="olink">Managing Replication Manager Group Membership</a> chapter in the <em class="citetitle">Berkeley DB Programmer's Reference Guide</em>. </p> <p> Replication Manager no longer prints an error message on a - connection failure. Instead it generates an event with the + connection failure. Instead it generates an event with the equivalent information (invoking the application's event-handling call-back function). </p> @@ -119,38 +118,41 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp676752"></a>Upgrading</h3> + <h3 class="title"><a id="idp1270248"></a>Upgrading</h3> </div> </div> </div> - <p> - An existing application running a previous version of BDB can do a - "live upgrade" so that only one site at a time has to be shut down. - To do this, restart each site in the group, with the old master - being shutdown last. When each site is restarted, use - <code class="literal">DB_SITE</code> to configure the local site with the - flag <code class="literal">DB_LEGACY</code>, and create a - <code class="literal">DB_SITE</code> handle with a full specification of all - the remote site addresses for all other sites currently in the - group, and configure each handle with the - <code class="literal">DB_LEGACY</code> flag. When the old master is - restarted and a new master has been established, the new master is - ready to manage membership changes, and new sites can be added as - usual. But the application must not try to add new sites, or remove - existing sites, during the mixed-version transitional phase. + <p> + An existing application running a previous version of + BDB can do a "live upgrade" so that only one site at a + time has to be shut down. To do this, restart each site in + the group, with the old master being shutdown last. When + each site is restarted, use <code class="literal">DB_SITE</code> to + configure the local site with the flag + <code class="literal">DB_LEGACY</code>, and create a + <code class="literal">DB_SITE</code> handle with a full + specification of all the remote site addresses for all + other sites currently in the group, and configure each + handle with the <code class="literal">DB_LEGACY</code> flag. When + the old master is restarted and a new master has been + established, the new master is ready to manage membership + changes, and new sites can be added as usual. But the + application must not try to add new sites, or remove + existing sites, during the mixed-version transitional + phase. </p> <p> - To do a non-live upgrade shutdown the entire replication group. - Then restart the group with each site configured with the - <code class="literal">DB_LEGACY</code> flag, and in - <code class="literal">DB_REP_ELECTION</code> mode. + To do a non-live upgrade shutdown the entire + replication group. Then restart the group with each site + configured with the <code class="literal">DB_LEGACY</code> flag, and + in <code class="literal">DB_REP_ELECTION</code> mode. </p> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp657144"></a>New Functions</h3> + <h3 class="title"><a id="idp1250760"></a>New Functions</h3> </div> </div> </div> @@ -187,16 +189,16 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp655568"></a>Modified Functions</h3> + <h3 class="title"><a id="idp1249616"></a>Modified Functions</h3> </div> </div> </div> <div class="itemizedlist"> <ul type="disc"> - <li><a href="../api_reference/C/repnsites.html" class="olink">DB_ENV->rep_set_nsites()</a> is no longer used by the Replication Manager, - but is still used by the Base API. It can now be used to - change the number of sites dynamically, even when master - leases are in use. + <li><a href="../api_reference/C/repnsites.html" class="olink">DB_ENV->rep_set_nsites()</a> is no longer used by the + Replication Manager, but is still used by the Base + API. It can now be used to change the number of sites + dynamically, even when master leases are in use. </li> </ul> </div> @@ -205,7 +207,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp602496"></a>New Events</h3> + <h3 class="title"><a id="idp1129176"></a>New Events</h3> </div> </div> </div> @@ -239,7 +241,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp684960"></a>Removed Functions</h3> + <h3 class="title"><a id="idp1278544"></a>Removed Functions</h3> </div> </div> </div> @@ -264,13 +266,13 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp650072"></a>New Parameters</h3> + <h3 class="title"><a id="idp1245336"></a>New Parameters</h3> </div> </div> </div> - <p> - The following new parameters are passed to - <a href="../api_reference/C/dbsite_set_config.html" class="olink">DB_SITE->set_config()</a>. + <p> + The following new parameters are passed to + <a href="../api_reference/C/dbsite_set_config.html" class="olink">DB_SITE->set_config()</a>. </p> <div class="itemizedlist"> <ul type="disc"> @@ -296,14 +298,15 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp671784"></a>New Structure</h3> + <h3 class="title"><a id="idp1265176"></a>New Structure</h3> </div> </div> </div> <div class="itemizedlist"> <ul type="disc"> - <li><code class="literal">DB_REPMGR_CONN_ERR</code> encapsulates an EID - and an integer system error code. + <li><code class="literal"> + DB_REPMGR_CONN_ERR</code> encapsulates an + EID and an integer system error code. </li> </ul> </div> diff --git a/docs/installation/upgrade_11gr2_52_heap.html b/docs/installation/upgrade_11gr2_52_heap.html index 9708a1a6..9bdf6083 100644 --- a/docs/installation/upgrade_11gr2_52_heap.html +++ b/docs/installation/upgrade_11gr2_52_heap.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_grp_mbr.html" title="Group Membership in Repmgr" /> <link rel="next" href="upgrade_11gr2_52_mvcc_sql.html" title="Enabling Transaction Snapshots in the SQL Layer" /> </head> <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="upgrade_11gr2_52_grp_mbr.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_mvcc_sql.html">Next</a></td> </tr> </table> @@ -42,33 +40,34 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_heap.html#idp683880">New Functions</a> + <a href="upgrade_11gr2_52_heap.html#idp1277464">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_heap.html#idp677456">Modified Functions</a> + <a href="upgrade_11gr2_52_heap.html#idp1270952">Modified Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_heap.html#idp678808">New Definition</a> + <a href="upgrade_11gr2_52_heap.html#idp1272304">New Definition</a> </span> </dt> </dl> </div> <p> - Databases can now be configured as heaps by passing the access type - <code class="literal">DB_HEAP</code> to <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a>. Heap size can be - configured with <a href="../api_reference/C/dbset_heapsize.html" class="olink">DB->set_heapsize()</a>, and <a href="../api_reference/C/dbstat.html" class="olink">DB->stat()</a> now returns heap - statistics in the structure <code class="literal">DB_HEAP_STAT</code> when - applied to a heap database. + Databases can now be configured as heaps by passing the + access type <code class="literal">DB_HEAP</code> to <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a>. Heap size + can be configured with <a href="../api_reference/C/dbset_heapsize.html" class="olink">DB->set_heapsize()</a>, and <a href="../api_reference/C/dbstat.html" class="olink">DB->stat()</a> now + returns heap statistics in the structure + <code class="literal">DB_HEAP_STAT</code> when applied to a heap + database. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp683880"></a>New Functions</h3> + <h3 class="title"><a id="idp1277464"></a>New Functions</h3> </div> </div> </div> @@ -87,17 +86,18 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp677456"></a>Modified Functions</h3> + <h3 class="title"><a id="idp1270952"></a>Modified Functions</h3> </div> </div> </div> <div class="itemizedlist"> <ul type="disc"> - <li><a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a> now accepts <code class="literal">DB_HEAP</code> as an access type. - </li> - <li><a href="../api_reference/C/dbstat.html" class="olink">DB->stat()</a> now returns heap statistics in the structure - <code class="literal">DB_HEAP_STAT</code>. - </li> + <li><a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a> now accepts <code class="literal">DB_HEAP</code> + as an access type. + </li> + <li><a href="../api_reference/C/dbstat.html" class="olink">DB->stat()</a> now returns heap statistics in the + structure <code class="literal">DB_HEAP_STAT</code>. + </li> </ul> </div> </div> @@ -105,14 +105,15 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp678808"></a>New Definition</h3> + <h3 class="title"><a id="idp1272304"></a>New Definition</h3> </div> </div> </div> <div class="itemizedlist"> <ul type="disc"> - <li><code class="literal">DB_HEAP_RID</code> is the defined heap key value. - </li> + <li><code class="literal">DB_HEAP_RID</code> is the defined heap key + value. + </li> </ul> </div> </div> diff --git a/docs/installation/upgrade_11gr2_52_hot_backup.html b/docs/installation/upgrade_11gr2_52_hot_backup.html index 292e4671..82220155 100644 --- a/docs/installation/upgrade_11gr2_52_hot_backup.html +++ b/docs/installation/upgrade_11gr2_52_hot_backup.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_xa.html" title="Berkeley DB X/Open Compliant XA Resource Manager" /> <link rel="next" href="changelog_5_2.html" title="Berkeley DB Library Version 11.2.5.2 Change Log" /> </head> <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="upgrade_11gr2_52_xa.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="changelog_5_2.html">Next</a></td> </tr> </table> @@ -39,13 +37,14 @@ </div> </div> <p> - Because non-UNIX systems do not support atomic file system reads, - the <a href="../api_reference/C/db_hotbackup.html" class="olink">db_hotbackup</a> utility has been modified to read data through the environment. - If your application is running on a UNIX based system such as Solaris, HPUX, - BSD or Mac OS, you can specify the <span class="bold"><strong>-F</strong></span> - flag to read directly from the filesystem. Please refer to - <a href="../programmer_reference/transapp_recovery.html" class="olink">Recovery procedures</a> in the <em class="citetitle">Berkeley DB Programmer's Reference Guide</em> for - more information on safely backing up your databases. + Because non-UNIX systems do not support atomic file system + reads, the <a href="../api_reference/C/db_hotbackup.html" class="olink">db_hotbackup</a> utility has been modified to read data + through the environment. If your application is running on a + UNIX based system such as Solaris, HPUX, BSD or Mac OS, you + can specify the <span class="bold"><strong>-F</strong></span> flag to + read directly from the filesystem. Please refer to + <a href="../programmer_reference/transapp_recovery.html" class="olink">Recovery procedures</a> in the <em class="citetitle">Berkeley DB Programmer's Reference Guide</em> + for more information on safely backing up your databases. </p> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_11gr2_52_mvcc_sql.html b/docs/installation/upgrade_11gr2_52_mvcc_sql.html index bcb18b21..386b411a 100644 --- a/docs/installation/upgrade_11gr2_52_mvcc_sql.html +++ b/docs/installation/upgrade_11gr2_52_mvcc_sql.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_heap.html" title="Heap Access Method" /> <link rel="next" href="upgrade_11gr2_52_rep_2site_strict.html" title="2SITE_STRICT Enabled by Default in Replication" /> </head> <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="upgrade_11gr2_52_heap.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_rep_2site_strict.html">Next</a></td> </tr> </table> @@ -42,29 +40,30 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_mvcc_sql.html#idp698336">New Pragmas</a> + <a href="upgrade_11gr2_52_mvcc_sql.html#idp1291928">New Pragmas</a> </span> </dt> </dl> </div> - <p> - Read/write concurrency can now be enabled in the SQL API by using - <code class="literal">PRAGMA multiversion=on</code> before accessing any - tables in the database. After multiversion has been enabled, it - can be temporarily disabled using the - <code class="literal">PRAGMA transaction_snapshots=on/off</code>. + <p> + Read/write concurrency can now be enabled in the SQL API by + using <code class="literal">PRAGMA multiversion=on</code> before + accessing any tables in the database. After multiversion has + been enabled, it can be temporarily disabled using the + <code class="literal">PRAGMA transaction_snapshots=on/off</code>. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp698336"></a>New Pragmas</h3> + <h3 class="title"><a id="idp1291928"></a>New Pragmas</h3> </div> </div> </div> <p> - For more details on pragmas concerning Transaction Snapshots - read <a href="../bdb-sql/mvcc.html" class="olink">Using Multiversion Concurrency Control</a> in the <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide. + For more details on pragmas concerning Transaction + Snapshots read <a href="../bdb-sql/mvcc.html" class="olink">Using Multiversion Concurrency Control</a> in the + <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide. </p> <div class="itemizedlist"> <ul type="disc"> diff --git a/docs/installation/upgrade_11gr2_52_rep_2site_strict.html b/docs/installation/upgrade_11gr2_52_rep_2site_strict.html index 3d684c69..b94cf98d 100644 --- a/docs/installation/upgrade_11gr2_52_rep_2site_strict.html +++ b/docs/installation/upgrade_11gr2_52_rep_2site_strict.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_mvcc_sql.html" title="Enabling Transaction Snapshots in the SQL Layer" /> <link rel="next" href="upgrade_11gr2_52_rep_sql.html" title="Enabling Replication in the SQL Layer" /> </head> <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="upgrade_11gr2_52_mvcc_sql.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_rep_sql.html">Next</a></td> </tr> </table> @@ -38,11 +36,11 @@ </div> </div> </div> - <p> - The 2SITE_STRICT replication configuration parameter is now turned - on by default. This configuration parameter is controlled using - the <a href="../api_reference/C/repconfig.html#config_DB_REPMGR_CONF_2SITE_STRICT" class="olink">DB_REPMGR_CONF_2SITE_STRICT</a>. - flag on the <a href="../api_reference/C/repconfig.html" class="olink">DB_ENV->rep_set_config()</a> method. + <p> + The 2SITE_STRICT replication configuration parameter is now + turned on by default. This configuration parameter is + controlled using the <a href="../api_reference/C/repconfig.html#config_DB_REPMGR_CONF_2SITE_STRICT" class="olink">DB_REPMGR_CONF_2SITE_STRICT</a>. + flag on the <a href="../api_reference/C/repconfig.html" class="olink">DB_ENV->rep_set_config()</a> method. </p> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_11gr2_52_rep_dbt_readonly.html b/docs/installation/upgrade_11gr2_52_rep_dbt_readonly.html index 8cbdbc28..c652183a 100644 --- a/docs/installation/upgrade_11gr2_52_rep_dbt_readonly.html +++ b/docs/installation/upgrade_11gr2_52_rep_dbt_readonly.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_bit_cmp_win.html" title="32bit/64bit Compatibility on Windows" /> <link rel="next" href="upgrade_11gr2_52_dyn_env.html" title="Dynamic Environment Configuration" /> </head> <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="upgrade_11gr2_52_bit_cmp_win.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_dyn_env.html">Next</a></td> </tr> </table> @@ -42,22 +40,23 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_rep_dbt_readonly.html#idp654424">New Flag</a> + <a href="upgrade_11gr2_52_rep_dbt_readonly.html#idp1248208">New Flag</a> </span> </dt> </dl> </div> - <p> - A <a href="../api_reference/C/dbt.html" class="olink">DBT</a> can now be set as read-only, when passed to the <a href="../api_reference/C/dbget.html" class="olink">DB->get()</a> - method, using the flag <code class="literal">DB_DBT_READONLY</code>. This is - useful when using a static string as a key value, because this flag - will prevent Berkeley DB from updating the <a href="../api_reference/C/dbt.html" class="olink">DBT</a>. + <p> + A <a href="../api_reference/C/dbt.html" class="olink">DBT</a> can now be set as read-only, when passed to the + <a href="../api_reference/C/dbget.html" class="olink">DB->get()</a> method, using the flag + <code class="literal">DB_DBT_READONLY</code>. This is useful when + using a static string as a key value, because this flag will + prevent Berkeley DB from updating the <a href="../api_reference/C/dbt.html" class="olink">DBT</a>. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp654424"></a>New Flag</h3> + <h3 class="title"><a id="idp1248208"></a>New Flag</h3> </div> </div> </div> diff --git a/docs/installation/upgrade_11gr2_52_rep_sql.html b/docs/installation/upgrade_11gr2_52_rep_sql.html index 84165503..16dbfaeb 100644 --- a/docs/installation/upgrade_11gr2_52_rep_sql.html +++ b/docs/installation/upgrade_11gr2_52_rep_sql.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_rep_2site_strict.html" title="2SITE_STRICT Enabled by Default in Replication" /> <link rel="next" href="upgrade_11gr2_52_repmgr_channels.html" title="Repmgr Message Channels" /> </head> <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="upgrade_11gr2_52_rep_2site_strict.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_repmgr_channels.html">Next</a></td> </tr> </table> @@ -42,21 +40,22 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_rep_sql.html#idp709672">New Pragmas</a> + <a href="upgrade_11gr2_52_rep_sql.html#idp1303192">New Pragmas</a> </span> </dt> </dl> </div> - <p> - Replication can now be enabled and configured in the SQL layer - using pragmas. The pragmas + <p> + Replication can now be enabled and configured in the SQL + layer using pragmas. The pragmas <code class="literal">replication_local_site</code>, <code class="literal">replication_initial_master</code>, and - <code class="literal">replication_remote_site</code> can be used to configure - the replication group. Note that when the BDB SQL replicated - application is initially started, a specific master site must be - explicitly designated. After configuring the replication group, - start replication using <code class="literal">PRAGMA replication=ON</code>. + <code class="literal">replication_remote_site</code> can be used to + configure the replication group. Note that when the BDB SQL + replicated application is initially started, a specific master + site must be explicitly designated. After configuring the + replication group, start replication using <code class="literal">PRAGMA + replication=ON</code>. </p> <p> To display replication statistics in the dbsql shell, use: @@ -66,14 +65,14 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp709672"></a>New Pragmas</h3> + <h3 class="title"><a id="idp1303192"></a>New Pragmas</h3> </div> </div> </div> - <p> + <p> For more details on the replication pragmas see - <a href="../bdb-sql/reppragma.html" class="olink">Replication PRAGMAs</a> in the <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide. - + <a href="../bdb-sql/reppragma.html" class="olink">Replication PRAGMAs</a> in the <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> + guide. </p> <div class="itemizedlist"> @@ -82,22 +81,28 @@ <code class="literal">PRAGMA replication=ON|OFF</code> </li> <li> - <code class="literal">PRAGMA replication_initial_master=ON|OFF</code> + <code class="literal">PRAGMA + replication_initial_master=ON|OFF</code> </li> <li> - <code class="literal">PRAGMA replication_local_site="hostname:port"</code> + <code class="literal">PRAGMA + replication_local_site="hostname:port"</code> </li> <li> - <code class="literal">PRAGMA replication_remote_site="hostname:port"</code> + <code class="literal">PRAGMA + replication_remote_site="hostname:port"</code> </li> <li> - <code class="literal">PRAGMA replication_remove_site="host:port"</code> + <code class="literal">PRAGMA + replication_remove_site="host:port"</code> </li> <li> - <code class="literal">PRAGMA replication_verbose_output=ON|OFF</code> + <code class="literal">PRAGMA + replication_verbose_output=ON|OFF</code> </li> <li> - <code class="literal">PRAGMA replication_verbose_file=filename</code> + <code class="literal">PRAGMA + replication_verbose_file=filename</code> </li> </ul> </div> diff --git a/docs/installation/upgrade_11gr2_52_repmgr_channels.html b/docs/installation/upgrade_11gr2_52_repmgr_channels.html index 45c16ee9..0025dcd1 100644 --- a/docs/installation/upgrade_11gr2_52_repmgr_channels.html +++ b/docs/installation/upgrade_11gr2_52_repmgr_channels.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_rep_sql.html" title="Enabling Replication in the SQL Layer" /> <link rel="next" href="upgrade_11gr2_52_seq_sql.html" title="Sequence Support in the SQL Layer" /> </head> <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="upgrade_11gr2_52_rep_sql.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_seq_sql.html">Next</a></td> </tr> </table> @@ -42,29 +40,30 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_repmgr_channels.html#idp704400">New Functions</a> + <a href="upgrade_11gr2_52_repmgr_channels.html#idp1249368">New Functions</a> </span> </dt> </dl> </div> - <p> + <p> Application components running at various sites within a - replication group can now use the Replication Manager's existing - TCP/IP communications infrastructure to send and process messages - among themselves, using the <code class="literal">DB_CHANNEL</code> handle. - <a href="../api_reference/C/repmgr_channel.html" class="olink">DB_ENV->repmgr_channel()</a> is used to create the - <code class="literal">DB_CHANNEL</code> handle. <a href="../api_reference/C/dbchannel_send_msg.html" class="olink">DB_CHANNEL->send_msg()</a> and - <a href="../api_reference/C/dbchannel_send_request.html" class="olink">DB_CHANNEL->send_request()</a> are used to send sychronous and - asychronous messages that are handled by the function set by - <a href="../api_reference/C/repmgr_msg_dispatch.html" class="olink">DB_ENV->repmgr_msg_dispatch()</a>. <a href="../api_reference/C/dbchannel_set_timeout.html" class="olink">DB_CHANNEL->set_timeout()</a> is used to - configure channel time out, and <a href="../api_reference/C/dbchannel_close.html" class="olink">DB_CHANNEL->close()</a> closes the - channel and frees resources held by it. + replication group can now use the Replication Manager's + existing TCP/IP communications infrastructure to send and + process messages among themselves, using the + <code class="literal">DB_CHANNEL</code> handle. <a href="../api_reference/C/repmgr_channel.html" class="olink">DB_ENV->repmgr_channel()</a> + is used to create the <code class="literal">DB_CHANNEL</code> handle. + <a href="../api_reference/C/dbchannel_send_msg.html" class="olink">DB_CHANNEL->send_msg()</a> and <a href="../api_reference/C/dbchannel_send_request.html" class="olink">DB_CHANNEL->send_request()</a> are used to + send sychronous and asychronous messages that are handled by + the function set by <a href="../api_reference/C/repmgr_msg_dispatch.html" class="olink">DB_ENV->repmgr_msg_dispatch()</a>. + <a href="../api_reference/C/dbchannel_set_timeout.html" class="olink">DB_CHANNEL->set_timeout()</a> is used to configure channel time out, + and <a href="../api_reference/C/dbchannel_close.html" class="olink">DB_CHANNEL->close()</a> closes the channel and frees resources + held by it. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp704400"></a>New Functions</h3> + <h3 class="title"><a id="idp1249368"></a>New Functions</h3> </div> </div> </div> @@ -107,7 +106,8 @@ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Sequence Support in the SQL Layer</td> + <td width="40%" align="right" valign="top"> Sequence Support in the + SQL Layer</td> </tr> </table> </div> diff --git a/docs/installation/upgrade_11gr2_52_seq_sql.html b/docs/installation/upgrade_11gr2_52_seq_sql.html index 74d4fe07..585f4b06 100644 --- a/docs/installation/upgrade_11gr2_52_seq_sql.html +++ b/docs/installation/upgrade_11gr2_52_seq_sql.html @@ -7,24 +7,23 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_repmgr_channels.html" title="Repmgr Message Channels" /> <link rel="next" href="upgrade_11gr2_52_xa.html" title="Berkeley DB X/Open Compliant XA Resource Manager" /> </head> <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">Sequence Support in the SQL Layer</th> + <th colspan="3" align="center">Sequence Support in the + SQL Layer</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="upgrade_11gr2_52_repmgr_channels.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_xa.html">Next</a></td> </tr> </table> @@ -34,7 +33,8 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="upgrade_11gr2_52_seq_sql"></a>Sequence Support in the SQL Layer</h2> + <h2 class="title" style="clear: both"><a id="upgrade_11gr2_52_seq_sql"></a>Sequence Support in the + SQL Layer</h2> </div> </div> </div> @@ -42,26 +42,26 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_seq_sql.html#idp710392">New Functions</a> + <a href="upgrade_11gr2_52_seq_sql.html#idp1303976">New Functions</a> </span> </dt> </dl> </div> <p> - A partial implementation of the sequence API defined in the SQL - 2003 specification has been added to the SQL layer. A sequence is - created using the syntax: + A partial implementation of the sequence API defined in the + SQL 2003 specification has been added to the SQL layer. A + sequence is created using the syntax: </p> <pre class="programlisting">SELECT create_sequence("sequence_name"...) </pre> - <p> - The sequence numbers are accessed using + <p> + The sequence numbers are accessed using </p> <pre class="programlisting">SELECT nextval("sequence_name") </pre> - <p> + <p> and </p> <pre class="programlisting">SELECT currval("sequence_name")</pre> - <p> + <p> Finally, a sequence can be dropped using </p> <pre class="programlisting">SELECT drop_sequence("sequence_name")</pre> @@ -69,15 +69,15 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp710392"></a>New Functions</h3> + <h3 class="title"><a id="idp1303976"></a>New Functions</h3> </div> </div> </div> - <p> - The four new functions, which have to be called as part of a - <code class="literal">SELECT</code> statement, are describe in more - detail in <a href="../bdb-sql/sequencesupport.html" class="olink">Using Sequences</a> in the - <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide. + <p> + The four new functions, which have to be called as part + of a <code class="literal">SELECT</code> statement, are describe in + more detail in <a href="../bdb-sql/sequencesupport.html" class="olink">Using Sequences</a> in the + <em class="citetitle">Berkeley DB Getting Started with the SQL APIs</em> guide. </p> <div class="itemizedlist"> @@ -91,7 +91,7 @@ <li> <a href="../bdb-sql/sequencesupport.html#seq_currval" class="olink">seq_currval</a> </li> - <li><a href="../bdb-sql/sequencesupport.html#seq_drop_sequence" class="olink">seq_drop_sequence</a>. + <li><a href="../bdb-sql/sequencesupport.html#seq_drop_sequence" class="olink">seq_drop_sequence</a>. </li> </ul> </div> diff --git a/docs/installation/upgrade_11gr2_52_sqlite_ver.html b/docs/installation/upgrade_11gr2_52_sqlite_ver.html index 1372c66a..596d20b1 100644 --- a/docs/installation/upgrade_11gr2_52_sqlite_ver.html +++ b/docs/installation/upgrade_11gr2_52_sqlite_ver.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> - <link rel="prev" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="prev" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="next" href="upgrade_11gr2_52_bit_cmp_win.html" title="32bit/64bit Compatibility on Windows" /> </head> <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="upgrade_52_toc.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_bit_cmp_win.html">Next</a></td> </tr> </table> @@ -38,11 +36,12 @@ </div> </div> </div> - <p> - Berkeley DB's SQL interface includes code from SQLite. The version of - SQLite used has been upgraded, so DB SQL is compatible - with SQLite version 3.7.6.2. Please see the release notes at - <a class="ulink" href="http://sqlite.org/changes.html" target="_top">http://sqlite.org/changes.html</a> for further information. + <p> + Berkeley DB's SQL interface includes code from SQLite. The + version of SQLite used has been upgraded, so DB SQL is + compatible with SQLite version 3.7.6.2. Please see the release + notes at <a class="ulink" href="http://sqlite.org/changes.html" target="_top">http://sqlite.org/changes.html</a> for + further information. </p> </div> <div class="navfooter"> @@ -56,9 +55,7 @@ <td width="40%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_bit_cmp_win.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </td> + <td width="40%" align="left" valign="top">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/upgrade_11gr2_52_xa.html b/docs/installation/upgrade_11gr2_52_xa.html index b062717a..910fce5a 100644 --- a/docs/installation/upgrade_11gr2_52_xa.html +++ b/docs/installation/upgrade_11gr2_52_xa.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_52_toc.html" title="Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> + <link rel="up" href="upgrade_52_toc.html" title="Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2" /> <link rel="prev" href="upgrade_11gr2_52_seq_sql.html" title="Sequence Support in the SQL Layer" /> <link rel="next" href="upgrade_11gr2_52_hot_backup.html" title="Hot Backup Changes" /> </head> <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="upgrade_11gr2_52_seq_sql.html">Prev</a> </td> - <th width="60%" align="center">Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th width="60%" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_hot_backup.html">Next</a></td> </tr> </table> @@ -42,62 +40,63 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_xa.html#idp720184">Constraints</a> + <a href="upgrade_11gr2_52_xa.html#idp1314200">Constraints</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_xa.html#idp725120">New Flag</a> + <a href="upgrade_11gr2_52_xa.html#idp1319928">New Flag</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_xa.html#idp729168">Modified Function</a> + <a href="upgrade_11gr2_52_xa.html#idp1324040">Modified Function</a> </span> </dt> </dl> </div> - <p> - The Berkeley DB X/open compliant XA resource manager has been - restored. (It was removed from the product after the 4.7 release.) - The new implementation includes support for multi-threaded servers. - Consult the documentation of your chosen transaction manager to - learn how to implement a multi-threaded server. + <p> + The Berkeley DB X/open compliant XA resource manager has + been restored. (It was removed from the product after the 4.7 + release.) The new implementation includes support for + multi-threaded servers. Consult the documentation of your + chosen transaction manager to learn how to implement a + multi-threaded server. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp720184"></a>Constraints</h3> + <h3 class="title"><a id="idp1314200"></a>Constraints</h3> </div> </div> </div> <p> - Applictions that use a BDB XA resource manager must now take - into account the following constraints. + Applictions that use a BDB XA resource manager must now + take into account the following constraints. </p> <div class="itemizedlist"> <ul type="disc"> <li> No in-memory logging. </li> - <li> + <li> No application-level child transactions. </li> <li> - All database-level operations (open, close, create - and the like) must be performed outside of a global - transactions (i.e., they can be performed in local - BDB transactions, but not while a distributed - XA transaction is active). + All database-level operations (open, close, + create and the like) must be performed outside of a + global transactions (i.e., they can be performed in + local BDB transactions, but not while a distributed XA + transaction is active). </li> <li> - Environment configuration must be done using a + Environment configuration must be done using a DB_CONFIG file. </li> <li> - Cursors must be closed before a service invocation - returns. + Cursors must be closed before a service + invocation returns. </li> </ul> </div> @@ -106,15 +105,15 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp725120"></a>New Flag</h3> + <h3 class="title"><a id="idp1319928"></a>New Flag</h3> </div> </div> </div> <div class="itemizedlist"> <ul type="disc"> - <li><code class="literal">DB_XA_CREATE</code> - This flag is passed to - <a href="../api_reference/C/dbcreate.html" class="olink">db_create()</a> to create a <code class="literal">DB</code> handle that - supports XA transactions. + <li><code class="literal">DB_XA_CREATE</code> - This flag is passed + to <a href="../api_reference/C/dbcreate.html" class="olink">db_create()</a> to create a <code class="literal">DB</code> handle + that supports XA transactions. </li> </ul> </div> @@ -123,15 +122,15 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp729168"></a>Modified Function</h3> + <h3 class="title"><a id="idp1324040"></a>Modified Function</h3> </div> </div> </div> <div class="itemizedlist"> <ul type="disc"> <li><a href="../api_reference/C/dbstat.html" class="olink">DB->stat()</a> now returns the field - <code class="literal">DB_TXN_STAT->DB_TXN_ACTIVE->xa_status</code>, which - contains information on the XA transactions. + <code class="literal">DB_TXN_STAT->DB_TXN_ACTIVE->xa_status</code>, + which contains information on the XA transactions. </li> </ul> </div> @@ -148,7 +147,8 @@ <td width="40%" align="right"> <a accesskey="n" href="upgrade_11gr2_52_hot_backup.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Sequence Support in the SQL Layer </td> + <td width="40%" align="left" valign="top">Sequence Support in the + SQL Layer </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/upgrade_11gr2_53_build_windows.html b/docs/installation/upgrade_11gr2_53_build_windows.html index 4ad25867..40bd7f43 100644 --- a/docs/installation/upgrade_11gr2_53_build_windows.html +++ b/docs/installation/upgrade_11gr2_53_build_windows.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> - <link rel="prev" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="prev" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="next" href="upgrade_11gr2_53_conn_status.html" title="Replication Connection Status in the Java API" /> </head> <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="upgrade_53_toc.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_conn_status.html">Next</a></td> </tr> </table> @@ -39,12 +37,12 @@ </div> </div> <p> - Visual Studios projects in the <code class="literal">build_windows</code> - folder have been moved into two new sub folders - <code class="literal">build_windows/VS8</code> and - <code class="literal">build_windows/VS10</code>. Visual Studios 2010 projects - have been moved into the folder VS10, and Visual Studios 2008 projects - have been moved into the folder VS8. + Visual Studios projects in the + <code class="literal">build_windows</code> folder have been moved + into two new sub folders <code class="literal">build_windows/VS8</code> + and <code class="literal">build_windows/VS10</code>. Visual Studios 2010 + projects have been moved into the folder VS10, and Visual + Studios 2008 projects have been moved into the folder VS8. </p> </div> <div class="navfooter"> @@ -58,9 +56,7 @@ <td width="40%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_conn_status.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </td> + <td width="40%" align="left" valign="top">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/upgrade_11gr2_53_conn_status.html b/docs/installation/upgrade_11gr2_53_conn_status.html index fa3744a4..59ab1384 100644 --- a/docs/installation/upgrade_11gr2_53_conn_status.html +++ b/docs/installation/upgrade_11gr2_53_conn_status.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_build_windows.html" title="Changes to the build_windows Folder" /> <link rel="next" href="upgrade_11gr2_53_excl.html" title="Exclusive Database Handles" /> </head> <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="upgrade_11gr2_53_build_windows.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_excl.html">Next</a></td> </tr> </table> @@ -42,36 +40,38 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_conn_status.html#idp506032">New Function</a> + <a href="upgrade_11gr2_53_conn_status.html#idp1160632">New Function</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_conn_status.html#idp531112">New Class</a> + <a href="upgrade_11gr2_53_conn_status.html#idp1116080">New Class</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_conn_status.html#idp564984">Deprecated Function</a> + <a href="upgrade_11gr2_53_conn_status.html#idp1164288">Deprecated Function</a> </span> </dt> </dl> </div> - <p> - The Java function - <code class="literal">ReplicationManagerSiteInfo.isConnected()</code> is now - deprecated. To get the replication connection status, use - <code class="literal">ReplicationManagerSiteInfo.getConnectionStatus()</code>, - which returns the new class - <code class="literal">ReplicationManagerConnectionStatus</code>, which has the - values <code class="literal">CONNECTED</code>, <code class="literal">DISCONNECTED</code>, - and <code class="literal">UNKNOWN</code>. + <p> + The Java function + <code class="literal">ReplicationManagerSiteInfo.isConnected()</code> + is now deprecated. To get the replication connection status, + use + <code class="literal">ReplicationManagerSiteInfo.getConnectionStatus()</code>, + which returns the new class + <code class="literal">ReplicationManagerConnectionStatus</code>, + which has the values <code class="literal">CONNECTED</code>, + <code class="literal">DISCONNECTED</code>, and + <code class="literal">UNKNOWN</code>. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp506032"></a>New Function</h3> + <h3 class="title"><a id="idp1160632"></a>New Function</h3> </div> </div> </div> @@ -87,7 +87,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp531112"></a>New Class</h3> + <h3 class="title"><a id="idp1116080"></a>New Class</h3> </div> </div> </div> @@ -103,7 +103,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp564984"></a>Deprecated Function</h3> + <h3 class="title"><a id="idp1164288"></a>Deprecated Function</h3> </div> </div> </div> diff --git a/docs/installation/upgrade_11gr2_53_excl.html b/docs/installation/upgrade_11gr2_53_excl.html index ddfcfabc..3ddcb8d5 100644 --- a/docs/installation/upgrade_11gr2_53_excl.html +++ b/docs/installation/upgrade_11gr2_53_excl.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_conn_status.html" title="Replication Connection Status in the Java API" /> <link rel="next" href="upgrade_11gr2_53_heap_regionsize.html" title="Configure the Region Size of Heap Databases" /> </head> <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="upgrade_11gr2_53_conn_status.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_heap_regionsize.html">Next</a></td> </tr> </table> @@ -42,24 +40,25 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_excl.html#idp567208">New Functions</a> + <a href="upgrade_11gr2_53_excl.html#idp1166512">New Functions</a> </span> </dt> </dl> </div> - <p> - Database handles can now be configured to allow exclusive access to the - database. To enable exclusive access, call <a href="../api_reference/C/dbset_lk_exclusive.html" class="olink">DB->set_lk_exclusive()</a> before - calling <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a>. Set nowait_onoff to non-zero to have <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a> return - immediately, with the error <code class="literal">DB_LOCK_NOTGRANTED</code> if - it cannot immediately get exclusive access to the database, and to - 0 to have <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a> block until it can gain exclusive access. + <p> + Database handles can now be configured to allow exclusive + access to the database. To enable exclusive access, call + <a href="../api_reference/C/dbset_lk_exclusive.html" class="olink">DB->set_lk_exclusive()</a> before calling <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a>. Set nowait_onoff + to non-zero to have <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a> return immediately, with the + error <code class="literal">DB_LOCK_NOTGRANTED</code> if it cannot + immediately get exclusive access to the database, and to 0 to + have <a href="../api_reference/C/dbopen.html" class="olink">DB->open()</a> block until it can gain exclusive access. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp567208"></a>New Functions</h3> + <h3 class="title"><a id="idp1166512"></a>New Functions</h3> </div> </div> </div> diff --git a/docs/installation/upgrade_11gr2_53_heap_regionsize.html b/docs/installation/upgrade_11gr2_53_heap_regionsize.html index 4e30c057..9edc69f0 100644 --- a/docs/installation/upgrade_11gr2_53_heap_regionsize.html +++ b/docs/installation/upgrade_11gr2_53_heap_regionsize.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_excl.html" title="Exclusive Database Handles" /> <link rel="next" href="upgrade_11gr2_53_hotbackup.html" title="New Hotbackup Interface" /> </head> <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="upgrade_11gr2_53_excl.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_hotbackup.html">Next</a></td> </tr> </table> @@ -42,23 +40,25 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_heap_regionsize.html#idp570008">New Functions</a> + <a href="upgrade_11gr2_53_heap_regionsize.html#idp1093968">New Functions</a> </span> </dt> </dl> </div> <p> - The region size of heap databases is now configurable. Configuring the - region size is useful in controlling the growth of a heap database. - To set the region size, call <a href="../api_reference/C/dbset_heap_regionsize.html" class="olink">DB->set_heap_regionsize()</a> with the number - of pages that the region should have, before the database is created. - The function is ignored if it is called after the database is created. + The region size of heap databases is now configurable. + Configuring the region size is useful in controlling the + growth of a heap database. To set the region size, call + <a href="../api_reference/C/dbset_heap_regionsize.html" class="olink">DB->set_heap_regionsize()</a> with the number of pages that the + region should have, before the database is created. The + function is ignored if it is called after the database is + created. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp570008"></a>New Functions</h3> + <h3 class="title"><a id="idp1093968"></a>New Functions</h3> </div> </div> </div> diff --git a/docs/installation/upgrade_11gr2_53_hotbackup.html b/docs/installation/upgrade_11gr2_53_hotbackup.html index bcd0ea8e..108182dd 100644 --- a/docs/installation/upgrade_11gr2_53_hotbackup.html +++ b/docs/installation/upgrade_11gr2_53_hotbackup.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_heap_regionsize.html" title="Configure the Region Size of Heap Databases" /> <link rel="next" href="upgrade_11gr2_53_jdbc.html" title="Updated JDBC Version" /> </head> <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="upgrade_11gr2_53_heap_regionsize.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_jdbc.html">Next</a></td> </tr> </table> @@ -42,41 +40,41 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp571040">New Functions</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1170128">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp560912">Flags Accepted by DB_ENV->backup()</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1175656">Flags Accepted by DB_ENV->backup()</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp578624">Flags Accepted by DB_ENV->dbbackup()</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1177648">Flags Accepted by DB_ENV->dbbackup()</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp584448">Enumerations Accepted by DB_ENV->set_backup_config()</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1183112">Enumerations Accepted by DB_ENV->set_backup_config()</a> </span> </dt> </dl> </div> - <p> + <p> Two new functions have been added to the API that perform - hotbackups, <a href="../api_reference/C/envbackup.html" class="olink">DB_ENV->backup()</a> and <a href="../api_reference/C/envdbbackup.html" class="olink">DB_ENV->dbbackup()</a>. <a href="../api_reference/C/envbackup.html" class="olink">DB_ENV->backup()</a> creates a - hotbackup of all databases in the specified environment, and - <a href="../api_reference/C/envdbbackup.html" class="olink">DB_ENV->dbbackup()</a> creates a hotbackup of the specified database. The - functions <a href="../api_reference/C/envset_backup_callbacks.html" class="olink">DB_ENV->set_backup_callbacks()</a> and <a href="../api_reference/C/envset_backup_config.html" class="olink">DB_ENV->set_backup_config()</a> can - be called to customize the behavior of hotbackup. Note that this - interface must be used to create a hotbackup on all non-BSD or Unix - based systems. + hotbackups, <a href="../api_reference/C/envbackup.html" class="olink">DB_ENV->backup()</a> and <a href="../api_reference/C/envdbbackup.html" class="olink">DB_ENV->dbbackup()</a>. <a href="../api_reference/C/envbackup.html" class="olink">DB_ENV->backup()</a> creates + a hotbackup of all databases in the specified environment, and + <a href="../api_reference/C/envdbbackup.html" class="olink">DB_ENV->dbbackup()</a> creates a hotbackup of the specified database. + The functions <a href="../api_reference/C/envset_backup_callbacks.html" class="olink">DB_ENV->set_backup_callbacks()</a> and + <a href="../api_reference/C/envset_backup_config.html" class="olink">DB_ENV->set_backup_config()</a> can be called to customize the behavior + of hotbackup. Note that this interface must be used to create + a hotbackup on all non-BSD or Unix based systems. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp571040"></a>New Functions</h3> + <h3 class="title"><a id="idp1170128"></a>New Functions</h3> </div> </div> </div> @@ -101,7 +99,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp560912"></a>Flags Accepted by <a href="../api_reference/C/envbackup.html" class="olink">DB_ENV->backup()</a></h3> + <h3 class="title"><a id="idp1175656"></a>Flags Accepted by <a href="../api_reference/C/envbackup.html" class="olink">DB_ENV->backup()</a></h3> </div> </div> </div> @@ -138,7 +136,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp578624"></a>Flags Accepted by <a href="../api_reference/C/envdbbackup.html" class="olink">DB_ENV->dbbackup()</a></h3> + <h3 class="title"><a id="idp1177648"></a>Flags Accepted by <a href="../api_reference/C/envdbbackup.html" class="olink">DB_ENV->dbbackup()</a></h3> </div> </div> </div> @@ -157,7 +155,7 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp584448"></a>Enumerations Accepted by <a href="../api_reference/C/envset_backup_config.html" class="olink">DB_ENV->set_backup_config()</a></h3> + <h3 class="title"><a id="idp1183112"></a>Enumerations Accepted by <a href="../api_reference/C/envset_backup_config.html" class="olink">DB_ENV->set_backup_config()</a></h3> </div> </div> </div> diff --git a/docs/installation/upgrade_11gr2_53_jdbc.html b/docs/installation/upgrade_11gr2_53_jdbc.html index 3fc7a1fe..5a9eb6b6 100644 --- a/docs/installation/upgrade_11gr2_53_jdbc.html +++ b/docs/installation/upgrade_11gr2_53_jdbc.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_hotbackup.html" title="New Hotbackup Interface" /> <link rel="next" href="upgrade_11gr2_53_meta_dir.html" title="Configure Directory to Store Metadata Files" /> </head> <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="upgrade_11gr2_53_hotbackup.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_meta_dir.html">Next</a></td> </tr> </table> @@ -38,11 +36,11 @@ </div> </div> </div> - <p> - The JDBC library version included with Berkeley DB has been updated to - version 20110827. The new version supports the Embedded Java JSR 169 - standard, which is the official specification for JDBC with embedded - Java platforms. + <p> + The JDBC library version included with Berkeley DB has been + updated to version 20110827. The new version supports the + Embedded Java JSR 169 standard, which is the official + specification for JDBC with embedded Java platforms. </p> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_11gr2_53_meta_dir.html b/docs/installation/upgrade_11gr2_53_meta_dir.html index 9290b6e5..56e69920 100644 --- a/docs/installation/upgrade_11gr2_53_meta_dir.html +++ b/docs/installation/upgrade_11gr2_53_meta_dir.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_jdbc.html" title="Updated JDBC Version" /> <link rel="next" href="upgrade_11gr2_53_sql_build.html" title="Changes in the SQL API Build" /> </head> <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="upgrade_11gr2_53_jdbc.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_sql_build.html">Next</a></td> </tr> </table> @@ -42,30 +40,30 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_meta_dir.html#idp593384">New Functions</a> + <a href="upgrade_11gr2_53_meta_dir.html#idp1192152">New Functions</a> </span> </dt> </dl> </div> <p> - The directory in which persistent metadata files are stored can now - be configured. By default persistent metadata files are stored in - the environment home directory. The files that will be stored in - the metadata directory are __db.rep.system, __db.rep.gen, - __db.rep.egen and __db.rep.init. + The directory in which persistent metadata files are stored + can now be configured. By default persistent metadata files + are stored in the environment home directory. The files that + will be stored in the metadata directory are __db.rep.system, + __db.rep.gen, __db.rep.egen and __db.rep.init. </p> - <p> - To set the metadata file directory, call <a href="../api_reference/C/envset_metadata_dir.html" class="olink">DB_ENV->set_metadata_dir()</a> with - the path to the directory in which to store metadata files. The - metadata directory can also be set in the - <code class="literal">DB_CONFIG</code> file using + <p> + To set the metadata file directory, call + <a href="../api_reference/C/envset_metadata_dir.html" class="olink">DB_ENV->set_metadata_dir()</a> with the path to the directory in which + to store metadata files. The metadata directory can also be + set in the <code class="literal">DB_CONFIG</code> file using <code class="literal">set_metadata_dir</code>. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp593384"></a>New Functions</h3> + <h3 class="title"><a id="idp1192152"></a>New Functions</h3> </div> </div> </div> diff --git a/docs/installation/upgrade_11gr2_53_sql_build.html b/docs/installation/upgrade_11gr2_53_sql_build.html index 5ea90fe4..c17d1dc1 100644 --- a/docs/installation/upgrade_11gr2_53_sql_build.html +++ b/docs/installation/upgrade_11gr2_53_sql_build.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_meta_dir.html" title="Configure Directory to Store Metadata Files" /> <link rel="next" href="upgrade_11gr2_53_sql_pragma.html" title="New Berkeley DB SQL API PRAGMAs" /> </head> <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="upgrade_11gr2_53_meta_dir.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_sql_pragma.html">Next</a></td> </tr> </table> @@ -39,18 +37,20 @@ </div> </div> <p> - Several changes have been made to the SQL API build. - Encryption is now disabled by default on Windows, and the compile time - flag BDBSQL_OMIT_SHARING has been changed to BDBSQL_SINGLE_PROCESS. + Several changes have been made to the SQL API build. + Encryption is now disabled by default on Windows, and the + compile time flag BDBSQL_OMIT_SHARING has been changed to + BDBSQL_SINGLE_PROCESS. </p> <p> - Encryption is now disabled by default in the Windows SQL API build. - This makes it consistent with builds of the SQL API on other systems. - To enable encryption in Visual Studios right click the db_sql project, - and select - <code class="literal">Properties->Configuration Properties->C/C++->Preprocessor</code> - and add <code class="literal">SQLITE_HAS_CODEC</code> to - <code class="literal">Preprocessor Definitions</code>. + Encryption is now disabled by default in the Windows SQL + API build. This makes it consistent with builds of the SQL API + on other systems. To enable encryption in Visual Studios right + click the db_sql project, and select + <code class="literal">Properties->Configuration + Properties->C/C++->Preprocessor</code> and add + <code class="literal">SQLITE_HAS_CODEC</code> to + <code class="literal">Preprocessor Definitions</code>. </p> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_11gr2_53_sql_pragma.html b/docs/installation/upgrade_11gr2_53_sql_pragma.html index 09aca956..f3b6f507 100644 --- a/docs/installation/upgrade_11gr2_53_sql_pragma.html +++ b/docs/installation/upgrade_11gr2_53_sql_pragma.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_sql_build.html" title="Changes in the SQL API Build" /> <link rel="next" href="upgrade_11gr2_53_sql_rep.html" title="Replication for Existing Databases in the SQL API" /> </head> <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="upgrade_11gr2_53_sql_build.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_sql_rep.html">Next</a></td> </tr> </table> @@ -42,29 +40,29 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_sql_pragma.html#idp599768">New PRAGMAs</a> + <a href="upgrade_11gr2_53_sql_pragma.html#idp1198640">New PRAGMAs</a> </span> </dt> </dl> </div> - <p> - Two new Berkeley DB SQL API specific pragmas have been added, - <code class="literal">bdbsql_shared_resources</code> and - <code class="literal">bdbsql_set_lock_tablesize</code>. - <code class="literal">bdbsql_shared_resources</code> is used to set the maximum - amount of memory, in bytes, to be used by shared structures in the main - environment region, which is useful in applications with a large - number of tables, transactions, or threads. - <code class="literal">bdbsql_set_lock_tablesize</code> is used to set the number - of buckets in the lock object hash table in the Berkeley DB - environment, which is useful if an application has many concurrent - long running transactions. + <p> + Two new Berkeley DB SQL API specific pragmas have been + added, <code class="literal">bdbsql_shared_resources</code> and + <code class="literal">bdbsql_set_lock_tablesize</code>. + <code class="literal">bdbsql_shared_resources</code> is used to set + the maximum amount of memory, in bytes, to be used by shared + structures in the main environment region, which is useful in + applications with a large number of tables, transactions, or + threads. <code class="literal">bdbsql_set_lock_tablesize</code> is used + to set the number of buckets in the lock object hash table in + the Berkeley DB environment, which is useful if an application + has many concurrent long running transactions. </p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp599768"></a>New PRAGMAs</h3> + <h3 class="title"><a id="idp1198640"></a>New PRAGMAs</h3> </div> </div> </div> @@ -74,7 +72,8 @@ <code class="literal">PRAGMA bdbsql_shared_resources[=N]</code> </li> <li> - <code class="literal">PRAGMA bdbsql_set_lock_tablesize[=N]</code> + <code class="literal">PRAGMA + bdbsql_set_lock_tablesize[=N]</code> </li> </ul> </div> diff --git a/docs/installation/upgrade_11gr2_53_sql_rep.html b/docs/installation/upgrade_11gr2_53_sql_rep.html index 566a6f7a..1762cc9c 100644 --- a/docs/installation/upgrade_11gr2_53_sql_rep.html +++ b/docs/installation/upgrade_11gr2_53_sql_rep.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_sql_pragma.html" title="New Berkeley DB SQL API PRAGMAs" /> <link rel="next" href="upgrade_11gr2_53_xa_mvcc.html" title="Berkeley DB X/Open Compliant XA Resource Manager and Transaction Snapshots" /> </head> <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,84 +22,25 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="upgrade_11gr2_53_sql_pragma.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_xa_mvcc.html">Next</a></td> </tr> </table> <hr /> </div> - <div class="sect1" lang="en" xml:lang="en"> - <div class="titlepage"> - <div> - <div> - <h2 class="title" style="clear: both"><a id="upgrade_11gr2_53_sql_rep"></a>Replication for Existing Databases in the SQL API</h2> - </div> - </div> - </div> - <div class="toc"> - <dl> - <dt> - <span class="sect2"> - <a href="upgrade_11gr2_53_sql_rep.html#idp593704">PRAGMAs With Permanent Effects</a> - </span> - </dt> - <dt> - <span class="sect2"> - <a href="upgrade_11gr2_53_sql_rep.html#idp600544">PRAGMAs That Can Now Operate on Existing Databases</a> - </span> - </dt> - </dl> - </div> - <p> - Replication can now be enabled on existing SQL databases, and - replication is now disabled permanently instead of temporarily. - Replication is enabled on an existing database the same way it is - enabled on a new database, with one restriction. The existing - database must configure itself as the initial master of a new - replication group. To disable replication on a - database permanently, use <code class="literal">pragma replication=OFF;</code>. - </p> - <div class="sect2" lang="en" xml:lang="en"> - <div class="titlepage"> - <div> - <div> - <h3 class="title"><a id="idp593704"></a>PRAGMAs With Permanent Effects</h3> - </div> - </div> - </div> - <div class="itemizedlist"> - <ul type="disc"> - <li> - <code class="literal">pragma replication=OFF;</code> - </li> - </ul> - </div> - </div> - <div class="sect2" lang="en" xml:lang="en"> - <div class="titlepage"> - <div> - <div> - <h3 class="title"><a id="idp600544"></a>PRAGMAs That Can Now Operate on Existing Databases</h3> - </div> - </div> - </div> - <div class="itemizedlist"> - <ul type="disc"> - <li> - <code class="literal">pragma replication_local_site="host:port";</code> - </li> - <li> - <code class="literal">pragma replication_initial_master=ON;</code> - </li> - <li> - <code class="literal">pragma replication=ON;</code> - </li> - </ul> - </div> - </div> - </div> + <div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="upgrade_11gr2_53_sql_rep"></a>Replication for Existing Databases in the SQL API</h2></div></div></div><div class="toc"><dl><dt><span class="sect2"><a href="upgrade_11gr2_53_sql_rep.html#idp1192472">PRAGMAs With Permanent Effects</a></span></dt><dt><span class="sect2"><a href="upgrade_11gr2_53_sql_rep.html#idp1199416">PRAGMAs That Can Now Operate on Existing Databases</a></span></dt></dl></div><p> + Replication can now be enabled on existing SQL databases, + and replication is now disabled permanently instead of + temporarily. Replication is enabled on an existing database + the same way it is enabled on a new database, with one + restriction. The existing database must configure itself as + the initial master of a new replication group. To disable + replication on a database permanently, use <code class="literal">pragma + replication=OFF;</code>. + </p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="idp1192472"></a>PRAGMAs With Permanent Effects</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><code class="literal">pragma replication=OFF;</code></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="idp1199416"></a>PRAGMAs That Can Now Operate on Existing Databases</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><code class="literal">pragma + replication_local_site="host:port";</code></li><li><code class="literal">pragma + replication_initial_master=ON;</code></li><li><code class="literal">pragma replication=ON;</code></li></ul></div></div>\ +</div> <div class="navfooter"> <hr /> <table width="100%" summary="Navigation footer"> diff --git a/docs/installation/upgrade_11gr2_53_xa_mvcc.html b/docs/installation/upgrade_11gr2_53_xa_mvcc.html index 0b063d4c..2af67d18 100644 --- a/docs/installation/upgrade_11gr2_53_xa_mvcc.html +++ b/docs/installation/upgrade_11gr2_53_xa_mvcc.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_53_toc.html" title="Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> + <link rel="up" href="upgrade_53_toc.html" title="Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3" /> <link rel="prev" href="upgrade_11gr2_53_sql_rep.html" title="Replication for Existing Databases in the SQL API" /> <link rel="next" href="changelog_5_3.html" title="Berkeley DB Library Version 11.2.5.3 Change Log" /> </head> <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="upgrade_11gr2_53_sql_rep.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th width="60%" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> <td width="20%" align="right"> <a accesskey="n" href="changelog_5_3.html">Next</a></td> </tr> </table> @@ -38,13 +36,13 @@ </div> </div> </div> - <p> - The transactions managed by the Berkeley DB X/open compliant XA - resource manager can now be enabled for transaction snapshots. To - enable snapshots open an XA managed database with the flag, - <code class="literal">DB_MULTIVERSION</code>, and all XA managed - transactions that operate on that database will use transaction - snapshots. + <p> + The transactions managed by the Berkeley DB X/open + compliant XA resource manager can now be enabled for + transaction snapshots. To enable snapshots open an XA managed + database with the flag, <code class="literal">DB_MULTIVERSION</code>, + and all XA managed transactions that operate on that database + will use transaction snapshots. </p> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_11gr2_autoinit.html b/docs/installation/upgrade_11gr2_autoinit.html index 14602ad5..f6f62095 100644 --- a/docs/installation/upgrade_11gr2_autoinit.html +++ b/docs/installation/upgrade_11gr2_autoinit.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> <link rel="prev" href="upgrade_11gr2_dbsqlcodegen.html" title="db_sql Renamed to db_sql_codegen" /> <link rel="next" href="upgrade_11gr2_repmgr.html" title="Support for Multiple Client-to-Client Peers" /> </head> <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="upgrade_11gr2_dbsqlcodegen.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </th> + <th width="60%" align="center">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_repmgr.html">Next</a></td> </tr> </table> @@ -39,12 +37,15 @@ </div> </div> <p> -In this release, the <code class="literal">DB_REP_CONF_NOAUTOINIT</code> flag is replaced by the -<code class="literal">DB_REP_CONF_AUTOINIT</code> flag. This option is ON by default. To turn -off automatic internal initialization, call the -<code class="literal">DB_ENV->rep_set_config</code> method with the <span class="bold"><strong>which</strong></span> parameter set to -<code class="literal">DB_REP_CONF_AUTOINIT</code> and the <span class="bold"><strong>onoff</strong></span> parameter set to zero. -</p> + In this release, the + <code class="literal">DB_REP_CONF_NOAUTOINIT</code> flag is replaced + by the <code class="literal">DB_REP_CONF_AUTOINIT</code> flag. This + option is ON by default. To turn off automatic internal + initialization, call the + <code class="literal">DB_ENV->rep_set_config</code> method with the + <span class="bold"><strong>which</strong></span> parameter set to + <code class="literal">DB_REP_CONF_AUTOINIT</code> and the <span class="bold"><strong>onoff</strong></span> parameter set to zero. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/upgrade_11gr2_dbsqlcodegen.html b/docs/installation/upgrade_11gr2_dbsqlcodegen.html index d0e0a15f..f4c91958 100644 --- a/docs/installation/upgrade_11gr2_dbsqlcodegen.html +++ b/docs/installation/upgrade_11gr2_dbsqlcodegen.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> - <link rel="prev" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="prev" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> <link rel="next" href="upgrade_11gr2_autoinit.html" title="DB_REP_CONF_NOAUTOINIT Replaced" /> </head> <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="upgrade_11gr2_toc.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </th> + <th width="60%" align="center">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_autoinit.html">Next</a></td> </tr> </table> @@ -38,8 +36,13 @@ </div> </div> </div> - <p> -The db_sql utility is now called db_sql_codegen. This command line utility is not built by default. To build db_sql_codegen, specify <code class="literal">--enable-sql_codegen</code> when configuring Berkeley DB.</p> + <p> + The db_sql utility is now called db_sql_codegen. This + command line utility is not built by default. To build + db_sql_codegen, specify + <code class="literal">--enable-sql_codegen</code> when configuring + Berkeley DB. + </p> </div> <div class="navfooter"> <hr /> @@ -52,9 +55,7 @@ The db_sql utility is now called db_sql_codegen. This command line utility is no <td width="40%" align="right"> <a accesskey="n" href="upgrade_11gr2_autoinit.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </td> + <td width="40%" align="left" valign="top">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/upgrade_11gr2_remsupp.html b/docs/installation/upgrade_11gr2_remsupp.html index 4d9129e0..e8176221 100644 --- a/docs/installation/upgrade_11gr2_remsupp.html +++ b/docs/installation/upgrade_11gr2_remsupp.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> <link rel="prev" href="build_unix_db_nosync.html" title="DB_NOSYNC Flag to Flush Files" /> <link rel="next" href="build_unix_stacksize.html" title="Changing Stack Size" /> </head> <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="build_unix_db_nosync.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </th> + <th width="60%" align="center">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_stacksize.html">Next</a></td> </tr> </table> @@ -39,13 +37,17 @@ </div> </div> <p> -Berkeley DB no longer supports Visual Studio 6.0. The earliest -version supported is Visual Studio 2005. The build files for Windows Visual Studio 6.0 are removed. -</p> - <p>Berkeley DB no longer supports Win9X, Windows Me (Millenium edition), and Windows NT 4.0. The minimum supported windows platform is Windows 2000.</p> + Berkeley DB no longer supports Visual Studio 6.0. The + earliest version supported is Visual Studio 2005. The build + files for Windows Visual Studio 6.0 are removed. + </p> <p> - -</p> + Berkeley DB no longer supports Win9X, Windows Me + (Millenium edition), and Windows NT 4.0. The minimum + supported windows platform is Windows 2000. + </p> + <p> + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/upgrade_11gr2_repmgr.html b/docs/installation/upgrade_11gr2_repmgr.html index 6a95dbc3..a983f383 100644 --- a/docs/installation/upgrade_11gr2_repmgr.html +++ b/docs/installation/upgrade_11gr2_repmgr.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> + <link rel="up" href="upgrade_11gr2_toc.html" title="Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0" /> <link rel="prev" href="upgrade_11gr2_autoinit.html" title="DB_REP_CONF_NOAUTOINIT Replaced" /> <link rel="next" href="build_unix_encrypt.html" title="Cryptography Support" /> </head> <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="upgrade_11gr2_autoinit.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </th> + <th width="60%" align="center">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </th> <td width="20%" align="right"> <a accesskey="n" href="build_unix_encrypt.html">Next</a></td> </tr> </table> @@ -39,29 +37,36 @@ </div> </div> <p> -A Berkeley DB Replication Manager application can now designate one or more -remote sites (called its "peers") to receive client-to-client requests. -</p> + A Berkeley DB Replication Manager application can now + designate one or more remote sites (called its "peers") to + receive client-to-client requests. + </p> + <p> + In previous releases, there could be only one peer at a + time. If you called the + <code class="literal">DB_ENV->repmgr_add_remote_site</code> method + specifying site "A" as a peer and you made another call + specifying site "B" as a peer, site "B" would become the only + peer, and site "A" would no longer be a peer. + </p> + <p> + Starting with Berkeley DB 11gR2, the same sequence of calls + results in both site "A" and site "B" being possible peers. + Replication Manager may select any of a site's possible peers + to use for client-to-client requests. If the first peer that + the Replication Manager selects cannot be used (for example, + it is unavailable or it is the current master), Replication + Manager attempts to use a different peer if there is more than + one peer. + </p> <p> -In previous releases, there could be only one peer at a time. If you -called the <code class="literal">DB_ENV->repmgr_add_remote_site</code> method specifying -site "A" as a peer and you made another call specifying site "B" as a peer, -site "B" would become the only peer, and site "A" would no longer be a peer. -</p> - <p> -Starting with Berkeley DB 11gR2, the same sequence of calls results in both -site "A" and site "B" being possible peers. Replication Manager may select -any of a site's possible peers to use for client-to-client requests. If the -first peer that the Replication Manager selects cannot be used (for example, it is -unavailable or it is the current master), Replication Manager attempts to -use a different peer if there is more than one peer. -</p> - <p> -To get the pre-11gR2 peer behavior in this example, you must -make an additional call to the <code class="literal">DB_ENV->repmgr_add_remote_site</code> method, -specifying site "A" and a flag value that excludes the <code class="literal">DB_REPMGR_PEER</code> -bit value to remove site "A" as a possible peer. -</p> + To get the pre-11gR2 peer behavior in this example, you + must make an additional call to the + <code class="literal">DB_ENV->repmgr_add_remote_site</code> method, + specifying site "A" and a flag value that excludes the + <code class="literal">DB_REPMGR_PEER</code> bit value to remove site + "A" as a possible peer. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/upgrade_11gr2_toc.html b/docs/installation/upgrade_11gr2_toc.html index 4a3d9b15..cdec88ea 100644 --- a/docs/installation/upgrade_11gr2_toc.html +++ b/docs/installation/upgrade_11gr2_toc.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> - <title>Chapter 12. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0</title> + <title>Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0</title> <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> @@ -14,13 +14,11 @@ <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 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </th> + <th colspan="3" align="center">Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="changelog_5_1.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="upgrade_11gr2_toc"></a>Chapter 12. - Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 - </h2> + <h2 class="title"><a id="upgrade_11gr2_toc"></a>Chapter 14. Upgrading Berkeley DB 4.8 applications to Berkeley DB 11.2.5.0 </h2> </div> </div> </div> @@ -94,22 +90,22 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp872512">Changes between 11.2.5.0.26 and 11.2.5.0.32</a> + <a href="changelog_5_0.html#idp1469256">Changes between 11.2.5.0.26 and 11.2.5.0.32</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp863208">Changes between 11.2.5.0.21 and 11.2.5.0.26</a> + <a href="changelog_5_0.html#idp1470160">Changes between 11.2.5.0.21 and 11.2.5.0.26</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp851296">Changes between 4.8 and 11.2.5.0.21</a> + <a href="changelog_5_0.html#idp1448240">Changes between 4.8 and 11.2.5.0.21</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_0.html#idp883672">Known Bugs</a> + <a href="changelog_5_0.html#idp1481264">Known Bugs</a> </span> </dt> </dl> @@ -124,12 +120,13 @@ </div> </div> </div> - <p>The following pages describe how to upgrade applications coded against - the Berkeley DB 4.8 release interfaces to the Berkeley DB - 11<span class="emphasis"><em>g</em></span> Release 2 interfaces. (Library version - 11.2.5.0). - This information does not describe how to upgrade Berkeley DB 1.85 - release applications.</p> + <p> + The following pages describe how to upgrade applications + coded against the Berkeley DB 4.8 release interfaces to the + Berkeley DB 11<span class="emphasis"><em>g</em></span> Release 2 interfaces. + (Library version 11.2.5.0). This information does not describe + how to upgrade Berkeley DB 1.85 release applications. + </p> </div> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_4_8_disk.html b/docs/installation/upgrade_4_8_disk.html index 2860789f..52e39785 100644 --- a/docs/installation/upgrade_4_8_disk.html +++ b/docs/installation/upgrade_4_8_disk.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> + <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> <link rel="prev" href="upgrade_4_8_fcntl.html" title="Dropped Support for fcntl System Calls" /> <link rel="next" href="changelog_4_8.html" title="Berkeley DB 4.8.28 Change Log" /> </head> <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,7 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="upgrade_4_8_fcntl.html">Prev</a> </td> - <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> + <th width="60%" align="center">Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> <td width="20%" align="right"> <a accesskey="n" href="changelog_4_8.html">Next</a></td> </tr> </table> @@ -37,22 +37,22 @@ </div> </div> <p> - The log file format changed in the Berkeley DB 4.8 release. -</p> - <p> - No database formats changed in the Berkeley DB 4.8 release. -</p> - <p> - The Berkeley DB 4.8 release does not support live replication upgrade from the - 4.2 or 4.3 releases, only from the 4.4 and later releases. -</p> - <p> - For further information on upgrading Berkeley DB installations, see the - - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/upgrading/index.html" target="_top"> - Berkeley DB Upgrade Guide. - </a> -</p> + The log file format changed in the Berkeley DB 4.8 release. + </p> + <p> + No database formats changed in the Berkeley DB 4.8 release. + </p> + <p> + The Berkeley DB 4.8 release does not support live + replication upgrade from the 4.2 or 4.3 releases, only from + the 4.4 and later releases. + </p> + <p> + For further information on upgrading Berkeley DB + installations, see the + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/upgrading/index.html" target="_top"> + Berkeley DB Upgrade Guide. </a> + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/upgrade_4_8_dpl.html b/docs/installation/upgrade_4_8_dpl.html index da0005fd..e9d3b6fc 100644 --- a/docs/installation/upgrade_4_8_dpl.html +++ b/docs/installation/upgrade_4_8_dpl.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> - <link rel="prev" href="upgrade_4_8_toc.html" title="Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> + <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> + <link rel="prev" href="upgrade_4_8_toc.html" title="Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> <link rel="next" href="upgrade_4_8_mpool.html" title="Minor Change in Behavior of DB_MPOOLFILE->get" /> </head> <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,7 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="upgrade_4_8_toc.html">Prev</a> </td> - <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> + <th width="60%" align="center">Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_4_8_mpool.html">Next</a></td> </tr> </table> @@ -37,41 +37,45 @@ </div> </div> <p> - Entity subclasses that define secondary keys must now be registered - prior to storing an instance of the class. This can be done in two - ways: -</p> + Entity subclasses that define secondary keys must now be + registered prior to storing an instance of the class. This can + be done in two ways: + </p> <div class="itemizedlist"> <ul type="disc"> <li> - <p> - The <code class="methodname">EntityModel.registerClass()</code> method - may be called to register the subclass before opening the - entity store. - </p> + <p> + The + <code class="methodname">EntityModel.registerClass()</code> + method may be called to register the subclass before + opening the entity store. + </p> </li> <li> - <p> - The <code class="methodname">EntityStore.getSubclassIndex()</code> - method may be called to implicitly register the subclass after - opening the entity store. - </p> + <p> + The + <code class="methodname">EntityStore.getSubclassIndex()</code> + method may be called to implicitly register the + subclass after opening the entity store. + </p> </li> </ul> </div> - <p> - Failure to register the entity subclass will result in an - <code class="classname">IllegalArgumentException</code> the first time an - attempt is made to store an instance of the subclass. An exception will - not occur if instances of the subclass have previously been stored, - which allows existing applications to run unmodified in most cases. -</p> - <p> - This behavioral change was made to increase reliability. In several - cases, registering an entity subclass has been necessary as a - workaround. The requirement to register the subclass will ensure that - such errors do not occur in deployed applications. -</p> + <p> + Failure to register the entity subclass will result in an + <code class="classname">IllegalArgumentException</code> the first + time an attempt is made to store an instance of the subclass. + An exception will not occur if instances of the subclass have + previously been stored, which allows existing applications to + run unmodified in most cases. + </p> + <p> + This behavioral change was made to increase reliability. In + several cases, registering an entity subclass has been + necessary as a workaround. The requirement to register the + subclass will ensure that such errors do not occur in deployed + applications. + </p> </div> <div class="navfooter"> <hr /> @@ -84,7 +88,7 @@ <td width="40%" align="right"> <a accesskey="n" href="upgrade_4_8_mpool.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8 </td> + <td width="40%" align="left" valign="top">Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8 </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/upgrade_4_8_fcntl.html b/docs/installation/upgrade_4_8_fcntl.html index d45da302..6fc1784e 100644 --- a/docs/installation/upgrade_4_8_fcntl.html +++ b/docs/installation/upgrade_4_8_fcntl.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> + <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> <link rel="prev" href="upgrade_4_8_mpool.html" title="Minor Change in Behavior of DB_MPOOLFILE->get" /> <link rel="next" href="upgrade_4_8_disk.html" title="Upgrade Requirements" /> </head> <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,7 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="upgrade_4_8_mpool.html">Prev</a> </td> - <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> + <th width="60%" align="center">Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_4_8_disk.html">Next</a></td> </tr> </table> @@ -36,12 +36,13 @@ </div> </div> </div> - <p> - Berkeley DB no longer supports mutex implementations based on the - <code class="literal">fcntl</code> system call. If you have been configuring - Berkeley DB to use this type of mutex, you need to either switch to a - different mutex type or contact the Berkeley DB team for support. -</p> + <p> + Berkeley DB no longer supports mutex implementations based + on the <code class="literal">fcntl</code> system call. If you have been + configuring Berkeley DB to use this type of mutex, you need to + either switch to a different mutex type or contact the + Berkeley DB team for support. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/upgrade_4_8_mpool.html b/docs/installation/upgrade_4_8_mpool.html index d012f147..368161d6 100644 --- a/docs/installation/upgrade_4_8_mpool.html +++ b/docs/installation/upgrade_4_8_mpool.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> + <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> <link rel="prev" href="upgrade_4_8_dpl.html" title="Registering DPL Secondary Keys" /> <link rel="next" href="upgrade_4_8_fcntl.html" title="Dropped Support for fcntl System Calls" /> </head> <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,7 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="upgrade_4_8_dpl.html">Prev</a> </td> - <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> + <th width="60%" align="center">Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_4_8_fcntl.html">Next</a></td> </tr> </table> @@ -37,27 +37,30 @@ </div> </div> <p> - DB 4.8 introduces some performance enhancements, based on the use - of shared/exclusive latches instead of locks in some areas of the - internal buffer management code. This change will affect how the - <code class="classname">DB_MPOOL</code> interface handles dirty buffers. -</p> - <p> Because of these - changes, <code class="methodname">DB_MPOOLFILE->get</code> will now - acquire an exclusive latch on the buffer if - the <code class="literal">DB_MPOOL_DIRTY</code> - or <code class="literal">DB_MPOOL_EDIT</code> flags are specified. This - could lead to an application deadlock if the application tries to - fetch the buffer again, without an - intervening <code class="methodname">DB_MPOOLFILE->put</code> call. -</p> + DB 4.8 introduces some performance enhancements, based on + the use of shared/exclusive latches instead of locks in some + areas of the internal buffer management code. This change will + affect how the <code class="classname">DB_MPOOL</code> interface + handles dirty buffers. + </p> + <p> + Because of these changes, + <code class="methodname">DB_MPOOLFILE->get</code> will now + acquire an exclusive latch on the buffer if the + <code class="literal">DB_MPOOL_DIRTY</code> or + <code class="literal">DB_MPOOL_EDIT</code> flags are specified. This + could lead to an application deadlock if the application tries + to fetch the buffer again, without an intervening + <code class="methodname">DB_MPOOLFILE->put</code> call. + </p> <p> - If your application uses the <code class="literal">DB_MPOOL</code> - interface, and especially the <code class="literal">DB_MPOOL_DIRTY</code> - and <code class="literal">DB_MPOOL_EDIT</code> flags, you should review your - code to ensure that this behavior change does not cause your - application to deadlock. -</p> + If your application uses the <code class="literal">DB_MPOOL</code> + interface, and especially the + <code class="literal">DB_MPOOL_DIRTY</code> and + <code class="literal">DB_MPOOL_EDIT</code> flags, you should review + your code to ensure that this behavior change does not cause + your application to deadlock. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/upgrade_4_8_toc.html b/docs/installation/upgrade_4_8_toc.html index 1a321950..51249743 100644 --- a/docs/installation/upgrade_4_8_toc.html +++ b/docs/installation/upgrade_4_8_toc.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> - <title>Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</title> + <title>Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</title> <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> @@ -14,11 +14,11 @@ <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 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> + <th colspan="3" align="center">Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="changelog_5_0.html">Prev</a> </td> @@ -32,7 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="upgrade_4_8_toc"></a>Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</h2> + <h2 class="title"><a id="upgrade_4_8_toc"></a>Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</h2> </div> </div> </div> @@ -75,183 +75,183 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp908504"> + <a href="changelog_4_8.html#idp1293368"> Changes between 4.8.26 and 4.8.28:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp853904"> + <a href="changelog_4_8.html#idp1497568"> Known bugs in 4.8 </a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp885088"> + <a href="changelog_4_8.html#idp1482176"> Changes between 4.8.24 and 4.8.26:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp907544"> + <a href="changelog_4_8.html#idp1475624"> Changes between 4.8.21 and 4.8.24:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp853432"> + <a href="changelog_4_8.html#idp1553248"> Changes between 4.7 and 4.8.21:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp944680"> + <a href="changelog_4_8.html#idp1542376"> Database or Log File On-Disk Format Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp875992"> + <a href="changelog_4_8.html#idp1323496"> New Features:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp945096"> + <a href="changelog_4_8.html#idp1471240"> Database Environment Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp953944"> + <a href="changelog_4_8.html#idp1552400"> Concurrent Data Store Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp954344"> + <a href="changelog_4_8.html#idp1552800"> General Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp964688"> + <a href="changelog_4_8.html#idp1562416"> Btree Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp962400"> + <a href="changelog_4_8.html#idp1560192"> Hash Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp972744"> + <a href="changelog_4_8.html#idp1570528"> Queue Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp973816"> + <a href="changelog_4_8.html#idp1478984"> Recno Access Method Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp959840"> + <a href="changelog_4_8.html#idp1558464"> C-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp964968"> + <a href="changelog_4_8.html#idp1562696"> C++-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp985536"> + <a href="changelog_4_8.html#idp1583472"> Java-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp978792"> + <a href="changelog_4_8.html#idp1577104"> Direct Persistence Layer (DPL), Bindings and Collections API:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp979064"> + <a href="changelog_4_8.html#idp1576792"> Tcl-specific API Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp991048"> + <a href="changelog_4_8.html#idp1588984"> RPC-specific Client/Server Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp992632"> + <a href="changelog_4_8.html#idp1576880"> Replication Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp988920"> + <a href="changelog_4_8.html#idp1586856"> XA Resource Manager Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp994464"> + <a href="changelog_4_8.html#idp1592504"> Locking Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp987808"> + <a href="changelog_4_8.html#idp1585688"> Logging Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1005064"> + <a href="changelog_4_8.html#idp1603104"> Memory Pool Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1005456"> + <a href="changelog_4_8.html#idp1592944"> Mutex Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp987512"> + <a href="changelog_4_8.html#idp1585392"> Test Suite Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp996512"> + <a href="changelog_4_8.html#idp1594608"> Transaction Subsystem Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1018456"> + <a href="changelog_4_8.html#idp1588800"> Utility Changes:</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_4_8.html#idp1020896"> + <a href="changelog_4_8.html#idp1618888"> Configuration, Documentation, Sample Application, Portability and Build Changes:</a> </span> </dt> @@ -267,10 +267,13 @@ Configuration, Documentation, Sample Application, Portability and Build Changes: </div> </div> </div> - <p>The following pages describe how to upgrade applications coded against -the Berkeley DB 4.7 release interfaces to the Berkeley DB 4.8 release interfaces. -This information does not describe how to upgrade Berkeley DB 1.85 release -applications.</p> + <p> + The following pages describe how to upgrade applications + coded against the Berkeley DB 4.7 release interfaces to the + Berkeley DB 4.8 release interfaces. This information does not + describe how to upgrade Berkeley DB 1.85 release + applications. + </p> </div> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_51_toc.html b/docs/installation/upgrade_51_toc.html index a783dfb7..ee3f533d 100644 --- a/docs/installation/upgrade_51_toc.html +++ b/docs/installation/upgrade_51_toc.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> - <title>Chapter 11. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1</title> + <title>Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1</title> <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> @@ -14,13 +14,11 @@ <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 11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </th> + <th colspan="3" align="center">Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="changelog_5_2.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="upgrade_51_toc"></a>Chapter 11. - Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 - </h2> + <h2 class="title"><a id="upgrade_51_toc"></a>Chapter 13. Upgrading Berkeley DB 11.2.5.0 applications to Berkeley DB 11.2.5.1 </h2> </div> </div> </div> @@ -79,122 +75,122 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp799888">Database or Log File On-Disk Format Changes</a> + <a href="changelog_5_1.html#idp1395416">Database or Log File On-Disk Format Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp792216">New Features</a> + <a href="changelog_5_1.html#idp1335544">New Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp787976">Database Environment Changes</a> + <a href="changelog_5_1.html#idp1322264">Database Environment Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp806432">Concurrent Data Store Changes</a> + <a href="changelog_5_1.html#idp1402240">Concurrent Data Store Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp727768">Access Method Changes</a> + <a href="changelog_5_1.html#idp1322352">Access Method Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp795776">API Changes</a> + <a href="changelog_5_1.html#idp1395912">API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp802264">SQL-Specific API Changes</a> + <a href="changelog_5_1.html#idp1398072">SQL-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp803624">Tcl-Specific API Changes</a> + <a href="changelog_5_1.html#idp1399432">Tcl-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp799176">Java-Specific API Changes</a> + <a href="changelog_5_1.html#idp1394704">Java-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp734296">C#-Specific API Changes</a> + <a href="changelog_5_1.html#idp1391096">C#-Specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp807320">Direct Persistence Layer (DPL), Bindings and Collections API</a> + <a href="changelog_5_1.html#idp1412856">Direct Persistence Layer (DPL), Bindings and Collections API</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp816672">Replication Changes</a> + <a href="changelog_5_1.html#idp1412472">Replication Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp827552">Locking Subsystem Changes</a> + <a href="changelog_5_1.html#idp1423304">Locking Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp839224">Logging Subsystem Changes</a> + <a href="changelog_5_1.html#idp1436016">Logging Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp822992">Memory Pool Subsystem Changes</a> + <a href="changelog_5_1.html#idp1418744">Memory Pool Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp827368">Mutex Subsystem Changes</a> + <a href="changelog_5_1.html#idp1423120">Mutex Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp836200">Transaction Subsystem Changes</a> + <a href="changelog_5_1.html#idp1431840">Transaction Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp813832">Test Suite Changes</a> + <a href="changelog_5_1.html#idp1409688">Test Suite Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp834616">Utility Changes</a> + <a href="changelog_5_1.html#idp1430312">Utility Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp837928">Configuration, Documentation, Sample Apps, Portability, and Build Changes</a> + <a href="changelog_5_1.html#idp1433952">Configuration, Documentation, Sample Apps, Portability, and Build Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp828192">Example Changes</a> + <a href="changelog_5_1.html#idp1423944">Example Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp848592">Miscellaneous Bug Fixes</a> + <a href="changelog_5_1.html#idp1445752">Miscellaneous Bug Fixes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp846464">Deprecated Features</a> + <a href="changelog_5_1.html#idp1443624">Deprecated Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_1.html#idp847112">Known Bugs</a> + <a href="changelog_5_1.html#idp1444272">Known Bugs</a> </span> </dt> </dl> @@ -210,22 +206,20 @@ </div> </div> <p> - The following pages describe how to upgrade applications coded against - the Berkeley DB 11.2.5.0 library to the Berkeley DB - 11.2.5.1 library (both of which belong to Berkeley DB - 11<span class="emphasis"><em>g</em></span> Release 2). - This information does not describe how to upgrade Berkeley DB 1.85 - release applications. - </p> - <p> - For information on the general process of upgrading Berkeley DB - installations and upgrade instructions related to historical releases, see the - - - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/upgrading/index.html" target="_top"> - Berkeley DB Upgrade Guide. - </a> - </p> + The following pages describe how to upgrade + applications coded against the Berkeley DB 11.2.5.0 + library to the Berkeley DB 11.2.5.1 library (both of which + belong to Berkeley DB 11<span class="emphasis"><em>g</em></span> Release 2). + This information does not describe how to upgrade Berkeley + DB 1.85 release applications. + </p> + <p> + For information on the general process of upgrading + Berkeley DB installations and upgrade instructions related + to historical releases, see the + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/upgrading/index.html" target="_top"> + Berkeley DB Upgrade Guide. </a> + </p> </div> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_52_toc.html b/docs/installation/upgrade_52_toc.html index 6d256499..75336ccb 100644 --- a/docs/installation/upgrade_52_toc.html +++ b/docs/installation/upgrade_52_toc.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> - <title>Chapter 10. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2</title> + <title>Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2</title> <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> @@ -14,13 +14,11 @@ <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 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </th> + <th colspan="3" align="center">Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="changelog_5_3.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="upgrade_52_toc"></a>Chapter 10. - Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 - </h2> + <h2 class="title"><a id="upgrade_52_toc"></a>Chapter 12. Upgrading Berkeley DB 11.2.5.1 applications to Berkeley DB 11.2.5.2 </h2> </div> </div> </div> @@ -69,7 +65,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_rep_dbt_readonly.html#idp654424">New Flag</a> + <a href="upgrade_11gr2_52_rep_dbt_readonly.html#idp1248208">New Flag</a> </span> </dt> </dl> @@ -83,12 +79,12 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_dyn_env.html#idp611120">New Functions</a> + <a href="upgrade_11gr2_52_dyn_env.html#idp1243744">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_dyn_env.html#idp659088">Deprecated Functions</a> + <a href="upgrade_11gr2_52_dyn_env.html#idp1252704">Deprecated Functions</a> </span> </dt> </dl> @@ -107,37 +103,37 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp676752">Upgrading</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1270248">Upgrading</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp657144">New Functions</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1250760">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp655568">Modified Functions</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1249616">Modified Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp602496">New Events</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1129176">New Events</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp684960">Removed Functions</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1278544">Removed Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp650072">New Parameters</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1245336">New Parameters</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_grp_mbr.html#idp671784">New Structure</a> + <a href="upgrade_11gr2_52_grp_mbr.html#idp1265176">New Structure</a> </span> </dt> </dl> @@ -151,17 +147,17 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_heap.html#idp683880">New Functions</a> + <a href="upgrade_11gr2_52_heap.html#idp1277464">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_heap.html#idp677456">Modified Functions</a> + <a href="upgrade_11gr2_52_heap.html#idp1270952">Modified Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_heap.html#idp678808">New Definition</a> + <a href="upgrade_11gr2_52_heap.html#idp1272304">New Definition</a> </span> </dt> </dl> @@ -175,7 +171,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_mvcc_sql.html#idp698336">New Pragmas</a> + <a href="upgrade_11gr2_52_mvcc_sql.html#idp1291928">New Pragmas</a> </span> </dt> </dl> @@ -194,7 +190,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_rep_sql.html#idp709672">New Pragmas</a> + <a href="upgrade_11gr2_52_rep_sql.html#idp1303192">New Pragmas</a> </span> </dt> </dl> @@ -208,21 +204,22 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_repmgr_channels.html#idp704400">New Functions</a> + <a href="upgrade_11gr2_52_repmgr_channels.html#idp1249368">New Functions</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> - <a href="upgrade_11gr2_52_seq_sql.html">Sequence Support in the SQL Layer</a> + <a href="upgrade_11gr2_52_seq_sql.html">Sequence Support in the + SQL Layer</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_seq_sql.html#idp710392">New Functions</a> + <a href="upgrade_11gr2_52_seq_sql.html#idp1303976">New Functions</a> </span> </dt> </dl> @@ -236,17 +233,17 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_xa.html#idp720184">Constraints</a> + <a href="upgrade_11gr2_52_xa.html#idp1314200">Constraints</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_xa.html#idp725120">New Flag</a> + <a href="upgrade_11gr2_52_xa.html#idp1319928">New Flag</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_52_xa.html#idp729168">Modified Function</a> + <a href="upgrade_11gr2_52_xa.html#idp1324040">Modified Function</a> </span> </dt> </dl> @@ -265,112 +262,112 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp719568">Database or Log File On-Disk Format Changes</a> + <a href="changelog_5_2.html#idp1313480">Database or Log File On-Disk Format Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp725640">New Features</a> + <a href="changelog_5_2.html#idp1320448">New Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp731112">Database Environment Changes</a> + <a href="changelog_5_2.html#idp1304040">Database Environment Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp742672">Concurrent Data Store Changes</a> + <a href="changelog_5_2.html#idp1337840">Concurrent Data Store Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp736048">Access Method Changes</a> + <a href="changelog_5_2.html#idp1331240">Access Method Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp736464">SQL API Changes</a> + <a href="changelog_5_2.html#idp1319744">SQL API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp719112">C API Changes</a> + <a href="changelog_5_2.html#idp1312960">C API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp743448">Tcl-specific API Changes</a> + <a href="changelog_5_2.html#idp1338616">Tcl-specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp749040">C#-specific API Changes</a> + <a href="changelog_5_2.html#idp1313048">C#-specific API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp741376">Replication Changes</a> + <a href="changelog_5_2.html#idp1336544">Replication Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp743864">Locking Subsystem Changes</a> + <a href="changelog_5_2.html#idp1339000">Locking Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp749456">Logging Subsystem Changes</a> + <a href="changelog_5_2.html#idp1352672">Logging Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp763176">Memory Pool Subsystem Changes</a> + <a href="changelog_5_2.html#idp1334816">Memory Pool Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp765792">Mutex Subsystem Changes</a> + <a href="changelog_5_2.html#idp1360960">Mutex Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp766552">Transaction Subsystem Changes</a> + <a href="changelog_5_2.html#idp1353088">Transaction Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp763560">Test Suite Changes</a> + <a href="changelog_5_2.html#idp1345456">Test Suite Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp776568">Utility Changes</a> + <a href="changelog_5_2.html#idp1371840">Utility Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp766936">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> + <a href="changelog_5_2.html#idp1373456">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp780312">Example Changes</a> + <a href="changelog_5_2.html#idp1345232">Example Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp781208">Miscellaneous Bug Fixes</a> + <a href="changelog_5_2.html#idp1376368">Miscellaneous Bug Fixes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp782744">Deprecated Features</a> + <a href="changelog_5_2.html#idp1377904">Deprecated Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_2.html#idp785040">Known Bugs</a> + <a href="changelog_5_2.html#idp1379824">Known Bugs</a> </span> </dt> </dl> @@ -386,22 +383,20 @@ </div> </div> <p> - The following pages describe how to upgrade applications coded against - the Berkeley DB 11.2.5.1 library to the Berkeley DB - 11.2.5.2 library (both of which belong to Berkeley DB - 11<span class="emphasis"><em>g</em></span> Release 2). - This information does not describe how to upgrade Berkeley DB 1.85 - release applications. - </p> + The following pages describe how to upgrade + applications coded against the Berkeley DB 11.2.5.1 + library to the Berkeley DB 11.2.5.2 library (both of which + belong to Berkeley DB 11<span class="emphasis"><em>g</em></span> Release 2). + This information does not describe how to upgrade Berkeley + DB 1.85 release applications. + </p> <p> - For information on the general process of upgrading Berkeley DB - installations and upgrade instructions related to historical releases, see the - - - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/upgrading/index.html" target="_top"> - Berkeley DB Upgrade Guide. - </a> - </p> + For information on the general process of upgrading + Berkeley DB installations and upgrade instructions related + to historical releases, see the + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/upgrading/index.html" target="_top"> + Berkeley DB Upgrade Guide. </a> + </p> </div> </div> <div class="navfooter"> diff --git a/docs/installation/upgrade_53_toc.html b/docs/installation/upgrade_53_toc.html index f14a91df..4e5f3290 100644 --- a/docs/installation/upgrade_53_toc.html +++ b/docs/installation/upgrade_53_toc.html @@ -3,27 +3,25 @@ <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> - <title>Chapter 9. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3</title> + <title>Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3</title> <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> <link rel="up" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="prev" href="build_vxworks_faq.html" title="VxWorks FAQ" /> + <link rel="prev" href="changelog_6_0.html" title="Berkeley DB Library Version 12.1.6.0 Change Log" /> <link rel="next" href="upgrade_11gr2_53_build_windows.html" title="Changes to the build_windows Folder" /> </head> <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 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </th> + <th colspan="3" align="center">Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </th> </tr> <tr> - <td width="20%" align="left"><a accesskey="p" href="build_vxworks_faq.html">Prev</a> </td> + <td width="20%" align="left"><a accesskey="p" href="changelog_6_0.html">Prev</a> </td> <th width="60%" align="center"> </th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_build_windows.html">Next</a></td> </tr> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="upgrade_53_toc"></a>Chapter 9. - Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 - </h2> + <h2 class="title"><a id="upgrade_53_toc"></a>Chapter 11. Upgrading Berkeley DB 11.2.5.2 applications to Berkeley DB 11.2.5.3 </h2> </div> </div> </div> @@ -64,17 +60,17 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_conn_status.html#idp506032">New Function</a> + <a href="upgrade_11gr2_53_conn_status.html#idp1160632">New Function</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_conn_status.html#idp531112">New Class</a> + <a href="upgrade_11gr2_53_conn_status.html#idp1116080">New Class</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_conn_status.html#idp564984">Deprecated Function</a> + <a href="upgrade_11gr2_53_conn_status.html#idp1164288">Deprecated Function</a> </span> </dt> </dl> @@ -88,7 +84,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_excl.html#idp567208">New Functions</a> + <a href="upgrade_11gr2_53_excl.html#idp1166512">New Functions</a> </span> </dt> </dl> @@ -102,7 +98,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_heap_regionsize.html#idp570008">New Functions</a> + <a href="upgrade_11gr2_53_heap_regionsize.html#idp1093968">New Functions</a> </span> </dt> </dl> @@ -116,22 +112,22 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp571040">New Functions</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1170128">New Functions</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp560912">Flags Accepted by DB_ENV->backup()</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1175656">Flags Accepted by DB_ENV->backup()</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp578624">Flags Accepted by DB_ENV->dbbackup()</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1177648">Flags Accepted by DB_ENV->dbbackup()</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_hotbackup.html#idp584448">Enumerations Accepted by DB_ENV->set_backup_config()</a> + <a href="upgrade_11gr2_53_hotbackup.html#idp1183112">Enumerations Accepted by DB_ENV->set_backup_config()</a> </span> </dt> </dl> @@ -150,7 +146,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_meta_dir.html#idp593384">New Functions</a> + <a href="upgrade_11gr2_53_meta_dir.html#idp1192152">New Functions</a> </span> </dt> </dl> @@ -169,7 +165,7 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_sql_pragma.html#idp599768">New PRAGMAs</a> + <a href="upgrade_11gr2_53_sql_pragma.html#idp1198640">New PRAGMAs</a> </span> </dt> </dl> @@ -183,12 +179,12 @@ <dl> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_sql_rep.html#idp593704">PRAGMAs With Permanent Effects</a> + <a href="upgrade_11gr2_53_sql_rep.html#idp1192472">PRAGMAs With Permanent Effects</a> </span> </dt> <dt> <span class="sect2"> - <a href="upgrade_11gr2_53_sql_rep.html#idp600544">PRAGMAs That Can Now Operate on Existing Databases</a> + <a href="upgrade_11gr2_53_sql_rep.html#idp1199416">PRAGMAs That Can Now Operate on Existing Databases</a> </span> </dt> </dl> @@ -207,82 +203,77 @@ <dl> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp594928">Changes between 11.2.5.3.15 and 11.2.5.3.21</a> + <a href="changelog_5_3.html#idp1207192">Database or Log File On-Disk Format Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp608376">Database or Log File On-Disk Format Changes</a> + <a href="changelog_5_3.html#idp1200256">New Features</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp590024">New Features</a> + <a href="changelog_5_3.html#idp1206088">Database Environment Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp594216">Database Environment Changes</a> + <a href="changelog_5_3.html#idp1211048">Access Method Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp607088">Access Method Changes</a> + <a href="changelog_5_3.html#idp1208744">SQL API Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp616640">SQL API Changes</a> + <a href="changelog_5_3.html#idp1199152">Java-specific API changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp610088">Java-specific API changes</a> + <a href="changelog_5_3.html#idp1208832">Replication Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp616728">Replication Changes</a> + <a href="changelog_5_3.html#idp1199992">Locking Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp594560">Locking Subsystem Changes</a> + <a href="changelog_5_3.html#idp1217800">Logging Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp635880">Logging Subsystem Changes</a> + <a href="changelog_5_3.html#idp1209392">Memory Pool Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp625488">Memory Pool Subsystem Changes</a> + <a href="changelog_5_3.html#idp1226336">Mutex Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp632288">Mutex Subsystem Changes</a> + <a href="changelog_5_3.html#idp1218216">Transaction Subsystem Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp636296">Transaction Subsystem Changes</a> + <a href="changelog_5_3.html#idp1231856">Utility Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp625872">Utility Changes</a> + <a href="changelog_5_3.html#idp1226152">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> </span> </dt> <dt> <span class="sect2"> - <a href="changelog_5_3.html#idp632040">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> - </span> - </dt> - <dt> - <span class="sect2"> - <a href="changelog_5_3.html#idp641456">Known Bugs</a> + <a href="changelog_5_3.html#idp1235024">Known Bugs</a> </span> </dt> </dl> @@ -297,35 +288,33 @@ </div> </div> </div> + <p> + The following pages describe how to upgrade + applications coded against the Berkeley DB 11.2.5.2 + library to the Berkeley DB 11.2.5.3 library (both of which + belong to Berkeley DB 11<span class="emphasis"><em>g</em></span> Release 2). + This information does not describe how to upgrade Berkeley + DB 1.85 release applications. + </p> <p> - The following pages describe how to upgrade applications coded against - the Berkeley DB 11.2.5.2 library to the Berkeley DB - 11.2.5.3 library (both of which belong to Berkeley DB - 11<span class="emphasis"><em>g</em></span> Release 2). - This information does not describe how to upgrade Berkeley DB 1.85 - release applications. - </p> - <p> - For information on the general process of upgrading Berkeley DB - installations and upgrade instructions related to historical releases, see the - - - <a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/upgrading/index.html" target="_top"> - Berkeley DB Upgrade Guide. - </a> - </p> + For information on the general process of upgrading + Berkeley DB installations and upgrade instructions related + to historical releases, see the + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/upgrading/index.html" target="_top"> + Berkeley DB Upgrade Guide. </a> + </p> </div> </div> <div class="navfooter"> <hr /> <table width="100%" summary="Navigation footer"> <tr> - <td width="40%" align="left"><a accesskey="p" href="build_vxworks_faq.html">Prev</a> </td> + <td width="40%" align="left"><a accesskey="p" href="changelog_6_0.html">Prev</a> </td> <td width="20%" align="center"> </td> <td width="40%" align="right"> <a accesskey="n" href="upgrade_11gr2_53_build_windows.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">VxWorks FAQ </td> + <td width="40%" align="left" valign="top">Berkeley DB Library Version 12.1.6.0 Change Log </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/upgrade_60_toc.html b/docs/installation/upgrade_60_toc.html new file mode 100644 index 00000000..6cbfcd17 --- /dev/null +++ b/docs/installation/upgrade_60_toc.html @@ -0,0 +1,346 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="prev" href="changelog_6_1.html" title="Berkeley DB Library Version 12.1.6.1 Change Log" /> + <link rel="next" href="blob-support.html" title="Binary Large Object Support" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="changelog_6_1.html">Prev</a> </td> + <th width="60%" align="center"> </th> + <td width="20%" align="right"> <a accesskey="n" href="blob-support.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="chapter" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title"><a id="upgrade_60_toc"></a>Chapter 10. Upgrading Berkeley DB 11.2.5.3 applications to Berkeley DB 12.1.6.0 </h2> + </div> + </div> + </div> + <div class="toc"> + <p> + <b>Table of Contents</b> + </p> + <dl> + <dt> + <span class="sect1"> + <a href="upgrade_60_toc.html#upgrade_60_intro">Introduction</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="blob-support.html">Binary Large Object Support</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp865296">New Functions</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp998896">New Flags Accepted by Blob Streaming Interfaces</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp1063832">Other New Flags</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="blob-support.html#idp1064912">New Pragma</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="rep_views.html">Replication Views</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="rep_views.html#idp988640">New Function</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="rep_views.html#idp1072824">New Flag</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="bdbsql_ha_more_options.html">Enhanced BDB SQL Replication Options</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="bdbsql_ha_more_options.html#idp1049920">New Pragmas</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="rep_auto_takeover.html">Replication Manager Automatic Takeover</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="rep_auto_takeover.html#idp1079576">New Event</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="sql_logbuf.html">New Berkeley DB SQL API Pragma</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="sql_logbuf.html#idp1083784">New Pragma</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="bdb_sql_encryption.html">UNIX/POSIX SQL Encryption Default</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="seq_datatype.html">Sequence Datatype Changes</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="compare_func.html">Comparison Function Signature Change</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="license_change60.html">License Change</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="sqlite_ver60.html">Updated SQLite Version</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="sun_opt.html">Sun Workshop Compiler Optimization + Level</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="drop_sup60.html">Dropped Support</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="changelog_6_0.html">Berkeley DB Library Version 12.1.6.0 Change Log</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1103464">Database or Log File On-Disk Format Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1085208">New Features</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1091952">Database Environment Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1109616">Concurrent Data Store Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1092040">Access Method Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1102752">API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1105448">SQL-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1118096">Tcl-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1103848">Java-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1108320">C#-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1118512">Replication Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1110216">Locking Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1117712">Logging Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1110304">Memory Pool Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1100424">Mutex Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1117416">Transaction Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1129976">Test Suite Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1127624">Utility Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1137784">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1130360">Example Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1140648">Miscellaneous Bug Fixes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1142544">Deprecated Features</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_0.html#idp1143680">Known Bugs</a> + </span> + </dt> + </dl> + </dd> + </dl> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="upgrade_60_intro"></a>Introduction</h2> + </div> + </div> + </div> + <p> + The following pages describe how to upgrade + applications coded against the Berkeley DB 11.2.5.3 + library (which belongs to Berkeley DB + 11<span class="emphasis"><em>g</em></span> Release 2) to the Berkeley DB + 12.1.6.0 library (which belongs to Berkeley DB + 12<span class="emphasis"><em>c</em></span> Release 1). This information + does not describe how to upgrade Berkeley DB 1.85 release + applications. + </p> + <p> + For information on the general process of upgrading + Berkeley DB installations and upgrade instructions related + to historical releases, see the + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/upgrading/index.html" target="_top"> + Berkeley DB Upgrade Guide. </a> + </p> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="changelog_6_1.html">Prev</a> </td> + <td width="20%" align="center"> </td> + <td width="40%" align="right"> <a accesskey="n" href="blob-support.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">Berkeley DB Library Version 12.1.6.1 Change Log </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Binary Large Object Support</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/upgrade_61_toc.html b/docs/installation/upgrade_61_toc.html new file mode 100644 index 00000000..f137e1a3 --- /dev/null +++ b/docs/installation/upgrade_61_toc.html @@ -0,0 +1,337 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1</title> + <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> + <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> + <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="up" href="index.html" title="Berkeley DB Installation and Build Guide" /> + <link rel="prev" href="build_vxworks_faq.html" title="VxWorks FAQ" /> + <link rel="next" href="fcbc_notif.html" title="Failchk Broadcast Notifications" /> + </head> + <body> + <div xmlns="" class="navheader"> + <div class="libver"> + <p>Library Version 12.1.6.1</p> + </div> + <table width="100%" summary="Navigation header"> + <tr> + <th colspan="3" align="center">Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </th> + </tr> + <tr> + <td width="20%" align="left"><a accesskey="p" href="build_vxworks_faq.html">Prev</a> </td> + <th width="60%" align="center"> </th> + <td width="20%" align="right"> <a accesskey="n" href="fcbc_notif.html">Next</a></td> + </tr> + </table> + <hr /> + </div> + <div class="chapter" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title"><a id="upgrade_61_toc"></a>Chapter 9. Upgrading Berkeley DB 12.1.6.0 applications to Berkeley DB 12.1.6.1 </h2> + </div> + </div> + </div> + <div class="toc"> + <p> + <b>Table of Contents</b> + </p> + <dl> + <dt> + <span class="sect1"> + <a href="upgrade_61_toc.html#upgrade_61_intro">Introduction</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="fcbc_notif.html">Failchk Broadcast Notifications</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="fcbc_notif.html#idp971040">New Parameter Value</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="fcbc_notif.html#idp920240">New Events</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="log_nosync.html">New Logging Option</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="log_nosync.html#idp954784">New Parameter Value</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="repmgr_prefmas.html">Replication Manager Preferred Master + Mode</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="repmgr_prefmas.html#idp972776">New Parameter Values</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="repmgr_inqueue.html">Replication Manager Incoming Queue + Size Limit</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="repmgr_inqueue.html#idp979760">New Functions</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="repmgr_inqueue.html#idp973032">New Event</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="blobdb_format.html">New Database Format for BLOBs</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="sqlite_ver61.html">Updated SQLite Version</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="sqlite_ver61.html#sqlite_db_upgrade_61">Upgrading SQL databases to releases after 6.1.19</a> + </span> + </dt> + </dl> + </dd> + <dt> + <span class="sect1"> + <a href="remlockdetect.html">Removed C# Class</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="dropsupp61.html">Dropped Support</a> + </span> + </dt> + <dt> + <span class="sect1"> + <a href="changelog_6_1.html">Berkeley DB Library Version 12.1.6.1 Change Log</a> + </span> + </dt> + <dd> + <dl> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp987784">Changes between 12.1.6.1.20 and 12.1.6.1.23</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp988168">Changes between 12.1.6.1.19 and 12.1.6.1.20</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp973896">Database or Log File On-Disk Format Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1005736">New Features/Improvements</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1006120">Database Environment Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp991992">Concurrent Data Store Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1006184">Access Method Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1001712">API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1016544">SQL-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1006600">Tcl-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1021880">Java-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1023576">C#-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1024704">C++-specific API Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1022296">Replication Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1005576">Locking Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1028536">Logging Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1029168">Memory Pool Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1027200">Mutex Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1034480">Transaction Subsystem Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1029552">Test Suite Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1031736">Utility Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1039888">Configuration, Documentation, Sample Apps, Portability and Build Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1039640">Example Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1039136">Miscellaneous Bug Fixes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1041536">Platform Certification Changes</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1040680">Deprecated Features</a> + </span> + </dt> + <dt> + <span class="sect2"> + <a href="changelog_6_1.html#idp1043736">Known Bugs</a> + </span> + </dt> + </dl> + </dd> + </dl> + </div> + <div class="sect1" lang="en" xml:lang="en"> + <div class="titlepage"> + <div> + <div> + <h2 class="title" style="clear: both"><a id="upgrade_61_intro"></a>Introduction</h2> + </div> + </div> + </div> + <p> + The following pages describe how to upgrade + applications coded against the Berkeley DB 12.1.6.0 + library (which belongs to Berkeley DB + 12<span class="emphasis"><em>c</em></span> Release 1) to the Berkeley DB + 12.1.6.1 library (which belongs to Berkeley DB + 12<span class="emphasis"><em>c</em></span> Release 1). This information + does not describe how to upgrade Berkeley DB 1.85 release + applications. + </p> + <p> + For information on the general process of upgrading + Berkeley DB installations and upgrade instructions related + to historical releases, see the + <a class="ulink" href="http://docs.oracle.com/cd/E17076_02/html/upgrading/index.html" target="_top"> + Berkeley DB Upgrade Guide. </a> + </p> + </div> + </div> + <div class="navfooter"> + <hr /> + <table width="100%" summary="Navigation footer"> + <tr> + <td width="40%" align="left"><a accesskey="p" href="build_vxworks_faq.html">Prev</a> </td> + <td width="20%" align="center"> </td> + <td width="40%" align="right"> <a accesskey="n" href="fcbc_notif.html">Next</a></td> + </tr> + <tr> + <td width="40%" align="left" valign="top">VxWorks FAQ </td> + <td width="20%" align="center"> + <a accesskey="h" href="index.html">Home</a> + </td> + <td width="40%" align="right" valign="top"> Failchk Broadcast Notifications</td> + </tr> + </table> + </div> + </body> +</html> diff --git a/docs/installation/win_additional_options.html b/docs/installation/win_additional_options.html index 5c01fcb1..8713d2a0 100644 --- a/docs/installation/win_additional_options.html +++ b/docs/installation/win_additional_options.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="win_build_dist_dll.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="build_win_small.html">Next</a></td> </tr> </table> @@ -41,65 +39,113 @@ <p> There are several build options that you can configure when building Berkeley DB on Windows. To specify these, select - <code class="literal">Project Properties</code>-><code class="literal">C/C++</code>-><code class="literal">Command Line</code> - and add the property. + <code class="literal">Project + Properties</code>-><code class="literal">C/C++</code>-><code class="literal">Command + Line</code> and add the property. </p> - <p> - These are some of the additional properties that you can specify - when you are building Berkeley DB on Windows: + <p> + These are some of the additional properties that you can + specify when you are building Berkeley DB on Windows: </p> <div class="itemizedlist"> <ul type="disc"> <li> + <p><a id="HAVE_FAILCHK_BROADCAST"></a> + Enable failchk broadcasting. This feature allows + <a href="../api_reference/C/envfailchk.html" class="olink">DB_ENV->failchk()</a> to inform all processes in the environment + that a failure has occurred. Those processes will return + <a href="../programmer_reference/program_errorret.html#program_errorret.DB_RUNRECOVERY" class="olink"> + DB_RUNRECOVERY + </a> + rather than hanging for an indefinite amount of time. + </p> + </li> + <li> <p><a id="HAVE_LOCALIZATION"></a> <span class="bold"><strong>/D HAVE_LOCALIZATION</strong></span> </p> - <p> + <p> Enable localized error message text, if available. - This option should not be used when - enabling stripped messages. + This option should not be used when enabling stripped + messages. </p> </li> <li> <p><a id="HAVE_MIXED_SIZE_ADDRESSING"></a> - <span class="bold"><strong>/D HAVE_MIXED_SIZE_ADDRESSING</strong></span> + <span class="bold"><strong>/D + HAVE_MIXED_SIZE_ADDRESSING</strong></span> </p> - <p> - Allows for the sharing of the BDB database environment - between 32-bit and 64-bit applications. Note that if you - use this macro to rebuild your Berkeley DB library, then - you need to also rebuild both your 32-bit and 64-bit - applications using - <span class="bold"><strong>/D HAVE_MIXED_SIZE_ADDRESSING</strong></span>. + <p> + Allows for the sharing of the BDB database + environment between 32-bit and 64-bit applications. + Note that if you use this macro to rebuild your + Berkeley DB library, then you need to also rebuild + both your 32-bit and 64-bit applications using + <span class="bold"><strong>/D + HAVE_MIXED_SIZE_ADDRESSING</strong></span>. </p> - <p> - Note that use of this macro means that private environments - are disabled for the library. + <p> + Note that use of this macro means that private + environments are disabled for the library. </p> </li> <li> <p><a id="HAVE_STRIPPED_MESSAGES"></a> - <span class="bold"><strong>/D HAVE_STRIPPED_MESSAGES</strong></span> + <span class="bold"><strong>/D + HAVE_STRIPPED_MESSAGES</strong></span> </p> <p> - Causes all error messages to be stripped of their textual - information. This option should not be used when enabling - localization support. Use of this property can reduce your - library footprint by up to 42KB (for DLLs) or 98KB - (for a .lib). + Causes all error messages to be stripped of their + textual information. This option should not be used + when enabling localization support. Use of this + property can reduce your library footprint by up to + 42KB (for DLLs) or 98KB (for a .lib). </p> - <p> - Note that this option is automatically enabled if you build - using the <code class="filename">db_small</code> project name. For - more information on building a small library, see - <a class="xref" href="build_win_small.html" title="Building a small memory footprint library">Building a small memory footprint library</a>. + <p> + Note that this option is automatically enabled if + you build using the <code class="filename">db_small</code> + project name. For more information on building a small + library, see <a class="xref" href="build_win_small.html" title="Building a small memory footprint library">Building a small memory + footprint library</a>. </p> <p> - If you use this build option, you can get an idea of - what text should be issued for a given error message by using - the - <a href="../articles/mssgtxt/index.html" class="olink">Message Reference for Stripped Libraries</a> guide. - </p> + If you use this build option, you can get an idea + of what text should be issued for a given error + message by using the <a href="../articles/mssgtxt/index.html" class="olink">Berkeley DB Message Reference Guide</a>. + </p> + </li> + <li> + <p><a id="DIAGNOSTIC"></a> + <span class="bold"><strong>/D DIAGNOSTIC</strong></span> + </p> + <p> + Included automatically in the Debug build. Allows a + number of additional checks to be performed when BDB + is running, and also causes some failures to trigger + process abort rather than returning errors to the + application. Applications built using this option + should not share database environments with + applications built without this option. The + <code class="literal">DIAGNOSTIC</code> option should not be + specified when configuring to build production + binaries because it degrades performance. + </p> + </li> + <li> + <p><a id="UMRW"></a> + <span class="bold"><strong>/D UMRW</strong></span> + </p> + <p> + Rational Software's Purify product and other + software analysis run-time tools complain about + uninitialized reads/writes of structure fields whose + only purpose is padding, as well as when heap memory + that was never initialized is written to disk. Specify + this option during configuration to mask these errors. + The <code class="literal">UMRW</code> option should not be + specified when configuring to build production + binaries. + </p> </li> </ul> </div> @@ -119,7 +165,8 @@ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Building a small memory footprint library</td> + <td width="40%" align="right" valign="top"> Building a small memory + footprint library</td> </tr> </table> </div> diff --git a/docs/installation/win_build64.html b/docs/installation/win_build64.html index 8a7507cb..e3db78e3 100644 --- a/docs/installation/win_build64.html +++ b/docs/installation/win_build64.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="build_win.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="win_build_cygwin.html">Next</a></td> </tr> </table> @@ -42,18 +40,22 @@ <dl> <dt> <span class="sect2"> - <a href="win_build64.html#idm80112">x64 build with Visual Studio 2005 or newer</a> + <a href="win_build64.html#idp269712">x64 build with Visual Studio 2005 or newer</a> </span> </dt> </dl> </div> - <p>The following procedure can be used to build natively on a 64-bit system -or to cross-compile from a 32-bit system.</p> <p> - When building 64-bit binaries, the output directory will be one of the following - Berkeley DB subdirectories, depending upon the configuration that you - chose: -</p> + The following procedure can be used + to build natively on a 64-bit system or to cross-compile + from a 32-bit system. + </p> + <p> + When building 64-bit + binaries, the output directory will be one of the + following Berkeley DB subdirectories, depending upon the + configuration that you chose: + </p> <table class="simplelist" border="0" summary="Simple list"> <tr> <td> @@ -80,21 +82,26 @@ or to cross-compile from a 32-bit system.</p> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idm80112"></a>x64 build with Visual Studio 2005 or newer</h3> + <h3 class="title"><a id="idp269712"></a>x64 build with Visual Studio 2005 or newer</h3> </div> </div> </div> <div class="orderedlist"> <ol type="1"> + <li> + Follow the build instructions for your + version of Visual Studio, as described in <a class="xref" href="build_win.html#win_build32" title="Building Berkeley DB for 32 bit Windows">Building Berkeley DB for 32 bit Windows</a>. + </li> <li> - Follow the build instructions for your version of Visual - Studio, as described in - <a class="xref" href="build_win.html#win_build32" title="Building Berkeley DB for 32 bit Windows">Building Berkeley DB for 32 bit Windows</a>. - </li> - <li>Select <span class="emphasis"><em>x64</em></span> from the <span class="emphasis"><em>Platform -Configuration</em></span> dropdown.</li> - <li>Right click on <span class="emphasis"><em>Solution 'Berkeley_DB'</em></span> in the -Solution Explorer, and select <span class="emphasis"><em>Build Solution</em></span></li> + Select <span class="emphasis"><em>x64</em></span> from the + <span class="emphasis"><em>Platform Configuration</em></span> + dropdown. + </li> + <li> + Right click on <span class="emphasis"><em>Solution + 'Berkeley_DB'</em></span> in the Solution + Explorer, and select <span class="emphasis"><em>Build + Solution</em></span></li> </ol> </div> </div> @@ -110,9 +117,7 @@ Solution Explorer, and select <span class="emphasis"><em>Build Solution</em></sp <td width="40%" align="right"> <a accesskey="n" href="win_build_cygwin.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 5. - Building Berkeley DB for Windows - </td> + <td width="40%" align="left" valign="top">Chapter 5. Building Berkeley DB for Windows </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> diff --git a/docs/installation/win_build_cxx.html b/docs/installation/win_build_cxx.html index d3e54af8..f42d5408 100644 --- a/docs/installation/win_build_cxx.html +++ b/docs/installation/win_build_cxx.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="win_build_cygwin.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="win_build_stl.html">Next</a></td> </tr> </table> @@ -38,7 +36,9 @@ </div> </div> </div> - <p>C++ support is built automatically on Windows.</p> + <p> + C++ support is built automatically on Windows. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/win_build_cygwin.html b/docs/installation/win_build_cygwin.html index 584d9e76..32a7d186 100644 --- a/docs/installation/win_build_cygwin.html +++ b/docs/installation/win_build_cygwin.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="win_build64.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="win_build_cxx.html">Next</a></td> </tr> </table> @@ -38,8 +36,10 @@ </div> </div> </div> - <p>To build Berkeley DB with Cygwin, follow the instructions in -<a class="xref" href="build_unix.html#build_unix_intro" title="Building for UNIX/POSIX">Building for UNIX/POSIX</a>.</p> + <p> + To build Berkeley DB with Cygwin, follow the + instructions in <a class="xref" href="build_unix.html#build_unix_intro" title="Building for UNIX/POSIX">Building for UNIX/POSIX</a>. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/win_build_dist_dll.html b/docs/installation/win_build_dist_dll.html index f4ff595d..9226ce35 100644 --- a/docs/installation/win_build_dist_dll.html +++ b/docs/installation/win_build_dist_dll.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="build_win_tcl.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="win_additional_options.html">Next</a></td> </tr> </table> @@ -39,11 +37,12 @@ </div> </div> <p> - When distributing applications linked against the DLL (not static) - version of the library, the DLL files you need will be found in one of the following - Berkeley DB subdirectories, depending upon the configuration that - you chose: - </p> + When distributing applications linked against the DLL + (not static) version of the library, the DLL files you + need will be found in one of the following Berkeley DB + subdirectories, depending upon the configuration that you + chose: + </p> <table class="simplelist" border="0" summary="Simple list"> <tr> <td> @@ -86,14 +85,17 @@ </td> </tr> </table> - <p> - You may also need to redistribute DLL files needed for the compiler's - runtime. Generally, these runtime DLL - files can be installed in the same directory that will contain your - installed Berkeley DB DLLs. This directory may need to be added to - your System PATH environment variable. Check your compiler's license - and documentation for specifics on redistributing runtime DLLs. -</p> + <p> + You may also need to redistribute DLL + files needed for the compiler's runtime. + + Generally, these runtime DLL files can be installed in the same directory + that will contain your installed Berkeley DB DLLs. This + directory may need to be added to your System PATH + environment variable. Check your compiler's license and + documentation for specifics on redistributing runtime + DLLs. + </p> </div> <div class="navfooter"> <hr /> diff --git a/docs/installation/win_build_stl.html b/docs/installation/win_build_stl.html index 79e073d5..c9f95b2b 100644 --- a/docs/installation/win_build_stl.html +++ b/docs/installation/win_build_stl.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="win_build_cxx.html">Prev</a> </td> - <th width="60%" align="center">Chapter 5. - Building Berkeley DB for Windows - </th> + <th width="60%" align="center">Chapter 5. Building Berkeley DB for Windows </th> <td width="20%" align="right"> <a accesskey="n" href="build_win_java.html">Next</a></td> </tr> </table> @@ -38,21 +36,25 @@ </div> </div> </div> + <p> + In the project list of the <code class="filename">Berkeley_DB.sln + </code> solution, build the "db_stl" project and + "db_stl_static" project to build STL API as a dynamic or + static library respectively. And in your application, you + should link this library file as well as the Berkeley DB + library file to your application. The STL API library file + is by default always put at the same location as the + Berkeley DB library file. + </p> <p> - -In the project list of the <code class="filename">Berkeley_DB.sln </code> -solution, build the "db_stl" project and "db_stl_static" project to build STL API -as a dynamic or static library respectively. And in your application, you should link this -library file as well as the Berkeley DB library file to your application. The STL API library file is by default always put at the -same location as the Berkeley DB library file. -</p> - <p> -And you need to include the STL API header files in your application code. -If you are using the Berkeley DB source tree, the header files are in <Berkeley DB Source Root >/stl directory; -If you -are using the pre-built installed version, these header files are in < Berkeley DB Installed Directory>/include, as well as the -db.h and db_cxx.h header files. -</p> + And you need to include the STL API header files in + your application code. If you are using the Berkeley DB + source tree, the header files are in <Berkeley DB + Source Root >/stl directory; If you are using the + pre-built installed version, these header files are in + < Berkeley DB Installed Directory>/include, as well + as the db.h and db_cxx.h header files. + </p> </div> <div class="navfooter"> <hr /> |