`

### Key/Data Pairs

Storage and retrieval for the Berkeley DB access methods are based on key/data pairs. Both key and data items are represented by the DBT data structure. (The name DBT is a mnemonic for data base thang, and was used because no one could think of a reasonable name that wasn't already in use somewhere else.) Key and data byte strings may reference strings of zero length up to strings of essentially unlimited length. See Database limits for more information.

>     typedef struct {
>     	void *data;
>     	void *app_private;
>     	u_int32_t size;
>     	u_int32_t ulen;
>     	u_int32_t dlen;
>     	u_int32_t doff;
>     	u_int32_t flags;
>     } DBT;

In order to ensure compatibility with future releases of Berkeley DB, all fields of the DBT structure that are not explicitly set should be initialized to 0 before the first time the structure is used. Do this by declaring the structure external or static, or by calling the C library routine bzero(3) or memset(3).

By default, the flags structure element is expected to be 0. In this default case, when the application is providing Berkeley DB a key or data item to store into the database, Berkeley DB expects the data structure element to point to a byte string of size bytes. When returning a key/data item to the application, Berkeley DB will store into the data structure element a pointer to a byte string of size bytes, and the memory referenced by the pointer will be allocated and managed by Berkeley DB.

The elements of the DBT structure are defined as follows:

void *data;
  A pointer to a byte string.

void *app_private;
  This field is provided for the use of the application program, and is not used in any way by Berkeley DB.

u_int32_t size;
  The length of data, in bytes.

u_int32_t ulen;
  The size of the user's buffer (referenced by data), in bytes. This location is not written by the Berkeley DB functions.

  Note that applications can determine the length of a record by setting the ulen field to 0 and checking the return value in the size field. See the DB_DBT_USERMEM flag for more information.

u_int32_t dlen;
  The length of the partial record being read or written by the application, in bytes. See the DB_DBT_PARTIAL flag for more information.

u_int32_t doff;
  The offset of the partial record being read or written by the application, in bytes. See the DB_DBT_PARTIAL flag for more information.

u_int32_t flags;

  The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more of the following values.

  DB_DBT_MALLOC
    Ignored except when retrieving information from a database (a DB->get or DBcursor->c_get call). When this flag is set Berkeley DB will allocate memory for the returned key or data item (using malloc(3), or the user-specified malloc function) and return a pointer to it in the data field of the key or data DBT structure. As any allocated memory becomes the responsibility of the calling application, the caller must be able to determine if memory was allocated.

    It is an error to specify more than one of DB_DBT_MALLOC, DB_DBT_REALLOC and DB_DBT_USERMEM.

  DB_DBT_REALLOC
    Ignored except when retrieving information from a database (a DB->get or DBcursor->c_get call). When this flag is set Berkeley DB will allocate memory for the returned key or data item (using realloc(3), or the user-specified realloc function) and return a pointer to it in the data field of the key or data DBT structure. As any allocated memory becomes the responsibility of the calling application, the caller must be able to determine if memory was allocated.

    The difference between DB_DBT_MALLOC and DB_DBT_REALLOC is that the latter will call realloc(3) instead of malloc(3), so the allocated memory will be grown as necessary instead of the application doing repeated free/malloc calls.

    It is an error to specify more than one of DB_DBT_MALLOC, DB_DBT_REALLOC and DB_DBT_USERMEM.

  DB_DBT_USERMEM
    Ignored except when retrieving information from a database (DB->get or DBcursor->c_get call). The data field of the key or data structure must reference memory that is at least ulen bytes in length. If the length of the requested item is less than or equal to that number of bytes, the item is copied into the memory referenced by the data field. Otherwise, the size field is set to the length needed for the requested item, and the error ENOMEM is returned.

    It is an error to specify more than one of DB_DBT_MALLOC, DB_DBT_REALLOC and DB_DBT_USERMEM.

  DB_DBT_PARTIAL
    Ignored except when specified for a data parameter, where this flag causes the partial retrieval or storage of an item. If the calling application is doing a get, the dlen bytes starting doff bytes from the beginning of the retrieved data record are returned as if they comprised the entire record. If any or all of the specified bytes do not exist in the record, the get is successful and the existing bytes or 0 bytes are returned.

    For example, if the data portion of a retrieved record was 100 bytes, and a partial retrieval was done using a DBT having a dlen field of 20 and a doff field of 85, the get call would succeed, the data field would reference the last 15 bytes of the record, and the size field would be set to 15.

    If the calling application is doing a put, the dlen bytes starting doff bytes from the beginning of the specified key's data record are replaced by the data specified by the data and size structure elements. If dlen is smaller than size, the record will grow, and if dlen is larger than size, the record will shrink. If the specified bytes do not exist, the record will be extended using nul bytes as necessary, and the put call will succeed.

    It is an error to attempt a partial put using the DB->put function in a database that supports duplicate records. Partial puts in databases supporting duplicate records must be done using a DBcursor->c_put function.

    It is an error to attempt a partial put with differing dlen and size values in Queue or Recno databases with fixed-length records.

    For example, if the data portion of a retrieved record was 100 bytes, and a partial put was done using a DBT having a dlen field of 20, a doff field of 85, and a size field of 30, the resulting record would be 115 bytes in length, where the last 30 bytes would be those specified by the put call.

### Retrieved key/data permanence

When using the non-cursor Berkeley DB calls to retrieve key/data items (e.g., DB->get), the memory referenced by the pointer stored into the Dbt is only valid until the next call to Berkeley DB using the Db handle returned by DB->open. (This includes any use of the returned Db handle, including by another thread of control within the process. For this reason, when multiple threads are using the returned Db handle concurrently, one of the DB_DBT_MALLOC, DB_DBT_REALLOC or DB_DBT_USERMEM flags must be specified with any non-cursor Dbt used for key or data retrieval.)

When using the cursor Berkeley DB calls to retrieve key/data items (e.g., DBcursor->c_get), the memory referenced by the pointer into the Dbt is only valid until the next call to Berkeley DB using the DBC handle returned by DB->cursor.

### Data alignment

The Berkeley DB access methods provide no guarantees about key/data byte string alignment, and applications are responsible for arranging any necessary alignment. The DB_DBT_MALLOC, DB_DBT_REALLOC and DB_DBT_USERMEM flags may be used to store returned items in memory of arbitrary alignment.

### Logical Record Numbers

In all cases for the Queue and Recno access methods, and when calling the DB->get and DBcursor->c_get functions with the DB_SET_RECNO flag specified, the data field of the key must be a pointer to a memory location of type db_recno_t, as typedef'd in the #include <db.h> include file. This type is a 32-bit unsigned type, (which limits the number of logical records in a Queue or Recno database, and the maximum logical record which may be directly retrieved from a Btree database, to 4,294,967,296). The size field of the key should be the size of that type, i.e., in the C programming language, sizeof(db_recno_t).

Logical record numbers are 1-based, not 0-based, i.e., the first record in the database is record number 1.

`

Copyright Sleepycat Software