Dbc.get |
import com.sleepycat.db.*;public int get(Dbt key, Dbt data, int flags) throws DbException;
The Dbc.get method retrieves key/data pairs from the database. The byte array and length of the key are returned in the object referenced by key (except for the case of the Db.DB_SET flag where the key object is unchanged), and the byte array and length of the data are returned in the object referenced by data.
Modifications to the database during a sequential scan will be reflected in the scan, i.e. 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 (i.e., entries that were never explicitly created or that were created and then deleted), will be skipped during a sequential scan.
If multiple threads or processes insert items into the same database file without using locking, the results are undefined. For more detail, see cursor stability.
The flags parameter must be set to one of the following values:
A record is available if it is not deleted and is not currently locked. For Db.DB_CONSUME to be specified, the underlying database must be of type Queue.
If the cursor key/data pair was deleted, Dbc.get will return Db.DB_KEYEMPTY.
If the cursor is not yet initialized, the Dbc.get method throws an exception that encapsulates EINVAL.
If the database is a Queue or Recno database, Dbc.get using the Db.DB_FIRST (Db.DB_LAST) flags will ignore any keys that exist but were never explicitly created by the application or were created and later deleted.
If the database is empty, Dbc.get will return Db.DB_NOTFOUND.
For Db.DB_GET_RECNO to be specified, the underlying database must be of type Btree and it must have been created with the Db.DB_RECNUM flag.
For Db.DB_JOIN_ITEM to be specified, the underlying cursor must have been returned from the Db.join method.
If the database is a Queue or Recno database, Dbc.get using the Db.DB_NEXT (Db.DB_PREV) flag will skip any keys that exist but were never explicitly created by the application or were created and later deleted.
If the cursor is already on the last (first) record in the database, Dbc.get will return Db.DB_NOTFOUND.
If the cursor is not yet initialized, the Dbc.get method throws an exception that encapsulates EINVAL.
If the database is a Queue or Recno database, Dbc.get using the Db.DB_NEXT_NODUP (Db.DB_PREV_NODUP) flags will ignore any keys that exist but were never explicitly created by the application or were created and later deleted.
If no non-duplicate key/data pairs occur after (before) the cursor position in the database, Dbc.get will return Db.DB_NOTFOUND.
In the presence of duplicate key values, Dbc.get will return the first data item for the given key.
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, Dbc.get will return Db.DB_KEYEMPTY.
If no matching keys are found, Dbc.get will return Db.DB_NOTFOUND.
For Db.DB_SET_RECNO to be specified, the underlying database must be of type Btree and it must have been created with the Db.DB_RECNUM flag.
In addition, the following flag may be set by bitwise inclusively OR'ing it into the flags parameter:
Otherwise, the Dbc.get method throws an exception that encapsulates a non-zero error value on failure.
If Dbc.get fails for any reason, the state of the cursor will be unchanged.
The Dbc.get method may fail and throw an exception encapsulating a non-zero error for the following conditions:
The specified cursor was not currently initialized.
If the operation was selected to resolve a deadlock, the Dbc.get method will fail and throw a DbDeadlockException exception.
If the requested item could not be returned due to insufficient memory, the Dbc.get method will fail and throw a DbMemoryException exception.
The Dbc.get method may fail and throw an exception for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the Dbc.get method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.