Edit File - File Manager

Edit File: dbc_get.html

<html>
<head>
<title>Berkeley DB: DBcursor-&gt;get</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>
DBcursor-&gt;get
</td>
<td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a>
<a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a></td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>
#include &lt;db.h&gt;

int
DBcursor-&gt;get(DBC *DBcursor,
 DBT *key, DBT *data, u_int32_t flags);

int
DBcursor-&gt;pget(DBC *DBcursor,
 DBT *key, DBT *pkey, DBT *data, u_int32_t flags);
</pre>
<hr size=1 noshade>
Description: DBcursor-&gt;get
The DBcursor-&gt;get method retrieves key/data pairs from the database. The
address and length of the key are returned in the object to which
key refers (except for the case of the DB_SET flag, in
which the key object is unchanged), and the address and length
of the data are returned in the object to which data refers.
When called on a cursor opened on a database that has been made into a
secondary index using the <a href="../../db4-devel-4.7.25/api_c/db_associate.html">DB-&gt;associate</a> method, the DBcursor-&gt;get
and DBcursor-&gt;pget methods return the key from the secondary index and the
data item from the primary database. In addition, the DBcursor-&gt;pget method
returns the key from the primary database. In databases that are not
secondary indices, the DBcursor-&gt;pget method will always fail.
Modifications to the database during a sequential scan will be reflected
in the scan; that is, records inserted behind a cursor will not be
returned while records inserted in front of a cursor will be returned.
In Queue and Recno databases, missing entries (that is, entries that
were never explicitly created or that were created and then deleted)
will be skipped during a sequential scan.
Unless otherwise specified, the DBcursor-&gt;get method
returns a non-zero error value on failure
and 0 on success.

If DBcursor-&gt;get fails for any reason, the state of the cursor will be
unchanged.
Parameters 
 data<ul compact><li>The data <a href="../../db4-devel-4.7.25/api_c/dbt_class.html">DBT</a> operated on.</ul>
 flags<ul compact><li>The flags parameter must be set to one of the following values:
 
<a name="DB_CURRENT">DB_CURRENT</a><ul compact><li>Return the key/data pair to which the cursor refers.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_KEYEMPTY">DB_KEYEMPTY</a> if DB_CURRENT is set and the cursor key/data pair was deleted.
</ul>
<a name="DB_FIRST">DB_FIRST</a><ul compact><li>The cursor is set to refer to the first key/data pair of the database,
and that pair is returned. If the first key has duplicate values, the
first data item in the set of duplicates is returned.
If the database is a Queue or Recno database, DBcursor-&gt;get using the
DB_FIRST flag will ignore any keys that exist but were never
explicitly created by the application, or were created and later
deleted.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if DB_FIRST is set and the database is empty.
</ul>
<a name="DB_GET_BOTH">DB_GET_BOTH</a><ul compact><li>The DB_GET_BOTH flag is identical to the DB_SET flag,
except that both the key and the data parameters must be matched by the
key and data item in the database.
When used with the DBcursor-&gt;pget method version of this method on a
secondary index handle, both the secondary and primary keys must be
matched by the secondary and primary key item in the database. It is
an error to use the DB_GET_BOTH flag with the DBcursor-&gt;get
version of this method and a cursor that has been opened on a secondary
index handle.</ul>
<a name="DB_GET_BOTH_RANGE">DB_GET_BOTH_RANGE</a><ul compact><li>The DB_GET_BOTH_RANGE flag is identical to the DB_GET_BOTH
flag, except that, in the case of any database supporting sorted
duplicate sets, the returned key/data pair is the smallest data item
greater than or equal to the specified data item (as determined by the
comparison function), permitting partial matches and range searches in
duplicate data sets.</ul>
<a name="DB_GET_RECNO">DB_GET_RECNO</a><ul compact><li>Return the record number associated with the cursor. The record number
will be returned in data, as described in <a href="../../db4-devel-4.7.25/api_c/dbt_class.html">DBT</a>. The
key parameter is ignored.
For DB_GET_RECNO to be specified, the underlying database must be
of type Btree, and it must have been created with the <a href="../../db4-devel-4.7.25/api_c/db_set_flags.html#DB_RECNUM">DB_RECNUM</a>
flag.
When called on a cursor opened on a database that has been made into a
secondary index, the DBcursor-&gt;get and DBcursor-&gt;pget methods return the
record number of the primary database in data. In addition, the
DBcursor-&gt;pget method returns the record number of the secondary index in
pkey. If either underlying database is not of type Btree or is
not created with the <a href="../../db4-devel-4.7.25/api_c/db_set_flags.html#DB_RECNUM">DB_RECNUM</a> flag, the out-of-band record
number of 0 is returned.</ul>
<a name="DB_JOIN_ITEM">DB_JOIN_ITEM</a><ul compact><li>Do not use the data value found in all of the cursors as a lookup key for
the primary database, but simply return it in the key parameter instead.
The data parameter is left unchanged.
For DB_JOIN_ITEM to be specified, the underlying cursor must have
been returned from the <a href="../../db4-devel-4.7.25/api_c/db_join.html">DB-&gt;join</a> method.</ul>
<a name="DB_LAST">DB_LAST</a><ul compact><li>The cursor is set to refer to the last key/data pair of the database,
and that pair is returned. If the last key has duplicate values, the
last data item in the set of duplicates is returned.
If the database is a Queue or Recno database, DBcursor-&gt;get using the
DB_LAST flag will ignore any keys that exist but were never
explicitly created by the application, or were created and later
deleted.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if DB_LAST is set and the database is empty.
</ul>
<a name="DB_NEXT">DB_NEXT</a><ul compact><li>If the cursor is not yet initialized, DB_NEXT is identical to
DB_FIRST. Otherwise, the cursor is moved to the next key/data
pair of the database, and that pair is returned. In the presence of
duplicate key values, the value of the key may not change.
If the database is a Queue or Recno database, DBcursor-&gt;get using the
DB_NEXT flag will skip any keys that exist but were never
explicitly created by the application, or those that were created and
later deleted.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if DB_NEXT is set and the cursor is already on the last record
in the database.
</ul>
<a name="DB_NEXT_DUP">DB_NEXT_DUP</a><ul compact><li>If the next key/data pair of the database is a duplicate data record for
the current key/data pair, the cursor is moved to the next key/data pair
of the database, and that pair is returned.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if DB_NEXT_DUP is set and the next key/data pair of the
database is not a duplicate data record for the current key/data pair.
</ul>
<a name="DB_NEXT_NODUP">DB_NEXT_NODUP</a><ul compact><li>If the cursor is not yet initialized, DB_NEXT_NODUP is identical
to DB_FIRST. Otherwise, the cursor is moved to the next
non-duplicate key of the database, and that key/data pair is returned.
If the database is a Queue or Recno database, DBcursor-&gt;get using the
DB_NEXT_NODUP flag will ignore any keys that exist but were
never explicitly created by the application, or those that were created
and later deleted.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if DB_NEXT_NODUP is set and no non-duplicate key/data pairs
occur after the cursor position in the database.
</ul>
<a name="DB_PREV">DB_PREV</a><ul compact><li>If the cursor is not yet initialized, DB_PREV is identical to
DB_LAST. Otherwise, the cursor is moved to the previous
key/data pair of the database, and that pair is returned. In the
presence of duplicate key values, the value of the key may not change.
If the database is a Queue or Recno database, DBcursor-&gt;get using the
DB_PREV flag will skip any keys that exist but were never
explicitly created by the application, or those that were created and
later deleted.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if DB_PREV is set and the cursor is already on the first record
in the database.
</ul>
<a name="DB_PREV_DUP">DB_PREV_DUP</a><ul compact><li>If the previous key/data pair of the database is a duplicate data record
for the current key/data pair, the cursor is moved to the previous key/data
pair of the database, and that pair is returned.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if DB_PREV_DUP is set and the previous key/data pair of the
database is not a duplicate data record for the current key/data pair.
</ul>
<a name="DB_PREV_NODUP">DB_PREV_NODUP</a><ul compact><li>If the cursor is not yet initialized, DB_PREV_NODUP is identical
to DB_LAST. Otherwise, the cursor is moved to the previous
non-duplicate key of the database, and that key/data pair is returned.
If the database is a Queue or Recno database, DBcursor-&gt;get using the
DB_PREV_NODUP flag will ignore any keys that exist but were
never explicitly created by the application, or those that were created
and later deleted.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if DB_PREV_NODUP is set and no non-duplicate key/data pairs
occur before the cursor position in the database.
</ul>
<a name="DB_SET">DB_SET</a><ul compact><li>Move the cursor to the specified key/data pair of the database, and
return the datum associated with the given key.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if DB_SET is set and
no matching keys are found.
The DBcursor-&gt;get method will return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_KEYEMPTY">DB_KEYEMPTY</a> if DB_SET is set and the database is a
Queue or Recno database, and the specified key exists, but was never
explicitly created by the application or was later deleted.
In the presence of duplicate key values, DBcursor-&gt;get will return the
first data item for the given key.
</ul>
<a name="DB_SET_RANGE">DB_SET_RANGE</a><ul compact><li>The DB_SET_RANGE flag is identical to the DB_SET flag,
except that in the case of the Btree access method, the key is returned
as well as the data item and the returned key/data pair is the smallest
key greater than or equal to the specified key (as determined by the
Btree comparison function), permitting partial key matches and range
searches.</ul>
<a name="DB_SET_RECNO">DB_SET_RECNO</a><ul compact><li>Move the cursor to the specific numbered record of the database, and
return the associated key/data pair. The data field of the
specified key must be a pointer to a memory location from which
a <a href="../../db4-devel-4.7.25/api_c/dbt_class.html#db_recno_t">db_recno_t</a> may be read, as described in <a href="../../db4-devel-4.7.25/api_c/dbt_class.html">DBT</a>. This
memory location will be read to determine the record to be retrieved.
For DB_SET_RECNO to be specified, the underlying database must be
of type Btree, and it must have been created with the <a href="../../db4-devel-4.7.25/api_c/db_set_flags.html#DB_RECNUM">DB_RECNUM</a>
flag.</ul>
 
In addition, the following flags may be set by
bitwise inclusively OR'ing them into the flags parameter:
 
<a name="DB_IGNORE_LEASE">DB_IGNORE_LEASE</a><ul compact><li>Return the data item irrespective of the state of master leases. The
item will be returned under all conditions: if master leases are not
configured, if the request is made to a client, if the request is made
to a master with a valid lease, or if the request is made to a master
without a valid lease.</ul>
<a name="DB_READ_UNCOMMITTED">DB_READ_UNCOMMITTED</a><ul compact><li>Database items read during a transactional call will have degree 1
isolation, including modified but not yet committed data. Silently
ignored if the <a href="../../db4-devel-4.7.25/api_c/db_open.html#DB_READ_UNCOMMITTED">DB_READ_UNCOMMITTED</a> flag was not specified when
the underlying database was opened.</ul>
<a name="DB_MULTIPLE">DB_MULTIPLE</a><ul compact><li>Return multiple data items in the data parameter.
In the case of Btree or Hash databases, duplicate data items for the
current key, starting at the current cursor position, are entered into
the buffer. Subsequent calls with both the DB_NEXT_DUP and
DB_MULTIPLE flags specified will return additional duplicate
data items associated with the current key or <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if
there are no additional duplicate data items to return. Subsequent
calls with both the DB_NEXT and DB_MULTIPLE flags
specified will return additional duplicate data items associated with
the current key or if there are no additional duplicate data items will
return the next key and its data items or <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if there
are no additional keys in the database.
In the case of Queue or Recno databases, data items starting at the
current cursor position are entered into the buffer. The record number
of the first record will be returned in the key parameter. The
record number of each subsequent returned record must be calculated from
this value. Subsequent calls with the DB_MULTIPLE flag
specified will return additional data items or <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if
there are no additional data items to return.
The buffer to which the data parameter refers must be provided
from user memory (see <a href="../../db4-devel-4.7.25/api_c/dbt_class.html#DB_DBT_USERMEM">DB_DBT_USERMEM</a>). The buffer must be at
least as large as the page size of the underlying database, aligned for
unsigned integer access, and be a multiple of 1024 bytes in size. If
the buffer size is insufficient, then upon return from the call the size
field of the data parameter will have been set to an estimated
buffer size, and the error DB_BUFFER_SMALL is returned. (The size is an estimate as the
exact size needed may not be known until all entries are read. It is
best to initially provide a relatively large buffer, but applications
should be prepared to resize the buffer as necessary and repeatedly call
the method.)
The multiple data items can be iterated over using the
<a href="../../db4-devel-4.7.25/api_c/dbt_bulk.html#DB_MULTIPLE_NEXT">DB_MULTIPLE_NEXT</a> macro.
The DB_MULTIPLE flag may only be used with the
DB_CURRENT, DB_FIRST, DB_GET_BOTH,
DB_GET_BOTH_RANGE, DB_NEXT, DB_NEXT_DUP,
DB_NEXT_NODUP, DB_SET, DB_SET_RANGE, and
DB_SET_RECNO options. The DB_MULTIPLE flag may not be
used when accessing databases made into secondary indices using the
<a href="../../db4-devel-4.7.25/api_c/db_associate.html">DB-&gt;associate</a> method.</ul>
<a name="DB_MULTIPLE_KEY">DB_MULTIPLE_KEY</a><ul compact><li>Return multiple key and data pairs in the data parameter.
Key and data pairs, starting at the current cursor position, are entered
into the buffer. Subsequent calls with both the DB_NEXT and
DB_MULTIPLE_KEY flags specified will return additional key and data
pairs or <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_NOTFOUND">DB_NOTFOUND</a> if there are no additional key and data
items to return.
In the case of Btree or Hash databases,
the multiple key and data pairs can be iterated over using the
<a href="../../db4-devel-4.7.25/api_c/dbt_bulk.html#DB_MULTIPLE_KEY_NEXT">DB_MULTIPLE_KEY_NEXT</a> macro.
In the case of Queue or Recno databases,
the multiple record number and data pairs can be iterated over using the
<a href="../../db4-devel-4.7.25/api_c/dbt_bulk.html#DB_MULTIPLE_RECNO_NEXT">DB_MULTIPLE_RECNO_NEXT</a> macro.
The buffer to which the data parameter refers must be provided
from user memory (see <a href="../../db4-devel-4.7.25/api_c/dbt_class.html#DB_DBT_USERMEM">DB_DBT_USERMEM</a>). The buffer must be at
least as large as the page size of the underlying database, aligned for
unsigned integer access, and be a multiple of 1024 bytes in size. If
the buffer size is insufficient, then upon return from the call the size
field of the data parameter will have been set to an estimated
buffer size, and the error DB_BUFFER_SMALL is returned. (The size is an estimate as the
exact size needed may not be known until all entries are read. It is
best to initially provide a relatively large buffer, but applications
should be prepared to resize the buffer as necessary and repeatedly call
the method.)
The DB_MULTIPLE_KEY flag may only be used with the
DB_CURRENT, DB_FIRST, DB_GET_BOTH,
DB_GET_BOTH_RANGE, DB_NEXT, DB_NEXT_DUP,
DB_NEXT_NODUP, DB_SET, DB_SET_RANGE, and
DB_SET_RECNO options. The DB_MULTIPLE_KEY flag may not
be used when accessing databases made into secondary indices using the
<a href="../../db4-devel-4.7.25/api_c/db_associate.html">DB-&gt;associate</a> method.</ul>
<a name="DB_RMW">DB_RMW</a><ul compact><li>Acquire write locks instead of read locks when doing the read, if
locking is configured. Setting this flag can eliminate deadlock during
a read-modify-write cycle by acquiring the write lock during the read
part of the cycle so that another thread of control acquiring a read
lock for the same item, in its own read-modify-write cycle, will not
result in deadlock.
</ul>
 </ul>
 key<ul compact><li>The key <a href="../../db4-devel-4.7.25/api_c/dbt_class.html">DBT</a> operated on.</ul>
 pkey<ul compact><li>The secondary index key <a href="../../db4-devel-4.7.25/api_c/dbt_class.html">DBT</a> operated on.</ul>
 
 Errors
The DBcursor-&gt;get method
may fail and return one of the following non-zero errors:
 
DB_BUFFER_SMALL<ul compact><li>The requested item could not be returned due to undersized buffer.</ul>
 
 
DB_LOCK_DEADLOCK<ul compact><li>A transactional database environment operation was selected to resolve
a deadlock.</ul>
DB_LOCK_NOTGRANTED<ul compact><li>A Berkeley DB Concurrent Data Store database environment configured for lock timeouts was unable
to grant a lock in the allowed time.</ul>
 
 
DB_REP_HANDLE_DEAD<ul compact><li>The database handle has been invalidated because a replication election
unrolled a committed transaction.</ul>
 
 
DB_REP_LEASE_EXPIRED<ul compact><li>The operation failed because the site's replication master lease has expired.</ul>
 
 
DB_REP_LOCKOUT<ul compact><li>The operation was blocked by client/master synchronization.</ul>
 
 
DB_SECONDARY_BAD<ul compact><li>A secondary index references a nonexistent primary key.</ul>
 
 
EINVAL<ul compact><li>If the DB_CURRENT, DB_NEXT_DUP or DB_PREV_DUP flags
were specified and the cursor has not been initialized;
the DBcursor-&gt;pget method was called with a cursor that does not refer to a
secondary index; or if an
invalid flag value or parameter was specified.</ul>
 
<hr size=1 noshade>
 Class
<a href="../../db4-devel-4.7.25/api_c/dbc_class.html">DBC</a>
 See Also
<a href="../../db4-devel-4.7.25/api_c/dbc_list.html">Database Cursors and Related Methods</a>
</tt>
<table width="100%"><tr><td> </td><td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a><a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager