diff options
| author | Ben Johnson <benbjohnson@yahoo.com> | 2015-02-16 08:09:08 -0700 |
|---|---|---|
| committer | Ben Johnson <benbjohnson@yahoo.com> | 2015-02-16 08:09:08 -0700 |
| commit | 75f70a1938f7e6990b3007824db86eb9bfb387e1 (patch) | |
| tree | ef763266f987d9af6c5b645202f428d7eb5c33bd | |
| parent | Merge pull request #297 from benbjohnson/seq (diff) | |
| download | dedo-75f70a1938f7e6990b3007824db86eb9bfb387e1.tar.gz dedo-75f70a1938f7e6990b3007824db86eb9bfb387e1.tar.xz | |
README
Removed reference to LMDB's append mode being unsafe.
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -453,9 +453,9 @@ lock-free MVCC using a single writer and multiple readers. The two projects have somewhat diverged. LMDB heavily focuses on raw performance while Bolt has focused on simplicity and ease of use. For example, LMDB allows -several unsafe actions such as direct writes and append writes for the sake of -performance. Bolt opts to disallow actions which can leave the database in a -corrupted state. The only exception to this in Bolt is `DB.NoSync`. +several unsafe actions such as direct writes for the sake of performance. Bolt +opts to disallow actions which can leave the database in a corrupted state. The +only exception to this in Bolt is `DB.NoSync`. There are also a few differences in API. LMDB requires a maximum mmap size when opening an `mdb_env` whereas Bolt will handle incremental mmap resizing |