1<!--$Id: set_flags.so,v 1.3 2003/10/18 19:16:16 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 3.2: DB_ENV->set_flags</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.3.2/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.3.2/callback.html"><img src="../../images/next.gif" alt="Next"></a> 14</td></tr></table> 15<p align=center><b>Release 3.2: DB_ENV->set_flags</b></p> 16<p>A new method has been added to the Berkeley DB environment handle, 17<a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a>. This method currently takes three flags: 18<a href="../../api_c/env_set_flags.html#DB_CDB_ALLDB">DB_CDB_ALLDB</a>, <a href="../../api_c/env_set_flags.html#DB_NOMMAP">DB_NOMMAP</a> and <a href="../../api_c/env_set_flags.html#DB_TXN_NOSYNC">DB_TXN_NOSYNC</a>. The 19first of these flags, <a href="../../api_c/env_set_flags.html#DB_CDB_ALLDB">DB_CDB_ALLDB</a>, provides new functionality, 20allowing Berkeley DB Concurrent Data Store applications to do locking across multiple databases.</p> 21<p>The other two flags, <a href="../../api_c/env_set_flags.html#DB_NOMMAP">DB_NOMMAP</a> and <a href="../../api_c/env_set_flags.html#DB_TXN_NOSYNC">DB_TXN_NOSYNC</a>, were 22specified to the <a href="../../api_c/env_open.html">DB_ENV->open</a> method in previous releases. In 23the 3.2 release, they have been moved to the <a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> method 24because this allows the database environment's value to be toggled 25during the life of the application as well as because it is a more 26appropriate place for them. Applications specifying either the 27<a href="../../api_c/env_set_flags.html#DB_NOMMAP">DB_NOMMAP</a> or <a href="../../api_c/env_set_flags.html#DB_TXN_NOSYNC">DB_TXN_NOSYNC</a> flags to the 28<a href="../../api_c/env_open.html">DB_ENV->open</a> method should replace those flags with calls to the 29<a href="../../api_c/env_set_flags.html">DB_ENV->set_flags</a> method.</p> 30<table width="100%"><tr><td><br></td><td align=right><a href="../upgrade.3.2/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.3.2/callback.html"><img src="../../images/next.gif" alt="Next"></a> 31</td></tr></table> 32<p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font> 33</body> 34</html> 35
