| 1 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> |
| 2 |
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| 3 |
<html xmlns="http://www.w3.org/1999/xhtml"> |
| 4 |
<head> |
| 5 |
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> |
| 6 |
<title>db_env_set_XXX</title> |
| 7 |
<link rel="stylesheet" href="gettingStarted.css" type="text/css" /> |
| 8 |
<meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> |
| 9 |
<link rel="start" href="index.html" title="Berkeley DB Upgrade Guide" /> |
| 10 |
<link rel="up" href="upgrade_4_0_toc.html" title="Chapter 10. Upgrading Berkeley DB 3.3 applications to Berkeley DB 4.0" /> |
| 11 |
<link rel="prev" href="upgrade_4_0_txn.html" title="txn_XXX" /> |
| 12 |
<link rel="next" href="upgrade_4_0_rpc.html" title="DB_ENV->set_server" /> |
| 13 |
</head> |
| 14 |
<body> |
| 15 |
<div xmlns="" class="navheader"> |
| 16 |
<div class="libver"> |
| 17 |
<p>Library Version 11.2.5.3</p> |
| 18 |
</div> |
| 19 |
<table width="100%" summary="Navigation header"> |
| 20 |
<tr> |
| 21 |
<th colspan="3" align="center">db_env_set_XXX</th> |
| 22 |
</tr> |
| 23 |
<tr> |
| 24 |
<td width="20%" align="left"><a accesskey="p" href="upgrade_4_0_txn.html">Prev</a> </td> |
| 25 |
<th width="60%" align="center">Chapter 10. Upgrading Berkeley DB 3.3 applications to Berkeley DB 4.0</th> |
| 26 |
<td width="20%" align="right"> <a accesskey="n" href="upgrade_4_0_rpc.html">Next</a></td> |
| 27 |
</tr> |
| 28 |
</table> |
| 29 |
<hr /> |
| 30 |
</div> |
| 31 |
<div class="sect1" lang="en" xml:lang="en"> |
| 32 |
<div class="titlepage"> |
| 33 |
<div> |
| 34 |
<div> |
| 35 |
<h2 class="title" style="clear: both"><a id="upgrade_4_0_env"></a>db_env_set_XXX</h2> |
| 36 |
</div> |
| 37 |
</div> |
| 38 |
</div> |
| 39 |
<p>The db_env_set_region_init function was removed in the 4.0 release and |
| 40 |
replaced with the <code class="literal">DB_REGION_INIT</code> flag to the |
| 41 |
<a href="../api_reference/C/envset_flags.html" class="olink">DB_ENV->set_flags()</a> method. This is an interface change: historically, |
| 42 |
the db_env_set_region_init function operated on the entire Berkeley DB |
| 43 |
library, not a single environment. The new method only operates on |
| 44 |
a single <a href="../api_reference/C/env.html" class="olink">DB_ENV class</a> handle (and any handles created in the scope of |
| 45 |
that handle). Applications calling the db_env_set_region_init function |
| 46 |
should update their calls: calls to the historic routine with an |
| 47 |
argument of 1 (0) are equivalent to calling <a href="../api_reference/C/envset_flags.html" class="olink">DB_ENV->set_flags()</a> with |
| 48 |
the <code class="literal">DB_REGION_INIT</code> flag and an argument of 1 (0).</p> |
| 49 |
<p>The db_env_set_tas_spins function was removed in the 4.0 release and |
| 50 |
replaced with the DB_ENV->set_tas_spins method. This is an |
| 51 |
interface change: historically, the db_env_set_tas_spins function |
| 52 |
operated on the entire Berkeley DB library, not a single environment. The new |
| 53 |
method only operates on a single <a href="../api_reference/C/env.html" class="olink">DB_ENV class</a> handle (and any handles |
| 54 |
created in the scope of that handle). Applications calling the |
| 55 |
db_env_set_tas_spins function should update their calls: calls to the |
| 56 |
historic routine are equivalent to calling DB_ENV->set_tas_spins |
| 57 |
with the same argument. In addition, for consistent behavior, all |
| 58 |
<a href="../api_reference/C/env.html" class="olink">DB_ENV class</a> handles opened by the application should make the same |
| 59 |
configuration call, or the value will need to be entered into the |
| 60 |
environment's <a href="../programmer_reference/env_db_config.html" class="olink">DB_CONFIG</a> file.</p> |
| 61 |
<p>Also, three of the standard Berkeley DB debugging interfaces changed in the |
| 62 |
4.0 release. It is quite unlikely that Berkeley DB applications use these |
| 63 |
interfaces.</p> |
| 64 |
<p>The DB_ENV->set_mutexlocks method was removed in the 4.0 release |
| 65 |
and replaced with the <code class="literal">DB_NO_LOCKING</code> flag to the |
| 66 |
<a href="../api_reference/C/envset_flags.html" class="olink">DB_ENV->set_flags()</a> method. Applications calling the |
| 67 |
DB_ENV->set_mutexlocks method should update their calls: calls |
| 68 |
to the historic routine with an argument of 1 (0) are equivalent to |
| 69 |
calling <code class="literal">DB_NO_LOCKING</code> flag and |
| 70 |
an argument of 1 (0).</p> |
| 71 |
<p>The db_env_set_pageyield function was removed in the 4.0 release and |
| 72 |
replaced with the <code class="literal">DB_YIELDCPU</code> flag to the |
| 73 |
<a href="../api_reference/C/envset_flags.html" class="olink">DB_ENV->set_flags()</a> method. This is an interface change: historically, |
| 74 |
the db_env_set_pageyield function operated on the entire Berkeley DB library, |
| 75 |
not a single environment. The new method only operates on a single |
| 76 |
<a href="../api_reference/C/env.html" class="olink">DB_ENV class</a> handle (and any handles created in the scope of that |
| 77 |
handle). Applications calling the db_env_set_pageyield function should |
| 78 |
update their calls: calls to the historic routine with an argument of 1 |
| 79 |
(0) are equivalent to calling <a href="../api_reference/C/envset_flags.html" class="olink">DB_ENV->set_flags()</a> with the |
| 80 |
<code class="literal">DB_YIELDCPU</code> flag and an argument of 1 (0). In addition, all |
| 81 |
<a href="../api_reference/C/env.html" class="olink">DB_ENV class</a> handles opened by the application will need to make the |
| 82 |
same call, or the <code class="literal">DB_YIELDCPU</code> flag will need to be entered into |
| 83 |
the environment's <a href="../programmer_reference/env_db_config.html" class="olink">DB_CONFIG</a> file.</p> |
| 84 |
<p>The db_env_set_panicstate function was removed in the 4.0 release, |
| 85 |
replaced with the <code class="literal">DB_PANIC_ENVIRONMENT</code> |
| 86 |
flags to the <a href="../api_reference/C/envset_flags.html" class="olink">DB_ENV->set_flags()</a> method. (The |
| 87 |
<code class="literal">DB_PANIC_ENVIRONMENT</code> flag will cause an environment to panic, |
| 88 |
affecting all threads of control using that environment. The |
| 89 |
<a href="../api_reference/C/envset_flags.html" class="olink">DB_ENV->set_flags()</a> handle to |
| 90 |
ignore the current panic state of the environment.) This is an |
| 91 |
interface change: historically the db_env_set_panicstate function |
| 92 |
operated on the entire Berkeley DB library, not a single environment. |
| 93 |
Applications calling the db_env_set_panicstate function should update |
| 94 |
their calls, replacing the historic call with a call to |
| 95 |
<a href="../api_reference/C/envset_flags.html" class="olink">DB_ENV->set_flags()</a> and the appropriate flag, depending on their |
| 96 |
usage of the historic interface.</p> |
| 97 |
</div> |
| 98 |
<div class="navfooter"> |
| 99 |
<hr /> |
| 100 |
<table width="100%" summary="Navigation footer"> |
| 101 |
<tr> |
| 102 |
<td width="40%" align="left"><a accesskey="p" href="upgrade_4_0_txn.html">Prev</a> </td> |
| 103 |
<td width="20%" align="center"> |
| 104 |
<a accesskey="u" href="upgrade_4_0_toc.html">Up</a> |
| 105 |
</td> |
| 106 |
<td width="40%" align="right"> <a accesskey="n" href="upgrade_4_0_rpc.html">Next</a></td> |
| 107 |
</tr> |
| 108 |
<tr> |
| 109 |
<td width="40%" align="left" valign="top">txn_XXX </td> |
| 110 |
<td width="20%" align="center"> |
| 111 |
<a accesskey="h" href="index.html">Home</a> |
| 112 |
</td> |
| 113 |
<td width="40%" align="right" valign="top"> DB_ENV->set_server</td> |
| 114 |
</tr> |
| 115 |
</table> |
| 116 |
</div> |
| 117 |
</body> |
| 118 |
</html> |