projects / platform / upstream / lmdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 77001f5) | patch
bugfix for mdb_cursor_put with MDB_MULTIPLE
authorClaude Brisson <claude.brisson@gmail.com>
Fri, 22 Mar 2013 15:00:21 +0000 (16:00 +0100)
committerHoward Chu <hyc@symas.com>
Sat, 23 Mar 2013 21:03:12 +0000 (14:03 -0700)
commitbbb27cde4af7d9f60ca77b4b0caea4b6237ed289
tree50c57ceb7c19b1e5d21c2d13c1c6336afd558aebtree | snapshot
parent77001f549ba5b28a4cff89c4d58012a106985437commit | diff
bugfix for mdb_cursor_put with MDB_MULTIPLE

If the variable dkey.mv_size is non-zero, then it means dkey
contains some original data which has to be put back in the
child db, typically when the child db has just been created.

But when using MDB_MULTIPLE, if this variable has not been
reset to zero, we may come back to this section and wrongly
think that there is some original data to be taken care of.
libraries/liblmdb/mdb.c diff | blob | history
Domain: System / Base;