Re: commit: ldap/servers/slapd/back-bdb add.c modify.c modrdn.c

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

I don't have code handy (I'm on holiday) but note that I
purposely put in a prepare before commit so that I could
do something after the prepare but before the commit
without worry that commit could fail.  However, you're
saying that prepare frees all the locks.  This seems odd
since the BDB needs to be prepared for an abort which
would require those locks.

Kurt

At 04:27 AM 12/24/2003, hyc@OpenLDAP.org wrote:
>Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-bdb
>
>Modified Files:
>        add.c  1.99 -> 1.100
>        modify.c  1.97 -> 1.98
>        modrdn.c  1.131 -> 1.132
>
>Log Message:
>ITS#2895 TXN_PREPARE is not needed since we use nested transactions. It
>also has a side-effect of releasing all the transaction's existing locks.
>
>
>CVS Web URLs:
>  http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/
>    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/add.c
>    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/modify.c
>    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/modrdn.c
>
>Changes are generally available on cvs.openldap.org (and CVSweb)
>within 30 minutes of being committed.