Bug #76227 | FKs are checked in some cases, even if FOREIGN_KEY_CHECK = 1 | ||
---|---|---|---|
Submitted: | 9 Mar 2015 13:28 | Modified: | 11 Mar 2015 16:33 |
Reporter: | Saverio Miroddi | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.6.23 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[9 Mar 2015 13:28]
Saverio Miroddi
[9 Mar 2015 15:55]
MySQL Verification Team
This behavior is fully documented in our manual. In the chapter 13.1.17.2, there is a section which describes the behavior when foreign_key_checks are set to 0. The text contains this description: " If you re-create a table that was dropped, it must have a definition that conforms to the foreign key constraints referencing it. " Hence, this is not a bug.
[10 Mar 2015 8:44]
Saverio Miroddi
I see, It would be still helpful to specify in the system variables chapter, that FOREIGN_KEY_CHECKS has some exceptions.
[10 Mar 2015 14:02]
MySQL Verification Team
Your request is not a bad idea. However, I am not clear what chapter exactly do you have in mind. Can you provide by its full number in the format of XX.YY.ZZ ???
[11 Mar 2015 16:33]
Saverio Miroddi
I would add it to the section: https://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_foreign_key_ch... with a simple note like 'Some exceptions apply, refer to chapter 13.1.17.2'. The existing reference "See Section 14.6.6, “InnoDB and FOREIGN KEY Constraints” itself doesn't contain any mention of such exception.
[11 Mar 2015 17:48]
MySQL Verification Team
We shall write to our team that is managing all our manuals to add the note that you specified. Thanks.
[11 Mar 2015 19:40]
Daniel Price
The foreign_key_checks description has been revised as per your suggestion. Please allow 24 hours for the revised content to appear on-line. Thank you for the report.