Issue 8250 - Allowing transaction to be created in the reset state
Summary: Allowing transaction to be created in the reset state
Status: UNCONFIRMED
Alias: None
Product: LMDB
Classification: Unclassified
Component: liblmdb (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords: has_patch
: 8010 (view as issue list)
Depends on:
Blocks:
 
Reported: 2015-09-19 18:44 UTC by rouzier@gmail.com
Modified: 2021-06-02 13:24 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description rouzier@gmail.com 2015-09-19 18:44:34 UTC
Full_Name: James Rouzier
Version: 
OS: 
URL: https://github.com/rouzier/openldap/commit/54f60e7eb699778197fa154953fccfa8ecc41d2a.patch
Submission from: (NULL) (70.81.32.80)


This patch allows mdb_txn_begin to create a transaction in the reset state.

So instead of doing this.
mdb_txn_begin(env, NULL, MDB_READONLY,&txn);
mdb_txn_reset(txn);

You now can just do this.
mdb_txn_begin(env, NULL, MDB_READONLY| MDB_TXNRESET,&txn);

You can view the patch here 
https://github.com/rouzier/openldap/commit/54f60e7eb699778197fa154953fccfa8ecc41d2a


The attached patch file is derived from OpenLDAP Software. All of the
modifications to OpenLDAP Software represented in the following patch(es) were
developed by James Rouzier <rouzier@gmail.com>.
I have not assigned rights and/or interest in this work to any party.

Comment 1 rouzier@gmail.com 2015-09-21 20:48:18 UTC
Sorry I did not retest the patch with after rebasing.
Here is the new patch and diff

https://github.com/rouzier/openldap/compare/7e476e4983cfba45cefe793b8bd6e13c486b3989...feature/txn-begin-reset.patch

https://github.com/rouzier/openldap/compare/7e476e4983cfba45cefe793b8bd6e13c486b3989...feature/txn-begin-reset.diff


On Sat, Sep 19, 2015 at 2:44 PM, <openldap-its@openldap.org> wrote:

>
> *** THIS IS AN AUTOMATICALLY GENERATED REPLY ***
>
> Thanks for your report to the OpenLDAP Issue Tracking System.  Your
> report has been assigned the tracking number ITS#8250.
>
> One of our support engineers will look at your report in due course.
> Note that this may take some time because our support engineers
> are volunteers.  They only work on OpenLDAP when they have spare
> time.
>
> If you need to provide additional information in regards to your
> issue report, you may do so by replying to this message.  Note that
> any mail sent to openldap-its@openldap.org with (ITS#8250)
> in the subject will automatically be attached to the issue report.
>
>         mailto:openldap-its@openldap.org?subject=(ITS#8250)
>
> You may follow the progress of this report by loading the following
> URL in a web browser:
>     http://www.OpenLDAP.org/its/index.cgi?findid=8250
>
> Please remember to retain your issue tracking number (ITS#8250)
> on any further messages you send to us regarding this report.  If
> you don't then you'll just waste our time and yours because we
> won't be able to properly track the report.
>
> Please note that the Issue Tracking System is not intended to
> be used to seek help in the proper use of OpenLDAP Software.
> Such requests will be closed.
>
> OpenLDAP Software is user supported.
>         http://www.OpenLDAP.org/support/
>
> --------------
> Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.
>
>
Comment 2 OpenLDAP project 2017-09-11 16:25:14 UTC
has patch
Comment 3 Quanah Gibson-Mount 2017-09-11 16:25:14 UTC
changed notes
Comment 4 Howard Chu 2021-06-02 13:24:32 UTC
*** Issue 8010 has been marked as a duplicate of this issue. ***