#include <db.h>int DB->put(DB *db, DB_TXN *txnid, DBT *key, DBT *data, u_int32_t flags);
The DB->put function stores key/data pairs in the database.
If the database supports duplicates, the DB->put function 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 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 values:
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 to add a duplicate entry if duplicates are allowed. Even if the designated database allows duplicates, a call to DB->put with the DB_NOOVERWRITE flag set will fail if the key already exists in the database.
The DB->put function returns the value of errno on failure, 0 on success, and DB_KEYEXIST if the DB_NOOVERWRITE flag was set and the key already exists in the file.
The DB->put function may fail and return errno for any of the errors specified for the following Berkeley DB and C library functions: DB->cursor, DBcursor->c_close(3), DBcursor->c_get, DBcursor->c_put(3), __account_page(3), dbenv->db_paniccall(3), fflush(3), fprintf(3), free(3), func(3), lock_get, lock_put, lock_vec, log_put, malloc(3), memcpy(3), memmove(3), memp_fget, memp_fput, memp_fset, memset(3), realloc(3), strerror(3), vfprintf(3), and vsnprintf(3).
In addition, the DB->put function may fail and return errno for the following conditions:
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.