1 .\" Copyright (c) 1990, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)dbopen.3 8.5 (Berkeley) 1/2/94
33 .\" $FreeBSD: src/lib/libc/db/man/dbopen.3,v 1.8 2002/12/19 09:40:21 ru Exp $
40 .Nd "database access methods"
47 .Fn dbopen "const char *file" "int flags" "int mode" "DBTYPE type" "const void *openinfo"
52 is the library interface to database files.
53 The supported file formats are btree, hashed and UNIX file oriented.
54 The btree format is a representation of a sorted, balanced tree structure.
55 The hashed format is an extensible, dynamic hashing scheme.
56 The flat-file format is a byte stream file with fixed or variable length
58 The formats and file format specific information are described in detail
59 in their respective manual pages
70 for reading and/or writing.
71 Files never intended to be preserved on disk may be created by setting
82 are as specified to the
84 routine, however, only the
85 .Dv O_CREAT , O_EXCL , O_EXLOCK , O_NONBLOCK ,
86 .Dv O_RDONLY , O_RDWR , O_SHLOCK
90 (Note, opening a database file
93 .\"Three additional options may be specified by
98 .\".Bl -tag -width indent
100 .\"Do the necessary locking in the database to support concurrent access.
101 .\"If concurrent access isn't needed or the database is read-only this
102 .\"flag should not be set, as it tends to have an associated performance
105 .\"Place the underlying memory pool used by the database in shared
107 .\"Necessary for concurrent access.
109 .\"Support transactions in the database.
114 .\"flags must be set as well.
125 .Dv DB_BTREE , DB_HASH
131 argument is a pointer to an access method specific structure described
132 in the access method's manual page.
137 each access method will use defaults appropriate for the system
138 and the access method.
143 returns a pointer to a
145 structure on success and
150 structure is defined in the
152 include file, and contains at
153 least the following fields:
157 int (*close)(const DB *db);
158 int (*del)(const DB *db, const DBT *key, u_int flags);
159 int (*fd)(const DB *db);
160 int (*get)(const DB *db, DBT *key, DBT *data, u_int flags);
161 int (*put)(const DB *db, DBT *key, const DBT *data,
163 int (*sync)(const DB *db, u_int flags);
164 int (*seq)(const DB *db, DBT *key, DBT *data, u_int flags);
168 These elements describe a database type and a set of functions performing
170 These functions take a pointer to a structure as returned by
172 and sometimes one or more pointers to key/data structures and a flag value.
173 .Bl -tag -width indent
175 The type of the underlying access method (and file format).
177 A pointer to a routine to flush any cached information to disk, free any
178 allocated resources, and close the underlying file(s).
179 Since key/data pairs may be cached in memory, failing to sync the file
184 function may result in inconsistent or lost information.
186 routines return -1 on error (setting
190 A pointer to a routine to remove key/data pairs from the database.
195 may be set to the following value:
196 .Bl -tag -width indent
198 Delete the record referenced by the cursor.
199 The cursor must have previously been initialized.
203 routines return -1 on error (setting
205 0 on success, and 1 if the specified
209 A pointer to a routine which returns a file descriptor representative
210 of the underlying database.
211 A file descriptor referencing the same file will be returned to all
217 This file descriptor may be safely used as an argument to the
222 The file descriptor is not necessarily associated with any of the
223 underlying files used by the access method.
224 No file descriptor is available for in memory databases.
226 routines return -1 on error (setting
228 and the file descriptor on success.
230 A pointer to a routine which is the interface for keyed retrieval from
232 The address and length of the data associated with the specified
234 are returned in the structure referenced by
237 routines return -1 on error (setting
239 0 on success, and 1 if the
243 A pointer to a routine to store key/data pairs in the database.
248 may be set to one of the following values:
249 .Bl -tag -width indent
251 Replace the key/data pair referenced by the cursor.
252 The cursor must have previously been initialized.
254 Append the data immediately after the data referenced by
256 creating a new key/data pair.
257 The record number of the appended key/data pair is returned in the
260 (Applicable only to the
264 Insert the data immediately before the data referenced by
266 creating a new key/data pair.
267 The record number of the inserted key/data pair is returned in the
270 (Applicable only to the
274 Enter the new key/data pair only if the key does not previously exist.
276 Store the key/data pair, setting or initializing the position of the
277 cursor to reference it.
278 (Applicable only to the
286 is available only for the
291 methods because it implies that the keys have an inherent order
292 which does not change.
297 are available only for the
299 access method because they each imply that the access method is able to
301 This is only true if the keys are ordered and independent, record numbers
304 The default behavior of the
306 routines is to enter the new key/data pair, replacing any previously
310 routines return -1 on error (setting
312 0 on success, and 1 if the
315 was set and the key already exists in the file.
317 A pointer to a routine which is the interface for sequential
318 retrieval from the database.
319 The address and length of the key are returned in the structure
322 and the address and length of the data are returned in the
327 Sequential key/data pair retrieval may begin at any time, and the
330 is not affected by calls to the
337 Modifications to the database during a sequential scan will be reflected
338 in the scan, i.e. records inserted behind the cursor will not be returned
339 while records inserted in front of the cursor will be returned.
345 be set to one of the following values:
346 .Bl -tag -width indent
348 The data associated with the specified key is returned.
349 This differs from the
351 routines in that it sets or initializes the cursor to the location of
355 access method, the returned key is not necessarily an
356 exact match for the specified key.
357 The returned key is the smallest key greater than or equal to the specified
358 key, permitting partial key matches and range searches.)
360 The first key/data pair of the database is returned, and the cursor
361 is set or initialized to reference it.
363 The last key/data pair of the database is returned, and the cursor
364 is set or initialized to reference it.
365 (Applicable only to the
371 Retrieve the key/data pair immediately after the cursor.
372 If the cursor is not yet set, this is the same as the
376 Retrieve the key/data pair immediately before the cursor.
377 If the cursor is not yet set, this is the same as the
380 (Applicable only to the
390 are available only for the
394 access methods because they each imply that the keys have an inherent
395 order which does not change.
398 routines return -1 on error (setting
400 0 on success and 1 if there are no key/data pairs less than or greater
401 than the specified or current key.
404 access method is being used, and if the database file
405 is a character special file and no complete key/data pairs are currently
410 A pointer to a routine to flush any cached information to disk.
411 If the database is in memory only, the
413 routine has no effect and will always succeed.
417 argument may be set to the following value:
418 .Bl -tag -width indent
422 access method is being used, this flag causes
425 routine to apply to the btree file which underlies the
426 recno file, not the recno file itself.
431 manual page for more information.)
435 routines return -1 on error (setting
440 Access to all file types is based on key/data pairs.
441 Both keys and data are represented by the following data structure:
451 structure are defined as follows:
452 .Bl -tag -width "data"
454 A pointer to a byte string.
456 The length of the byte string.
459 Key and data byte strings may reference strings of essentially unlimited
460 length although any two of them must fit into available memory at the same
462 It should be noted that the access methods provide no guarantees about
463 byte string alignment.
467 routine may fail and set
469 for any of the errors specified for the library routines
476 A file is incorrectly formatted.
478 An argument has been specified (hash function, pad byte etc.) that is
479 incompatible with the current file specification or which is not
480 meaningful for the function (for example, use of the cursor without
481 prior initialization) or there is a mismatch between the version
482 number of file and the software.
487 routines may fail and set
489 for any of the errors specified for the library routines
503 routines may fail and set
505 for any of the errors specified for the library routines
514 routines will fail and set
518 for in memory databases.
522 routines may fail and set
524 for any of the errors specified for the library routine
532 .%T "LIBTP: Portable, Modular Transactions for UNIX"
535 .%R "USENIX proceedings"
542 .Dq "data base thang" ,
544 because noone could think of a reasonable name that wasn't already used.
546 The file descriptor interface is a kluge and will be deleted in a
547 future version of the interface.
549 None of the access methods provide any form of concurrent access,
550 locking, or transactions.