Oh, I should also mention we have binary logging on and I verified by looking at the binary log that the commands are being excuted and logged with an error code of 0. So the obvious thought of the codes broken and not running them is unfortunately not the problem. It seems to be some sort of legitimate mysql setup error on our part or a bug in mysql.
John A. McCaskey -----Original Message----- From: John McCaskey [mailto:[EMAIL PROTECTED] Sent: Monday, July 11, 2005 9:46 AM To: mysql@lists.mysql.com Subject: SET FOREIGN_KEY_CHECKS=0 being ignored Hey, I have an application using the C API that is doing a REPLACE command into an innodb table that has other tables with cascading deletes relying on it's entries. Rather than use an UPDATE/Check affected/Insert/Check success/repeat method we have wrapped the REPLACE query in a SET FOREIGN_KEY_CHECKS=0; then after SET FOREIGN_KEY_CHECKS=1; pair of commands. This is working great in our dev and test environments but its been discovered that on our production servers it is apparently having no effect and the cascading deletes are occurring anyway. So, the first thing I thought was 'something must be wrong with the permissions' but I've been unable to find any discrepancies and the manual doesn't seem to indicate you even need any special permissions to execute the set command. Has anyone else experienced anything similar? Does anyone have any ideas what environmental differences could cause the SET FOREIGN_KEY_CHECKS command to be ignored? I'm at my wits end here... any suggestions appreciated. John A. McCaskey -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
