From: Howard Chu <hyc@openldap.org>
Date: Mon, 15 Dec 2014 20:40:59 +0000 (+0000)
Subject: Fix MDB_APPEND doc
X-Git-Tag: accepted/tizen/5.0/unified/20181102.030725~272
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=7ce29b9edbdaf34b7aeb545324008ed4dff62952;p=platform%2Fupstream%2Flmdb.git

Fix MDB_APPEND doc

We actually compare the new key against the last key, to prevent
corruption.
---

diff --git a/libraries/liblmdb/lmdb.h b/libraries/liblmdb/lmdb.h
index ad0ebed..f318ad4 100644
--- a/libraries/liblmdb/lmdb.h
+++ b/libraries/liblmdb/lmdb.h
@@ -1287,10 +1287,9 @@ int  mdb_get(MDB_txn *txn, MDB_dbi dbi, MDB_val *key, MDB_val *data);
 	 *		LMDB does nothing else with this memory, the caller is expected
 	 *		to modify all of the space requested.
 	 *	<li>#MDB_APPEND - append the given key/data pair to the end of the
-	 *		database. No key comparisons are performed. This option allows
-	 *		fast bulk loading when keys are already known to be in the
-	 *		correct order. Loading unsorted keys with this flag will cause
-	 *		data corruption.
+	 *		database. This option allows fast bulk loading when keys are
+	 *		already known to be in the correct order. Loading unsorted keys
+	 *		with this flag will cause a #MDB_KEYEXIST error.
 	 *	<li>#MDB_APPENDDUP - as above, but for sorted dup data.
 	 * </ul>
 	 * @return A non-zero error value on failure and 0 on success. Some possible