Bug #62361 | Foreign key constraint error while the key exist in the parent table | ||
---|---|---|---|
Submitted: | 6 Sep 2011 10:16 | Modified: | 16 Sep 2011 9:06 |
Reporter: | Cyril SCETBON | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.5.15,5.1.58 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | fk, innodb |
[6 Sep 2011 10:16]
Cyril SCETBON
[6 Sep 2011 16:07]
Cyril SCETBON
Same error with 5.1.58
[7 Sep 2011 16:46]
Cyril SCETBON
version added
[12 Sep 2011 8:05]
Cyril SCETBON
we still have the issue after having removed the DELETE orders in all sessions. However, we have some UPDATE parent-table SET OLDPK=NEWPK (PK is the foreign key referenced by the child-table) any one ?
[12 Sep 2011 21:32]
Cyril SCETBON
I checked without the last UPDATE and it seems to not be the cause as we still meet the issue. finallly, the only cause, seems to be the multithreading with foreign keys
[16 Sep 2011 9:04]
Cyril SCETBON
investigating the code in depth showed that it was not managing correctly deadlocks situations
[16 Sep 2011 9:06]
Cyril SCETBON
I was talking about the java code application of course :) Sorry for this bug report