Bug #15789 SET FOREIGN_KEY_CHECKS=0 has no effect
Submitted: 15 Dec 2005 19:55 Modified: 16 Dec 2005 16:35
Reporter: Boris Burtin Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1.17 OS:Windows (XP)
Assigned to: MySQL Verification Team CPU Architecture:Any

[15 Dec 2005 19:55] Boris Burtin 
Description:
SET FOREIGN_KEY_CHECKS=0 seems to have no effect when I run it in the MySQL Query Browser.  When I turn off foreign key checks and then run an INSERT or LOAD DATA INFILE that results in a foreign key violation, I still get the foreign key error.  This feature works as expected in the command-line mysql client.

How to repeat:
* Start MySQL Query Browser
* SET FOREIGN_KEY_CHECKS=0
* Run an INSERT statement that generates a foreign key violation

Suggested fix:
MySQL Query Browser should support SET FOREIGN_KEY_CHECKS=0.
[16 Dec 2005 13:13] MySQL Verification Team 
That is by design that for every query Query Browser opens a new session.
Use a script for that use.
[16 Dec 2005 16:35] Boris Burtin 
Fair enough, but for the record, it's a pretty confusing design.  Every other database client I've used maintains the same user session across multiple SQL statements.