From: Zach Vonler Date: Mon, 3 Jun 2024 19:39:02 +0000 (-0700) Subject: ITS#10222 LMDB: Updated mdb_dump man page X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b84c35053b5a0068c5215a2c02628b17969868e3;p=thirdparty%2Fopenldap.git ITS#10222 LMDB: Updated mdb_dump man page The -a option to mdb_load makes the previous text obsolete. --- diff --git a/libraries/liblmdb/mdb_dump.1 b/libraries/liblmdb/mdb_dump.1 index 5f2d771b58..9674c29f7b 100644 --- a/libraries/liblmdb/mdb_dump.1 +++ b/libraries/liblmdb/mdb_dump.1 @@ -61,14 +61,14 @@ Exit status is zero if no errors occur. Errors result in a non-zero exit status and a diagnostic message being written to standard error. -Dumping and reloading databases that use user-defined comparison functions -will result in new databases that use the default comparison functions. -\fBIn this case it is quite likely that the reloaded database will be -damaged beyond repair permitting neither record storage nor retrieval.\fP +Dumping databases that use user-defined comparison functions will output +records with the ordering imposed by those comparison functions. If +.B mdb_load +is invoked without including the +.B -a +option when reloading those records, the new databases will likely be +damaged beyond repair, permitting neither record storage nor retrieval. -The only available workaround is to modify the source for the -.BR mdb_load (1) -utility to load the database using the correct comparison functions. .SH "SEE ALSO" .BR mdb_load (1) .SH AUTHOR