[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
LMDB docs
- To: openldap-technical@openldap.org
- Subject: LMDB docs
- From: KS Sreeram <ks@claylabs.com>
- Date: Tue, 3 Jul 2018 21:34:33 +0530
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=claylabs-com.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=Wxf4i8I1nv0ZgEay8EwaIfJw30sReN3K5ynR4e5JuPQ=; b=zQE5BsGiqGGT7dKoJPxX6JMf/pPIBNbd9B1t26dDdZgIgVjYqMM1e4X8Ge+i79bSu2 CkyQ7PQCmXu9W3rReH+roDT5seY9phaL6OgQwtYkY5jrHLAGlxk6xNLneK+T0+z38XPx RyQJHdEpMoTl6hPLifu47Kk3aq7kL+m9FWRsrAOyYLCMQjO+q7bqJzI0e7sn/ODH9Q0x 4IMBqB67TOIy9lFz8of816Semwv46MsBu+Xlsq+m+0hIrekMUw+bWCzWNBKKit1Zh2Nn GvSb5SLScNBAD+4o6ZSXuVDh7Y9bxzd1b8LYQSPBAgneQ37GKB5Zw93fcbo+dRkgcMiS vDMQ==
Hello folks
On this page: http://www.lmdb.tech/doc/starting.html
The following passage occurs:
> Because LMDB is very efficient (and usually zero-copy), the data returned in an MDB_val structure may be memory-mapped straight from disk. In other words look but do not touch (or free() for that matter). Once a transaction is closed, the values can no longer be used, so make a copy if you need to keep them after that.
The second sentence above is a bit misleading. Returned data cannot be used after a subsequent update. Not mentioning that is misleading.
Perhaps the second sentence can be replace with this:
> The values can no longer be used after a subsequent update or after the transaction ends. Make a copy if you need to keep them after that.
The documentation for `mdb_get` is correct and does mention the constraints. It’ll be nice to update this page too.
Best
KS Sreeram