Gleb Paharenko wrote:
Hello.
Among other things check that you correctly process lock timeouts.
I've check this, but it seems fine.
I'm testing it this way with 3 applications on the same computer (2
processors) :
- 2 clients applications with an open connection to the DB (which is
remote with si
Hello.
Among other things check that you correctly process lock timeouts.
>
> Well, I'm sure it's a bug hidden somewhere in my apps, i've check with
> another connexion and it worked ;)
>
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is spon
Philippe Poelvoorde wrote:
Gleb Paharenko wrote:
Hello.
What transaction isolation level do you use? By the
way - there's a fresh bug related to SELECT ... FOR UPDATE:
http://bugs.mysql.com/bug.php?id=9512
tx_isolation is set to : REPEATABLE-READ (which is the default)
I've stripped everything u
Gleb Paharenko wrote:
Hello.
What transaction isolation level do you use? By the
way - there's a fresh bug related to SELECT ... FOR UPDATE:
http://bugs.mysql.com/bug.php?id=9512
tx_isolation is set to : REPEATABLE-READ (which is the default)
I've stripped everything uneeded from my code, and pri
Hello.
What transaction isolation level do you use? By the
way - there's a fresh bug related to SELECT ... FOR UPDATE:
http://bugs.mysql.com/bug.php?id=9512
Philippe Poelvoorde <[EMAIL PROTECTED]> wrote:
> Hello,
>
> here is a snippet of my code :
>
> BEGIN
> SELECT ...
Hello,
here is a snippet of my code :
BEGIN
SELECT ... FROM table1, table2 ... FOR UPDATE
is_present = false
if ( we have results ) {
for ( all results ) {
SELECT COUNT(*) FROM table1 ... FOR UPDATE
if ( match all conditions )
is_prese
