On 12/21/11 6:36 PM, Selcuk AYA wrote:
We have two options:
* Have a txn context per request. Store context with cursor, then when
user switches into cursor, restore its context, when it is leaving
cursor, remove txn context. This way you dont have to deal with txn
ref count or txn upgrade. I d
On Wed, Dec 21, 2011 at 12:30 PM, Emmanuel Lecharny wrote:
> Hi Selcuk,
>
> first of all, let me tell you what I'm currently doing.
>
> I started to look at the server to see if I can get the tests working, and I
> did that in my spare time while I was visiting Roma, which means I wasn't
> able to
Hi Selcuk,
first of all, let me tell you what I'm currently doing.
I started to look at the server to see if I can get the tests working,
and I did that in my spare time while I was visiting Roma, which means I
wasn't able to spend a lot of time on the code. That can explain some of
my vague
Since you cannot use triggers right now, I am assuming you are trying
to do the recursive delete thorugh ldap core connection?
As I tried to explain in my previous emails, the first thing to decide
is to where to put the transaction boundaries:
* For Ldap requests over the wite, ldap protocol han
Hi,
I tried to get some tests passing where a recursive delete is done. The
problem is that we do a search at each level, whch means we start a new
transaction at each new level.
I can easily check that a transaction has not been started yet (so that
the txn is only started once), but as I t
