: Heikki Tuuri; mysql@lists.mysql.com; Jim Kan; Kevin Chee
Subject: Re: Regarding SET FOREIGN_KEY_CHECKS=0;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noga Woronoff wrote:
> Hi Heikki -
>
> I tested the two connections in MySQL 4.0.26 and got the same results
as
> you did:
>
ected (0.13 sec)
>
> mysql> create table t2(a int primary key, foreign key (a) references
> t(a)) type = innodb;
> Query OK, 0 rows affected (0.08 sec)
>
> mysql> set foreign_key_checks=0;
> Query OK, 0 rows affected (0.00 sec)
>
> Connection 2:
> mysql> inse
Chee
Subject: Re: Regarding SET FOREIGN_KEY_CHECKS=0;
Noga,
yes, the setting SET FOREIGN_KEY_CHECKS=0 is per session. If it is
somehow 'inherited' to another session, that is a serious bug.
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and fo
Noga,
yes, the setting SET FOREIGN_KEY_CHECKS=0 is per session. If it is
somehow 'inherited' to another session, that is a serious bug.
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backu
innodb;
Query OK, 0 rows affected (0.08 sec)
mysql> set foreign_key_checks=0;
Query OK, 0 rows affected (0.00 sec)
Connection 2:
mysql> insert into t2 values (10);
ERROR 1216: Cannot add or update a child row: a foreign key constraint
fails
mysql>
Am I right to assume that when a MySQL-clie
Noga,
if SET FOREIGN_KEY_CHECKS=0 affects other connections to the database, that
is a serious bug.
If you can repeat the problem, please file a bug report to bugs.mysql.com
I tested this with 5.0.15, and it worked ok:
Connection 1:
[EMAIL PROTECTED]:~/mysql-5.0.15/client$ ./mysql test
PROTECTED]
Sent: Friday, November 18, 2005 2:56 PM
To: Noga Woronoff
Cc: Heikki Tuuri
Subject: Re: Regarding SET FOREIGN_KEY_CHECKS=0;
Noga,
please forward this communication to mysql@lists.mysql.com
> mysql -u root -p -e "SET FOREIGN_KEY_CHECKS=0;" < /tmp/dump.sql
FOREIGN_K
ts the SET FOREIGN_KEY_CONSTRAINTS as succeeding
right before the replace though.
John A. McCaskey
-Original Message-
From: Michael Stassen [mailto:[EMAIL PROTECTED]
Sent: Monday, July 11, 2005 11:42 AM
To: John McCaskey
Cc: mysql@lists.mysql.com
Subject: Re: SET FOREIGN_KEY_CHECKS=0 being ignored
Some addit
this is some sort of bug with the user being corrupted
somehow and permissions checks causing the SET FOREIGN_KEY_CHECKS=0 to
not work but still return success? Seems like a mysql bug then right?
John A. McCaskey
-Original Message-
From: John McCaskey
Sent: Monday, July 11, 2005 9:51 AM
To: John M
27; IDENTIFIED BY
PASSWORD '2326f23b5ff9232' |
+---
--+
1 row in set (0.00 sec)
mysql>
So it looks like this is some sort of bug with the user being corrupted
somehow and permissions checks causing the SET FOREIGN_K
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
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 though
Hello.
You may execute "SET FOREIGN_KEY_CHECKS=0;" in mysql and then use
"source sql.file;". Run mysql with -B command line option.
Terence <[EMAIL PROTECTED]> wrote:
> Hi,
>
> After reading the docs I realise that in order to use mysqldump with
just write the below lines of code to a file in the location where your
mysqldump file exists
SET FOREIGN_KEY_CHECKS = 0;
SOURCE <>;
SET FOREIGN_KEY_CHECKS = 1;
then execute the following command
mysql < <>
Thanks
Anil
DBA
-Original Message-
From: Heikki Tuuri
Terence,
- Original Message -
From: "Terence" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, December 22, 2004 5:58 AM
Subject: mysqldump and innodb - set foreign_key_checks=0
Hi,
After reading the docs I realise that in order to use mysql
Hi,
After reading the docs I realise that in order to use mysqldump with
innodb tables i need to include
SET FOREIGN_KEY_CHECKS=0;
at the top of my dump file. Is there anyway to do this when my slave
starts up or some other way. The dump file is huge and it takes ages to
open and put the line
Hello, Heikki!
In my last suggestion, you replied :
"Jungsu, Jeremy,
it can be considered as a bug that MySQL/InnoDB does not replicate the
setting
SET FOREIGN_KEY_CHECKS=0
I am working on fixing this bug in 4.0.x.
"
(I suggested it MySQL 4.0.11.)
but, "set foreign_key_checks=0&
Jungsu, Jeremy,
it can be considered as a bug that MySQL/InnoDB does not replicate the
setting
SET FOREIGN_KEY_CHECKS=0
I am working on fixing this bug in 4.0.x.
Regards,
Heikki
Innobase Oy
sql query
- Original Message -
From: ""Jeremy Tinley"" <[EMAIL
ne, I can.
-J
-Original Message-
From: wertyu [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 21, 2003 3:15 AM
To: [EMAIL PROTECTED]
Subject: "SET FOREIGN_KEY_CHECKS = 0" Suggestion.
Hello, everyone.
I'm using MySQL replication(Version 4.0.10)
Master and slave have FOR
Hello, everyone.
I'm using MySQL replication(Version 4.0.10)
Master and slave have FOREIGN KEY constration.
and I back up data with mysqldump.
but mysqldump does not produce table and record invalid order for FK.
So,when I restore data, I execute "SET FOREIGN_KEY_CHECKS = 0;"
20 matches
Mail list logo
