[Date Prev][Date Next]
(ITS#7551) [lmdb] bugfix for mdb_cursor_put with MDB_MULTIPLE
Full_Name: Claude Brisson
Submission from: (NULL) (18.104.22.168)
(once again with the attachment...)
This patch fixes the following problem:
In mdb_cursor_put, section 'put_sub', 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 resetted to zero, we
may come back to this section and wrongly think that there is some original data
to be taken care of.
Notice: I, Claude Brisson, hereby place the following modifications to OpenLDAP
Software (and only these modifications) into the public domain. Hence, these
modifications may be freely used and/or redistributed for any purpose with or
without attribution and/or other notice.