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 d692b174bfcae1a1c6eb1b4c9857a782ebb07fbe..408b6ed0ead0c10a1713a6f8df49252f54d22129 100644 (file)
--- a/libraries/liblmdb/lmdb.h
+++ b/libraries/liblmdb/lmdb.h
@@ -1270,10 +1270,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