<!--$Id: lock.html,v 1.1.1.1 2003/02/15 04:56:04 zarzycki Exp $--> <!--Copyright 1997-2002 by Sleepycat Software, Inc.--> <!--All rights reserved.--> <!--See the file LICENSE for redistribution information.--> <html> <head> <title>Berkeley DB Reference Guide: Release 4.0: lock_XXX</title> <meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> <meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,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><h3><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></h3></td> <td align=right><a href="../../ref/upgrade.4.0/deadlock.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/upgrade.4.0/log.html"><img src="../../images/next.gif" alt="Next"></a> </td></tr></table> <p> <h1 align=center>Release 4.0: lock_XXX</h1> <p>The C API for the Berkeley DB Locking subsystem was reworked in the 4.0 release as follows: <p><table border=1 align=center> <tr><th>Historic functional interface</th><th>Berkeley DB 4.X method</th></tr> <tr><td>lock_detect</td><td><a href="../../api_c/lock_detect.html">DB_ENV->lock_detect</a></td></tr> <tr><td>lock_get</td><td><a href="../../api_c/lock_get.html">DB_ENV->lock_get</a></td></tr> <tr><td>lock_id</td><td><a href="../../api_c/lock_id.html">DB_ENV->lock_id</a></td></tr> <tr><td>lock_put</td><td><a href="../../api_c/lock_put.html">DB_ENV->lock_put</a></td></tr> <tr><td>lock_stat</td><td><a href="../../api_c/lock_stat.html">DB_ENV->lock_stat</a></td></tr> <tr><td>lock_vec</td><td><a href="../../api_c/lock_vec.html">DB_ENV->lock_vec</a></td></tr> </table> <p>Applications calling any of these functions should update their calls to use the enclosing <a href="../../api_c/env_class.html">DB_ENV</a> handle's method (easily done as the first argument to the existing call is the correct handle to use). <p>In addition, the <a href="../../api_c/lock_stat.html">DB_ENV->lock_stat</a> call has been changed in the 4.0 release to take a flags argument. To leave their historic behavior unchanged, applications should add a final argument of 0 to any calls made to <a href="../../api_c/lock_stat.html">DB_ENV->lock_stat</a>. <p>The C++ and Java APIs for the DbLock::put (DbLock.put) method was reworked in the 4.0 release to make the lock put interface a method of the <a href="../../api_c/env_class.html">DB_ENV</a> handle rather than the DbLock handle. Applications calling the DbLock::put or DbLock.put method should update their calls to use the enclosing <a href="../../api_c/env_class.html">DB_ENV</a> handle's method (easily done as the first argument to the existing call is the correct handle to use). <table width="100%"><tr><td><br></td><td align=right><a href="../../ref/upgrade.4.0/deadlock.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/upgrade.4.0/log.html"><img src="../../images/next.gif" alt="Next"></a> </td></tr></table> <p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font> </body> </html>