2
<!--Copyright 1997-2002 by Sleepycat Software, Inc.-->
3
<!--All rights reserved.-->
4
<!--See the file LICENSE for redistribution information.-->
7
<title>Berkeley DB: DB_ENV->lock_get</title>
8
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
9
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
12
<a name="2"><!--meow--></a>
13
<table width="100%"><tr valign=top>
15
<h1>DB_ENV->lock_get</h1>
18
<a href="../api_c/c_index.html"><img src="../images/api.gif" alt="API"></a><a href="../reftoc.html"><img src="../images/ref.gif" alt="Ref"></a>
26
DB_ENV->lock_get(DB_ENV *env, u_int32_t locker,
27
u_int32_t flags, const DBT *obj,
28
const db_lockmode_t lock_mode, DB_LOCK *lock);
31
<p>The DB_ENV->lock_get method acquires a lock from the lock table, returning
32
information about it in
33
the <b>lock</b> argument.
34
<p>The <b>locker</b> argument specified to DB_ENV->lock_get is an unsigned
35
32-bit integer quantity. It represents the entity requesting or releasing
37
<p>The <b>flags</b> value must be set to 0 or
40
<p><dt><a name="DB_LOCK_NOWAIT">DB_LOCK_NOWAIT</a><dd>If a lock cannot be granted because the requested lock conflicts with an
42
return DB_LOCK_NOTGRANTED immediately instead of waiting
43
for the lock to become available.
45
<p>The <b>obj</b> argument is an untyped byte string that specifies the
46
object to be locked or released. Applications using the locking
47
subsystem directly while also doing locking via the Berkeley DB access methods
48
must take care not to inadvertently lock objects that happen to be equal
49
to the unique file IDs used to lock files. See
50
<a href="../ref/lock/am_conv.html">Access method locking conventions</a>
52
<p>The <b>mode</b> argument is used as an index into the environment's
53
lock conflict matrix. When using the default lock conflict matrix,
54
<b>mode</b> must be set to one of the following values:
56
<dt>DB_LOCK_READ<dd>read (shared)
57
<dt>DB_LOCK_WRITE<dd>write (exclusive)
58
<dt>DB_LOCK_IWRITE<dd>intention to write (shared)
59
<dt>DB_LOCK_IREAD<dd>intention to read (shared)
60
<dt>DB_LOCK_IWR<dd>intention to read and write (shared)
62
<p>See <a href="../api_c/env_set_lk_conflicts.html">DB_ENV->set_lk_conflicts</a> and <a href="../ref/lock/stdmode.html">Standard Lock Modes</a> for more information on the lock conflict matrix.
64
Otherwise, the DB_ENV->lock_get method returns a non-zero error value on failure and 0 on success.
66
<p>The DB_ENV->lock_get method may fail and return a non-zero error for the following conditions:
68
<p><dt>DB_LOCK_DEADLOCK<dd>The operation was selected to resolve a deadlock.
71
<p><dt>EINVAL<dd>An invalid flag value or parameter was specified.
74
<p><dt>ENOMEM<dd>The maximum number of locks has been reached.
76
<p>The DB_ENV->lock_get method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions.
77
If a catastrophic error has occurred, the DB_ENV->lock_get method may fail and
78
return <a href="../ref/program/errorret.html#DB_RUNRECOVERY">DB_RUNRECOVERY</a>,
79
in which case all subsequent Berkeley DB calls will fail in the same way.
81
<a href="../api_c/env_class.html">DB_ENV</a>, <a href="../api_c/lock_class.html">DB_LOCK</a>
83
<a href="../api_c/lock_list.html">Locking Subsystem and Related Methods</a>
85
<table width="100%"><tr><td><br></td><td align=right>
86
<a href="../api_c/c_index.html"><img src="../images/api.gif" alt="API"></a><a href="../reftoc.html"><img src="../images/ref.gif" alt="Ref"></a>
88
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>