On 29/08/13 22:21, Howard Chu wrote:
Mark Zealey wrote:
I've now switched the database to use MDB_DUPSORT and found what seems to be another issue to do with invalid data being returned after mdb_cursor_del. The following code shows the behaviour against a database that I can provide you with if you need:
It would help if you actually checked the return code from mdb_cursor_get.
So, it returns EINVAL which presumably means the cursor is not active after the delete or something? Still seems like a bug in mdb_cursor_del though as that should advance to the next item (ie if flags 0 NEXT_DUP if flags NODUPDATA then NEXT) after a deletion...