[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: OpenLDAP & bdb transactions

At 11:48 PM 4/25/2005, Lia Tarta wrote:
>Thanks for the reply.
>Unfortunately, the provided solution is not an option
>for me. 
>I have found this RFC:
> LDAP: Grouping of Related Operations
> <draft-zeilenga-ldap-grouping-06.txt>

First, this isn't an RFC, it's an expired Internet
Draft.  Secondly, it doesn't itself provide LDAP
transactions, but only a mechanism to group related
operations.  It can be used, as discussed in
draft-zeilenga-ldap-txn-xx.txt (another expired
Internet Draft), in support of LDAP transactions.
Lastly, grouping and transactions are not implemented
by anyone (as far as I know).

At present, slapd(8) does not support any LDAP transaction
mechanism (a mechanism that requires multiple directory
operations to be performed in one atomic, consistent,
isolated, and durable (ACID) action).


>and I am wondering if I could use grouped operations
>for my application. Actually, the question is: when
>performing 2 grouped operations, does OpenLDAP perform
>them within a single bdb transaction, or in separate
>I am asking that because I figure that Openldap opens
>a bdb transaction, for example, when it performs a
>ldapadd operation.
>--- Howard Chu <hyc@symas.com> wrote:
>> Lia Tarta wrote:
>> >Hello
>> >As I understand, OpenLDAP does not support
>> >transactions in its current version. However, the
>> bdb
>> >backend is said to be transactional. My question
>> is,
>> >how do I use these transactions for bdb? Is there
>> any
>> >way of performing a transactional operation that
>> makes
>> >2 calls (e.g.: to ADD calls) to OpenLDAP?
>> >Thanks
>> >
>> Not directly. back-bdb uses transactions within a
>> single operation, to 
>> maintain the consistency of all the indices
>> associated with a single 
>> entry. You still need a higher level control layer
>> to enforce 
>> transactions across multiple operations. You could
>> write an overlay to 
>> provide some form of transactional LDAP features, it
>> doesn't need to be 
>> implemented in the backend itself. Of course, it
>> would require a fair 
>> amount of effort to provide all of the
>> recoverability features that one 
>> expects from a transactional system.
>> -- 
>>   -- Howard Chu
>>   Chief Architect, Symas Corp.       Director,
>> Highland Sun
>>   http://www.symas.com              
>> http://highlandsun.com/hyc
>>   Symas: Premier OpenSource Development and Support
>Do you Yahoo!? 
>Yahoo! Small Business - Try our new resources site!