The DB->get function retrieves key/data pairs from the database. The
and length of the data associated with the specified key are
returned in the structure referenced by data.
In the presence of duplicate key values, DB->get will return the
first data item for the designated key. Duplicates are sorted by insert
order except where this order has been overridden by cursor operations.
Retrieval of duplicates requires the use of cursor operations.
See DBcursor->c_get for details.
If the file is being accessed under transaction protection, the
txnid parameter is a transaction ID returned from
txn_begin, otherwise, NULL.
The flags parameter must be set to 0 or one of the following
Return the record number and data from the available record closest to
the head of the queue and delete the record. The cursor will be
positioned on the deleted record. The record number will be returned
in key as described in DBT. The data will be returned
in the data parameter. A record is available if it is not
deleted and is not currently locked. The underlying database must be
of type Queue for DB_CONSUME to be specified.
The DB_CONSUME_WAIT flag is the same as the DB_CONSUME
flag except that if the Queue database is empty, the thread of control
will wait until there is data in the queue before returning. The
underlying database must be of type Queue for DB_CONSUME_WAIT
to be specified.
Retrieve the specified numbered key/data pair from a database.
Upon return, both the key and data items will have been
filled in, not just the data item as is done for all other uses of the
The data field of the specified key
must be a pointer to a logical record number (i.e., a db_recno_t).
This record number determines 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 DB_RECNUM flag.
In addition, the following flag may be set by bitwise inclusively OR'ing it into the
Acquire write locks instead of read locks when doing the retrieval.
Setting this flag may decrease the likelihood of deadlock during a
read-modify-write cycle by immediately 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.
As the DB->get interface will not hold locks across
Berkeley DB interface calls in non-transactional environments, the
DB_RMW flag to the DB->get call is only meaningful in
the presence of transactions.
If the database is a Queue or Recno database and the requested key exists,
but was never explicitly created by the application or was later deleted,
the DB->get function returns DB_KEYEMPTY.
Otherwise, if the requested key is not in the database, the
DB->get function returns DB_NOTFOUND.
Otherwise, the DB->get function returns a non-zero error value on failure and 0 on success.
The DB->get function may fail and return a non-zero error for the following conditions:
The operation was selected to resolve a deadlock.
There was insufficient memory to return the requested item.
The DB->get function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions.
If a catastrophic error has occurred, the DB->get function may fail and return
DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail
in the same way.