PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, December 15, 2003 11:26 AM
Subject: Can I really have no_wait row-locks in MySQL+InnoDB?
> Suppose some user issued 'select ... for update', then
> went for coffee-break (to think hard on what he
> really wants to update in th
mos wrote:
At 01:14 AM 12/16/2003, you wrote:
mos wrote:
At 04:22 AM 12/15/2003, you wrote:
To elaborate on Dr Frank's thing if you're interested, here's a
classic deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which
we will call R1.
2. Transaction B obtains an
At 01:14 AM 12/16/2003, you wrote:
mos wrote:
At 04:22 AM 12/15/2003, you wrote:
To elaborate on Dr Frank's thing if you're interested, here's a classic
deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which we
will call R1.
2. Transaction B obtains an exclusive lo
mos wrote:
At 04:22 AM 12/15/2003, you wrote:
To elaborate on Dr Frank's thing if you're interested, here's a
classic deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which we
will call R1.
2. Transaction B obtains an exclusive lock on another set of rows
which we
At 04:22 AM 12/15/2003, you wrote:
To elaborate on Dr Frank's thing if you're interested, here's a classic
deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which we will
call R1.
2. Transaction B obtains an exclusive lock on another set of rows which we
will call R2
To elaborate on Dr Frank's thing if you're interested, here's a classic
deadlock example:
1. Transaction A obtains an exclusive lock on a set of rows which we
will call R1.
2. Transaction B obtains an exclusive lock on another set of rows which
we will call R2.
3. Transaction A requests (but ob
Hi,
Dmitry Anikin schrieb:
>
> Suppose some user issued 'select ... for update', then
> went for coffee-break (to think hard on what he
> really wants to update in that row). Another client
> tries to update the same row and I don't want him to
> wait, just immediately return an error, so he coul
Suppose some user issued 'select ... for update', then
went for coffee-break (to think hard on what he
really wants to update in that row). Another client
tries to update the same row and I don't want him to
wait, just immediately return an error, so he could
do some other useful task meanwhile. I
