1<!--$Id: env.so,v 1.9 2007/09/26 15:11:31 bostic Exp $--> 2<!--Copyright (c) 1997,2008 Oracle. All rights reserved.--> 3<!--See the file LICENSE for redistribution information.--> 4<html> 5<head> 6<title>Berkeley DB Reference Guide: Release 4.0: db_env_set_XXX</title> 7<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> 8<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++"> 9</head> 10<body bgcolor=white> 11<table width="100%"><tr valign=top> 12<td><b><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></b></td> 13<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> 14</td></tr></table> 15<p align=center><b>Release 4.0: db_env_set_XXX</b></p> 16<p>The db_env_set_region_init function was removed in the 4.0 release and 17replaced with the <a href="/api_c/env_set_flags.html#DB_REGION_INIT">DB_REGION_INIT</a> flag to the 18<a href="/api_c/env_set_flags.html">DB_ENV->set_flags</a> method. This is an interface change: historically, 19the db_env_set_region_init function operated on the entire Berkeley DB 20library, not a single environment. The new method only operates on 21a single <a href="/api_c/env_class.html">DB_ENV</a> handle (and any handles created in the scope of 22that handle). Applications calling the db_env_set_region_init function 23should update their calls: calls to the historic routine with an 24argument of 1 (0) are equivalent to calling <a href="/api_c/env_set_flags.html">DB_ENV->set_flags</a> with 25the <a href="/api_c/env_set_flags.html#DB_REGION_INIT">DB_REGION_INIT</a> flag and an argument of 1 (0).</p> 26<p>The db_env_set_tas_spins function was removed in the 4.0 release and 27replaced with the DB_ENV->set_tas_spins method. This is an 28interface change: historically, the db_env_set_tas_spins function 29operated on the entire Berkeley DB library, not a single environment. The new 30method only operates on a single <a href="/api_c/env_class.html">DB_ENV</a> handle (and any handles 31created in the scope of that handle). Applications calling the 32db_env_set_tas_spins function should update their calls: calls to the 33historic routine are equivalent to calling DB_ENV->set_tas_spins 34with the same argument. In addition, for consistent behavior, all 35<a href="/api_c/env_class.html">DB_ENV</a> handles opened by the application should make the same 36configuration call, or the value will need to be entered into the 37environment's <a href="/ref/env/db_config.html#DB_CONFIG">DB_CONFIG</a> file.</p> 38<p>Also, three of the standard Berkeley DB debugging interfaces changed in the 394.0 release. It is quite unlikely that Berkeley DB applications use these 40interfaces.</p> 41<p>The DB_ENV->set_mutexlocks method was removed in the 4.0 release 42and replaced with the <a href="/api_c/env_set_flags.html#DB_NOLOCKING">DB_NOLOCKING</a> flag to the 43<a href="/api_c/env_set_flags.html">DB_ENV->set_flags</a> method. Applications calling the 44DB_ENV->set_mutexlocks method should update their calls: calls 45to the historic routine with an argument of 1 (0) are equivalent to 46calling <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 47an argument of 1 (0).</p> 48<p>The db_env_set_pageyield function was removed in the 4.0 release and 49replaced with the <a href="/api_c/env_set_flags.html#DB_YIELDCPU">DB_YIELDCPU</a> flag to the 50<a href="/api_c/env_set_flags.html">DB_ENV->set_flags</a> method. This is an interface change: historically, 51the db_env_set_pageyield function operated on the entire Berkeley DB library, 52not a single environment. The new method only operates on a single 53<a href="/api_c/env_class.html">DB_ENV</a> handle (and any handles created in the scope of that 54handle). Applications calling the db_env_set_pageyield function should 55update their calls: calls to the historic routine with an argument of 1 56(0) are equivalent to calling <a href="/api_c/env_set_flags.html">DB_ENV->set_flags</a> with the 57<a href="/api_c/env_set_flags.html#DB_YIELDCPU">DB_YIELDCPU</a> flag and an argument of 1 (0). In addition, all 58<a href="/api_c/env_class.html">DB_ENV</a> handles opened by the application will need to make the 59same call, or the <a href="/api_c/env_set_flags.html#DB_YIELDCPU">DB_YIELDCPU</a> flag will need to be entered into 60the environment's <a href="/ref/env/db_config.html#DB_CONFIG">DB_CONFIG</a> file.</p> 61<p>The db_env_set_panicstate function was removed in the 4.0 release, 62replaced 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> 63flags to the <a href="/api_c/env_set_flags.html">DB_ENV->set_flags</a> method. (The 64<a href="/api_c/env_set_flags.html#DB_PANIC_ENVIRONMENT">DB_PANIC_ENVIRONMENT</a> flag will cause an environment to panic, 65affecting all threads of control using that environment. The 66<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 67ignore the current panic state of the environment.) This is an 68interface change: historically the db_env_set_panicstate function 69operated on the entire Berkeley DB library, not a single environment. 70Applications calling the db_env_set_panicstate function should update 71their calls, replacing the historic call with a call to 72<a href="/api_c/env_set_flags.html">DB_ENV->set_flags</a> and the appropriate flag, depending on their 73usage of the historic interface.</p> 74<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> 75</td></tr></table> 76<p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font> 77</body> 78</html> 79
