s
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: ""Zeltser, Alex"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, January 20, 2004 9:20 PM
Subject: RE: InnoDB locking 'non-existence' of a row
>
iginal Message-
From: Joe Shear [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 11:00 AM
To: Zeltser, Alex
Cc: [EMAIL PROTECTED]
Subject: RE: InnoDB locking 'non-existence' of a row
hi,
Selecting a non-existent row won't acquire any locks that prevents inserts from
hap
stead of 'FOR UPDATE', but the
results were the
same.
Is there any way to make the second session block when both it and the first one are
'locking'
non-existence of a row?
Thanks in advance,
Alex
-Original Message-
From: Chris Nolan [mailto:[EMAIL PROTECTED]
Sent: Fri
Hi,
I wanted to take advantage of the InnoDB 'gap' locking to lock 'non-existence' of a
row, the way the
manual recommends. I tried to do this by using 'select ... for update', using the
'mysql' client
from two separate sessions as shown below:
Session 1:
> set AUTOCOMMIT=0;
> begin;
> select
