: 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:
>
-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:
>
> Connection 1:
> mysql> create table t(a int primary key) type = innodb;
> Query OK, 0 rows affected (0.13 sec)
>
> mysql>
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
Tuuri [mailto:[EMAIL PROTECTED]
Sent: Monday, November 21, 2005 4:21 AM
To: mysql@lists.mysql.com
Cc: Noga Woronoff
Subject: Re: Regarding SET FOREIGN_KEY_CHECKS=0;
Noga,
if SET FOREIGN_KEY_CHECKS=0 affects other connections to the database,
that
is a serious bug.
If you can repeat the proble
Woronoff
Subject: Re: Regarding SET FOREIGN_KEY_CHECKS=0;
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:
[EMAI
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
Welc
