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