CHips L Pro sangad

Current Path : /proc/2/cwd/usr/share/doc/db4-devel-4.7.25/ref/upgrade.3.3/

Current File : //proc/2/cwd/usr/share/doc/db4-devel-4.7.25/ref/upgrade.3.3/conflict.html

<!--$Id: conflict.so,v 1.6 2003/10/18 19:16:18 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 3.3: DB_LOCK_CONFLICT</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.3.3/alloc.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.3/memp_fget.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p align=center><b>Release 3.3: DB_LOCK_CONFLICT</b></p>
<p>The DB_LOCK_CONFLICT flag has been removed from the lock_detect function.
Applications specifying the DB_LOCK_CONFLICT flag should simply replace
it with a flags argument of 0.</p>
<table width="100%"><tr><td><br></td><td align=right><a href="../upgrade.3.3/alloc.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.3/memp_fget.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>

CHips L MINI SHELL

CHips L pro