Bug #65140 | Infinite loop when updating a table record with cyclical Foreign Keys | ||
---|---|---|---|
Submitted: | 28 Apr 2012 1:29 | Modified: | 2 Jun 2012 20:10 |
Reporter: | David Stavisski | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.6.4 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | Foreign Key Infinite Loop |
[28 Apr 2012 1:29]
David Stavisski
[28 Apr 2012 6:05]
Valeriy Kravchuk
Had you really tried with 5.6.5? This is what I see with current code: mysql> select version(); +----------------+ | version() | +----------------+ | 5.6.6-m9-debug | +----------------+ 1 row in set (0.00 sec) mysql> update attr set descr='Name 2' where name='OBJECT.Name'; Query OK, 1 row affected (0.04 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql> show create table attr\G *************************** 1. row *************************** Table: attr Create Table: CREATE TABLE `attr` ( `class` varchar(45) NOT NULL, `name` varchar(45) NOT NULL, `descr` varchar(45) NOT NULL, `dependon` varchar(45) DEFAULT NULL, `type` varchar(45) DEFAULT NULL, PRIMARY KEY (`name`), KEY `FK_attr_class` (`class`), KEY `FK_attr_type` (`type`), CONSTRAINT `FK_attr_class` FOREIGN KEY (`class`) REFERENCES `class` (`name`) ON DELETE CASCADE ON UPDATE NO ACTION, CONSTRAINT `FK_attr_type` FOREIGN KEY (`type`) REFERENCES `type` (`name`) ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=latin1 1 row in set (0.00 sec)
[30 Apr 2012 17:37]
David Stavisski
Yes I tried it on 5.6.4 and 5.6.5 (upto 5.6.3 it worked fine). I actually built a test CentOS image with a clean MySQL install just to diagnose it
[2 May 2012 20:10]
Sveta Smirnova
Thank you for the feedback. I can not repeat described behavior too. Please send us your configuration file and inform us which exact MySQL package (file name you downloaded) you use.
[3 Jun 2012 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".