import com.sleepycat.db.*;

public int put(DbTxn txnid, Dbt key, Dbt data, int flags) throws DbException;


The Db.put method stores key/data pairs in the database. The default behavior of the Db.put function is to enter the new key/data pair, replacing any previously existing key if duplicates are disallowed, or adding a duplicate data item if duplicates are allowed. If the database supports duplicates, the Db.put method adds the new data value at the end of the duplicate set. If the database supports sorted duplicates, the new data value is inserted at the correct sorted location.

If the operation is to be transaction-protected, the txnid parameter is a transaction handle returned from DbEnv.txn_begin; otherwise, null.

The flags value must be set to 0 or one of the following values:

Append the key/data pair to the end of the database. For the Db.DB_APPEND flag to be specified, the underlying database must be a Queue or Recno database. The record number allocated to the record is returned in the specified key.

There is a minor behavioral difference between the Recno and Queue access methods for the Db.DB_APPEND flag. If a transaction enclosing a Db.put operation with the Db.DB_APPEND flag aborts, the record number may be decremented (and later reallocated by a subsequent Db.DB_APPEND operation) by the Recno access method, but will not be decremented or reallocated by the Queue access method.

In the case of the Btree and Hash access methods, enter the new key/data pair only if it does not already appear in the database. If the key/data pair already appears in the database, Db.DB_KEYEXIST is returned. The Db.DB_NODUPDATA flag may only be specified if the underlying database has been configured to support sorted duplicates.

The Db.DB_NODUPDATA flag may not be specified to the Queue or Recno access methods.

Enter the new key/data pair only if the key does not already appear in the database. If the key already appears in the database, Db.DB_KEYEXIST is returned. Even if the database allows duplicates, a call to Db.put with the Db.DB_NOOVERWRITE flag set will fail if the key already exists in the database.

Otherwise, the Db.put method throws an exception that encapsulates a non-zero error value on failure.


The Db.put method may fail and throw an exception encapsulating a non-zero error for the following conditions:

An attempt was made to modify a read-only database.

An invalid flag value or parameter was specified.

A record number of 0 was specified.

An attempt was made to add a record to a fixed-length database that was too large to fit.

An attempt was made to do a partial put.

An attempt was made to add a record to a secondary index.

A btree exceeded the maximum btree depth (255).

If the operation was selected to resolve a deadlock, the Db.put method will fail and throw a DbDeadlockException exception.

The Db.put 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 Db.put method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.



See Also

Db.associate, Db.close, Db.cursor, Db.del, Db.fd, Db.get, Db.pget, Db.get_byteswapped, Db.get_type, Db.join, Db.key_range, Db.open, Db.put, Db.remove, Db.rename, Db.set_append_recno, Db.set_bt_minkey, Db.set_cachesize, Db.set_errcall, Db.set_errpfx, Db.set_feedback, Db.set_flags, Db.set_h_ffactor, Db.set_h_nelem, Db.set_lorder, Db.set_pagesize, Db.set_q_extentsize, Db.set_re_delim, Db.set_re_len, Db.set_re_pad, Db.set_re_source, Db.stat, Db.sync, Db.truncate, Db.upgrade, and Db.verify.


Copyright Sleepycat Software