ilReadCommitted -- specifically set.
yes, thread2 did a previous SELECT before on the same table but each
time the statement is done, it is destroyed (gone out of context).

and it is re-prepared and executed every single time.

Commit, haven't tried CommitRetain.

just a reminder: it doesn't ALWAYS happen, I believe it depends on
timing...

>
> Does your 'thread2' execute a previously prepared SELECT or do you
> really re-prepare/execute a new SELECT after 'thread1' signaled the
> commit done ?
>
> Does thread1 really Commit or CommitRetain ?
>
> --
> Olivier
>