Randy, that is expected:
http://www.innodb.com/ibman.php#Locks_set_by_statements " If a FOREIGN KEY constraint is defined on a table, any insert, update, or delete which requires checking of the constraint condition sets shared record level locks on the records it looks at to check the constraint. Also in the case where the constraint fails, InnoDB sets these locks. " Best regards, Heikki Innobase Oy http://www.innodb.com InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables Order MySQL support from http://www.mysql.com/support/index.html .............. From: "Randy Chrismon" ([EMAIL PROTECTED]) Subject: Re: Lock Wait Timeout View: Complete Thread (2 articles) Original Format Newsgroups: mailing.database.myodbc Date: 2003-12-30 11:12:12 PST Well now, this is interesting. The agent mentione previously ran flawlessly for a couple of weeks. The day I left for Christmas vacation, I started getting the lock wait timeout error. The difference? I altered the table to include a foreign key constraint. Not sure how this could possibly be the issue but when I dropped the foreign key constraint, the agent worked perfectly. I'm still at a loss as to why this problem happened. I'm using INNODB tables in MySQL 4.0.16. It looks like the one record which timed out was being updated and the referenced record and field values existed. In addition, I had already updated 26,000 records so I can't figure out what's wrong with this one particular record. Any thoughts appreciated. Randy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]