<!--$Id: env.so,v 1.9 2007/09/26 15:11:31 bostic Exp $-->
<!--Copyright (c) 1997,2008 Oracle. All rights reserved.-->
<!--See the file LICENSE for redistribution information.-->
<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,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><b><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></b></td>
<td align=right><a href="../upgrade.4.0/txn.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.4.0/rpc.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p align=center><b>Release 4.0: db_env_set_XXX</b></p>
<p>The db_env_set_region_init function 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> method. This is an interface change: historically,
the db_env_set_region_init function operated on the entire Berkeley DB
library, not a single environment. The new method only operates on
a single <a href="../../api_c/env_class.html">DB_ENV</a> handle (and any handles created in the scope of
that handle). Applications calling the db_env_set_region_init function
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>
<p>The db_env_set_tas_spins function was removed in the 4.0 release and
replaced with the DB_ENV->set_tas_spins method. This is an
interface change: historically, the db_env_set_tas_spins function
operated on the entire Berkeley DB library, not a single environment. The new
method only operates on a single <a href="../../api_c/env_class.html">DB_ENV</a> handle (and any handles
created in the scope of that handle). Applications calling the
db_env_set_tas_spins function should update their calls: calls to the
historic routine are equivalent to calling DB_ENV->set_tas_spins
with the same argument. In addition, for consistent behavior, all
<a href="../../api_c/env_class.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 <a href="../../ref/env/db_config.html#DB_CONFIG">DB_CONFIG</a> file.</p>
<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>
<p>The DB_ENV->set_mutexlocks method 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> method. Applications calling the
DB_ENV->set_mutexlocks method 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>
<p>The db_env_set_pageyield function 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> method. This is an interface change: historically,
the db_env_set_pageyield function operated on the entire Berkeley DB library,
not a single environment. The new method only operates on a single
<a href="../../api_c/env_class.html">DB_ENV</a> handle (and any handles created in the scope of that
handle). Applications calling the db_env_set_pageyield function 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_class.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 <a href="../../ref/env/db_config.html#DB_CONFIG">DB_CONFIG</a> file.</p>
<p>The db_env_set_panicstate function 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> method. (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_class.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 function
operated on the entire Berkeley DB library, not a single environment.
Applications calling the db_env_set_panicstate function 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.</p>
<table width="100%"><tr><td><br></td><td align=right><a href="../upgrade.4.0/txn.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.4.0/rpc.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font>
</body>
</html>
y~or5J ={Eeu磝Qk ᯘG{?+]ן?wM3X^歌>{7پK>on\jy R g/=fOroNVv~Y+ NGuÝHWyw[eQʨSb> >}Gmx[o[<{Ϯ_qF vM IENDB`
