diff options
-rw-r--r-- | NEWS | 9 | ||||
-rw-r--r-- | NOTE-WARNING | 16 | ||||
-rw-r--r-- | README | 2 |
3 files changed, 22 insertions, 5 deletions
@@ -1,4 +1,4 @@ -GNU dbm NEWS -- history of user-visible changes. 2011-08-09 +GNU dbm NEWS -- history of user-visible changes. 2011-08-11 Copyright (C) 1990-2011 Free Software Foundation, Inc. See the end of file for copying conditions. @@ -37,6 +37,13 @@ if dir is linked to pag, and if so breaks the link and creates a new dir file. When such a database is opened in a read-only mode, GDBM does not attempt to alter the link. +* gdbm_setopt + +New options are implemented for use with gdbm_setopt function. +In particular, a set of options is provided for retrieving various +database parameters, such as the file name, memory mapping status, +etc. + * The testgdbm program is installed Testgdbm is an interactive tool for manipulating GDBM database files. diff --git a/NOTE-WARNING b/NOTE-WARNING index 9600df8..6b1c197 100644 --- a/NOTE-WARNING +++ b/NOTE-WARNING @@ -7,18 +7,28 @@ system architectures, or potentially even different compilers. Differences in byte order, the size of file offsets, and even structure packing make gdbm files non-portable. -Gdbm version 1.9.0 includes `large file' support, enabling it on operating +Gdbm version 1.9 includes `large file' support, enabling it on operating systems where it is not the default. `Large file' support is essentially when a system uses 64bit file offsets. Gdbm has, of course, supported `large files' on systems where it was the default for a very long time. On some systems, such as Solaris, this functionality is not enabled by -default. Gdbm will now enable it. THIS MEANS THAT GDBM 1.9.0 MAY NOT BE +default. Gdbm will now enable it. THIS MEANS THAT GDBM 1.9 MAY NOT BE ABLE TO ACCESS DATABASES CREATED BY PREVIOUS VERIONS ON THE SAME SYSTEM. Running the `configure' script with the `--disable-largefile' flag should produce a backwards-compatible build on such a system. However, for maximum compatibility, and increased functionality, you may want to have your application produce a portable copy of your database with the 1.8.3 version -of the library, and then load it back into version 1.9.0. +of the library, and then load it back into version 1.9. + +Gdbm 1.9 contains a utility designed to help you produce such a portable +copy: gdbmexport. To build it, configure the package with the +--enable-gdbm-export option. For the information on how to use this +utility, refer to the documentation, chapter 17 "Export a database into +a portable format." (run `info gdbm gdbmexport' to access it, once +gdbm 1.9 has been installed, or `info -f doc/gdbm.info gdbmexport' to +access the shipped info file). + + @@ -40,7 +40,7 @@ UNIX-like dbm and ndbm interfaces. ** --enable-gdbm-export -Build and install gdbmexport with specified gdbm 1.8 library. +Build and install gdbmexport with the specified gdbm 1.8 library. ** --with-gdbm183-library=LIB |