Bug #58547 | foreign_key_checks not switch off in mysqldump with --tab option | ||
---|---|---|---|
Submitted: | 29 Nov 2010 8:24 | Modified: | 29 Nov 2010 10:44 |
Reporter: | Karl Penzhorn | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: mysqldump Command-line Client | Severity: | S3 (Non-critical) |
Version: | 5.1, 5.5 | OS: | Linux (Windows and Linux) |
Assigned to: | CPU Architecture: | Any | |
Tags: | mysqldump foreign_key_checks |
[29 Nov 2010 8:24]
Karl Penzhorn
[29 Nov 2010 8:25]
Karl Penzhorn
When using mysqldump with the --tab option, the .sql files generated are not prepended and postpended with /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; and /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; respectively. Also, UNIQUE_CHECKS is also missing. How to repeat: mysqldump -u root -ppassword mydatabase mytable > mytable type mytable mkdir mydatabasedir mysqldump -u root -ppassword --tab=mydatabasedir mydatabase type mydatabasedir\mytable.sql
[29 Nov 2010 10:44]
Susanne Ebrecht
Many thanks for writing a bug report. Verified as described. FK checks disappeared.