| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* gdbm_fetch, gdbm_firstkey, and gdbm_nextkey behavior
If the requested key was not found, these functions return datum with
dptr pointing to NULL and set gdbm_errno to GDBM_ITEM_NOT_FOUND (in
prior releases, gdbm_errno was set to GDBM_NO_ERROR),
If an error occurred, dptr is set to NULL, and gdbm_errno to
the error code.
In any case gdbm_errno is guaranteed to have meaningful value upon
return.
* Error handling
In previous versions of GDBM, fatal errors (such as write error while
storing the key/data pair or bucket) caused immediate termination of
the program via call to exit(3). This is no longer the case.
Starting from this version, if a fatal error occurrs while modifying
the database file, that database is marked as needing recovery and
gdbm_errno is set to GDBM_NEED_RECOVERY. Calls to any GDBM functions,
except gdbm_recover, will then return immediately with the same error
code.
The function gdbm_recover examines the database file and fixes
eventual inconsistencies. Upon successful return it clears the error
state and makes the database operational again.
For backward compatibility, the fatal_func argument to gdbm_open is
retained and its functionality is not changed. If it is not NULL, the
new error handling procedures are disabled, the function it points to
will be called upon fatal errors. When it returns, exit(1) will be
called.
* Per-database error codes
In addition to gdbm_error global variable, the most recent error state
is saved in the GDBM_FILE structure. This facilitates error handling
when operating multiple GDBM databases simultaneously.
|
|
|
|
problem. Thanks, martin!
Changes:
Version 1.11, 2013-12-25
* Improved dump format.
A new dump format is implemented, which encodes all data in base64 and
stores not only key/data pairs, but also the original database file
metadata, such as file name, mode and ownership. Files in this format
can be sent without additional encapsulation over transmission
channels that normally allow only ASCII data. Dumps in this format
allow for restoring an exact copy of the database, including file
ownership and privileges.
* New function: gdbm_count
int gdbm_count (GDBM_FILE *file, gdbm_count *count);
Counts records in `file' and stores the result in the memory location
pointed to by `count'.
* New utilities: gdbm_dump and gdbm_load.
Gdbm_dump creates a plain-text dump of the GDBM database. This dump
can be used to create an exact copy of the database afterward.
The gdbm_load performs the reverse: given the dump file, it creates a
GDBM database. Apart from native GDBM dump formats, it also understands
the format generated by Berkeley DB db_dump utility. Thus, an easy
way to convert a Berkeley DB database to GDBM is:
db_dump input.db | gdbm_load output.db
* gdbmtool
The gdbmtool utility allows you to examine, modify or create GDBM
databases. It provides an easy-to-use interactive shell and can
be used for scripting. One of the unique features of gdbmtool is that
it allows to define datum structures for key and content parts, similarly
to the C "struct" declarations, and to input and display such
structured data.
|
|
|
|
|
|
COMMENT should not be longer than 70 characters.
COMMENT should not begin with 'A'.
COMMENT should not begin with 'An'.
COMMENT should not begin with 'a'.
COMMENT should not end with a period.
COMMENT should start with a capital letter.
pkglint warnings. Some files also got minor formatting, spelling, and style
corrections.
|
|
|
|
|
|
|
|
errors because of USE_BUILTIN.gdbm usage.
|
|
|
|
|
|
|
|
GNU `dbm' is a library of functions implementing a hashed database
on a disk file. The software was written by Philip A. Nelson.
This is the optional dbm and ndbm API compatibility library and headers.
|
