List: MySQL General Discussion Previous MessageNext Message
From: Heikki Tuuri Date: January 21 2004 4:32am
Subject: Re: InnoDB locking 'non-existence' of a row
Alex,
diagram:
record1 'gap' record2
(User A holds a next-key lock on record2)
InnoDB can lock the non
Alex,
- Original Message -
From: Zeltser, Alex [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 21, 2004 10:28 PM
Subject: RE: InnoDB locking 'non-existence' of a row
Hello Heikki,
Thank you for your reply and your explanation. It clarifies things
: [EMAIL PROTECTED]
Subject: Re: InnoDB locking 'non-existence' of a row
Hi Alex!
On Sat, 2004-01-17 at 05:50, Zeltser, Alex wrote:
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
'
non-existence of a row?
Thanks in advance,
Alex
-Original Message-
From: Chris Nolan [mailto:[EMAIL PROTECTED]
Sent: Friday, January 16, 2004 4:55 PM
To: Zeltser, Alex
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB locking 'non-existence' of a row
Hi Alex!
On Sat, 2004
]
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
happening. One way
to accomplish what you want is to create a separate insert
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,=20
Selecting a non-existent row won't acquire any locks that prevents =
inserts from happening. One way
to accomplish
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 *
Hi Alex!
On Sat, 2004-01-17 at 05:50, Zeltser, Alex wrote:
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
