#include <db.h>

int
DB->put(DB *db,
    DB_TXN *txnid, DBT *key, DBT *data, u_int32_t flags);

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.

Unless otherwise specified, the DB->put method returns a non-zero error value on failure and 0 on success.

• The flags parameter must be set to 0 or one of the following values:
  DB_APPEND
  • Append the key/data pair to the end of the database. For the 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_APPEND flag. If a transaction enclosing a DB->put operation with the DB_APPEND flag aborts, the record number may be decremented (and later reallocated by a subsequent DB_APPEND operation) by the Recno access method, but will not be decremented or reallocated by the Queue access method.

  DB_NODUPDATA
  • 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.

    The DB_NODUPDATA flag may only be specified if the underlying database has been configured to support sorted duplicates. The DB_NODUPDATA flag may not be specified to the Queue or Recno access methods.

    The DB->put method will return DB_KEYEXIST if DB_NODUPDATA is set and the key/data pair already appears in the database.

  DB_NOOVERWRITE
  • Enter the new key/data pair only if the key does not already appear in the database. The DB->put method call with the DB_NOOVERWRITE flag set will fail if the key already exists in the database, even if the database supports duplicates.

    The DB->put method will return DB_KEYEXIST if DB_NOOVERWRITE is set and the key already appears in the database.

  
  

• The data DBT operated on.

• The key DBT operated on.

• If the operation is part of an application-specified transaction, the txnid parameter is a transaction handle returned from DB_ENV->txn_begin; if the operation is part of a Berkeley DB Concurrent Data Store group, the txnid parameter is a handle returned from DB_ENV->cdsgroup_begin; otherwise NULL. If no transaction handle is specified, but the operation occurs in a transactional database, the operation will be implicitly transaction protected.

The DB->put method may fail and return one of the following non-zero errors:

• A transactional database environment operation was selected to resolve a deadlock.

• A Berkeley DB Concurrent Data Store database environment configured for lock timeouts was unable to grant a lock in the allowed time.

• The database handle has been invalidated because a replication election unrolled a committed transaction.

• The operation was blocked by client/master synchronization.

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

• If 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; or if an invalid flag value or parameter was specified.

• A btree exceeded the maximum btree depth (255).