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 TRANSACTION ISOLATION LEVEL READ COMMITTED;
2/ User B: SET GLOBAL TRANSACTION ISOLATION LEVEL READ COMMITTED;
3/ User A:
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 TRANSACTION ISOLATION LEVEL READ COMMITTED;
2/ User B: SET GLOBAL TRANSACTION
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/ User B: SET GLOBAL TRANSACTION ISOLATION LEVEL READ COMMITTED;
3/ User A: START TRANSACTION;
4/ User B: START
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/ User B: SET GLOBAL TRANSACTION ISOLATION LEVEL READ COMMITTED;
3/
Hello,
Basically, I have multiple MySQL clients that have to delete entries from a
InnoDB table in a concurrent environment. What they do is:
1 - getting the first entry of the table that needs to by deleted, by executing
a SELECT ... LIMIT 1 query,
2 - doing stuff with the query result,
3 -
Hello.
Transactions are usually used for such purposes, just as
'select ... for update'.
You may have interest in:
http://dev.mysql.com/doc/mysql/en/InnoDB_locking_reads.html
http://dev.mysql.com/doc/mysql/en/Transactional_Commands.html
Julien ALLANOS [EMAIL PROTECTED] wrote:
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:
Hello,
Basically, I have multiple
