diff options
Diffstat (limited to 'db/docs/ref/upgrade.4.0/env.html')
| -rw-r--r-- | db/docs/ref/upgrade.4.0/env.html | 81 |
1 files changed, 81 insertions, 0 deletions
diff --git a/db/docs/ref/upgrade.4.0/env.html b/db/docs/ref/upgrade.4.0/env.html new file mode 100644 index 000000000..d7c6bbaa6 --- /dev/null +++ b/db/docs/ref/upgrade.4.0/env.html @@ -0,0 +1,81 @@ +<!--Id: env.so,v 1.5 2001/08/07 01:42:35 bostic Exp --> +<!--Copyright 1997-2001 by Sleepycat Software, Inc.--> +<!--All rights reserved.--> +<html> +<head> +<title>Berkeley DB Reference Guide: Release 4.0: db_env_set_XXX</title> +<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> +<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++"> +</head> +<body bgcolor=white> +<table width="100%"><tr valign=top> +<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></h3></td> +<td align=right><a href="../../ref/upgrade.4.0/txn.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/upgrade.4.0/rpc.html"><img src="../../images/next.gif" alt="Next"></a> +</td></tr></table> +<p> +<h1 align=center>Release 4.0: db_env_set_XXX</h1> +<p>The db_env_set_region_init interface was removed in the 4.0 release and +replaced with the <a href="../../api_c/env_set_flags.html#DB_REGION_INIT">DB_REGION_INIT</a> flag to the +<a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> interface. This is an interface change: +historically, the db_env_set_region_init interface operated on the +entire Berkeley DB library, not a single environment. The new interface only +operates on a single <a href="../../api_c/env_create.html">DB_ENV</a> handle (and any handles created in +the scope of that handle). Applications calling the +db_env_set_region_init interface should update their calls: calls to +the historic routine with an argument of 1 (0) are equivalent to calling +<a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> with the <a href="../../api_c/env_set_flags.html#DB_REGION_INIT">DB_REGION_INIT</a> flag and an +argument of 1 (0). +<p>The db_env_set_tas_spins interface was removed in the 4.0 release and +replaced with the <a href="../../api_c/env_set_tas_spins.html">DB_ENV->set_tas_spins</a> function. This is an interface +change: historically, the db_env_set_tas_spins interface operated on +the entire Berkeley DB library, not a single environment. The new interface +only operates on a single <a href="../../api_c/env_create.html">DB_ENV</a> handle (and any handles created +in the scope of that handle). Applications calling the +db_env_set_tas_spins interface should update their calls: calls to the +historic routine are equivalent to calling <a href="../../api_c/env_set_tas_spins.html">DB_ENV->set_tas_spins</a> function +with the same argument. In addition, for consistent behavior, all +<a href="../../api_c/env_create.html">DB_ENV</a> handles opened by the application should make the same +configuration call, or the value will need to be entered into the +environment's <b>DB_CONFIG</b> file. +<p>Also, three of the standard Berkeley DB debugging interfaces changed in the +4.0 release. It is quite unlikely that Berkeley DB applications use these +interfaces. +<p>The DB_ENV->set_mutexlocks interface was removed in the 4.0 release +and replaced with the <a href="../../api_c/env_set_flags.html#DB_NOLOCKING">DB_NOLOCKING</a> flag to the +<a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> interface. Applications calling the +DB_ENV->set_mutexlocks interface should update their calls: calls +to the historic routine with an argument of 1 (0) are equivalent to +calling <a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> with the <a href="../../api_c/env_set_flags.html#DB_NOLOCKING">DB_NOLOCKING</a> flag and +an argument of 1 (0). +<p>The db_env_set_pageyield interface was removed in the 4.0 release and +replaced with the <a href="../../api_c/env_set_flags.html#DB_YIELDCPU">DB_YIELDCPU</a> flag to the +<a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> interface. This is an interface change: +historically, the db_env_set_pageyield interface operated on the entire +Berkeley DB library, not a single environment. The new interface only +operates on a single <a href="../../api_c/env_create.html">DB_ENV</a> handle (and any handles created in +the scope of that handle). Applications calling the +db_env_set_pageyield interface should update their calls: calls to the +historic routine with an argument of 1 (0) are equivalent to calling +<a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> with the <a href="../../api_c/env_set_flags.html#DB_YIELDCPU">DB_YIELDCPU</a> flag and an +argument of 1 (0). In addition, all <a href="../../api_c/env_create.html">DB_ENV</a> handles opened by +the application will need to make the same call, or the +<a href="../../api_c/env_set_flags.html#DB_YIELDCPU">DB_YIELDCPU</a> flag will need to be entered into the environment's +<b>DB_CONFIG</b> file. +<p>The db_env_set_panicstate interface was removed in the 4.0 release, +replaced with the <a href="../../api_c/env_set_flags.html#DB_PANIC_ENVIRONMENT">DB_PANIC_ENVIRONMENT</a> and <a href="../../api_c/env_set_flags.html#DB_NOPANIC">DB_NOPANIC</a> +flags to the <a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> interface. (The +<a href="../../api_c/env_set_flags.html#DB_PANIC_ENVIRONMENT">DB_PANIC_ENVIRONMENT</a> flag will cause an environment to panic, +affecting all threads of control using that environment. The +<a href="../../api_c/env_set_flags.html#DB_NOPANIC">DB_NOPANIC</a> flag will cause a single <a href="../../api_c/env_create.html">DB_ENV</a> handle to +ignore the current panic state of the environment.) This is an +interface change: historically the db_env_set_panicstate interface +operated on the entire Berkeley DB library, not a single environment. +Applications calling the db_env_set_panicstate interface should update +their calls, replacing the historic call with a call to +<a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> and the appropriate flag, depending on their +usage of the historic interface. +<table width="100%"><tr><td><br></td><td align=right><a href="../../ref/upgrade.4.0/txn.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/upgrade.4.0/rpc.html"><img src="../../images/next.gif" alt="Next"></a> +</td></tr></table> +<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font> +</body> +</html> |