Selon Harald Fuchs <[EMAIL PROTECTED]>:
> In article <[EMAIL PROTECTED]>,
> Julien ALLANOS <[EMAIL PROTECTED]> writes:
>
> > Well, I've tried the following scenario:
>
> > 1/ User A: SET GLOBAL TRANSACTION ISOLATION LEVEL READ COMMITTED;
> > 2
Selon Harald Fuchs <[EMAIL PROTECTED]>:
> In article <[EMAIL PROTECTED]>,
> Julien ALLANOS <[EMAIL PROTECTED]> writes:
>
> > Thanks, I've already read these pages.
>
> > Here is a test example I've done:
>
> > 1/ User A: SET GLOBAL T
Date : Tue, 9 Nov 2004 18:35:40 +0100
De : Julien ALLANOS <[EMAIL PROTECTED]>
Adresse de retour :Julien ALLANOS <[EMAIL PROTECTED]>
Sujet : Re: Read locks with InnoDB?
À : Gleb Paharenko <[EMAIL PROTECTED]>
> Julien ALLANOS <[EMAIL PROTECTED]> wrote:
&
ame* stuff
as A, which is something I need to avoid.
How could I achieve this? Is it possible to have blocking SELECT queries, or to
set read locks on one row (without locking all the table, to let others users
purge the following entries)?
Thanks for feedback.
--
Ju
