Issue 8857 - Document cursor validity after mdb_cursor_del
Summary: Document cursor validity after mdb_cursor_del
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: documentation (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-15 10:26 UTC by moneromooo-monero@users.noreply.github.com
Modified: 2018-12-19 17:19 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description moneromooo-monero@users.noreply.github.com 2018-05-15 10:26:53 UTC 
Full_Name: moneromooo
Version: 0.9.70 (lmdb), master as of 15 may 2018
OS: Linux
URL: http://paste.debian.net/plainh/fd7978de
Submission from: (NULL) (78.109.23.1)


The documentation for mdb_cursor_del does not say whether the cursor is valid or
not after the call. http://www.openldap.org/lists/openldap-devel/201502/msg00028.html
does say, so add the relevant parts to the mdb_cursor_del.

I can't find how to post a comment without a mailer, so this is a new issue
superseding the previous one, sorry. hyc requested a less verbose addition.

Patch: http://paste.debian.net/plainh/fd7978de
Comment 1 Howard Chu 2018-09-10 18:07:39 UTC 
changed notes
changed state Open to Test
moved from Incoming to Documentation
Comment 2 OpenLDAP project 2018-12-19 17:19:25 UTC 
fixed in mdb.master
Fixed in mdb.RE/0.9 (0.9.23)
Comment 3 Quanah Gibson-Mount 2018-12-19 17:19:25 UTC 
changed notes
changed state Test to Closed