ySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
Order MySQL support from http://www.mysql.com/support/index.html
...
From: David Edwards ([EMAIL PROTECTED])
Subject: Re: InnoDB deadlock problem
View: Complete Threa
Hi Tobias,
Thanks for your reply. Unfortunately I couldn't see from the manual why I was getting
the deadlock - transaction 2 already has a lock on the index it is waiting for. The
difference seems to be 'insert intention' - I'm not sure what different types of
exclusive lock there are and how
On Wed, 6 Oct 2004, David Edwards wrote:
> I've got a deadlock problem using InnoDB tables
(...)
> Transaction 1:
> START TRANSACTION;
> DELETE FROM results WHERE id_job = 25920;
> INSERT INTO results(result,id_job) VALUES (31.461937,25920);
> COMMIT;
>
> Transaction 2:
> START TRANSACTION;
> DE
Hi,
I've got a deadlock problem using InnoDB tables in MySQL 4.1.5 for win32. I have two
tables, 'jobs' and 'results', where 'results' has a foreign key 'id_job' that
references the primary key of 'jobs'. There may be more than one result for any given
job. Both tables have a single auto_incre
