te: Saturday, February 09, 2002 3:59 PM
Subject: Re: InnoDB foreign keys crash MySQL
>> Harald,
>
>Hi, Heikki!
>
...
>
>> I tested now with the official Linux binary of 4.0.1 (not -max) and it
>> worked ok on our dual Xeon Linux-2.4.16-SMP-64GB. I did not define any
>
ages 1
FIELDS: t2id id
FOREIGN KEY CONSTRAINT 0_17: test/t3 ( t2id )
REFERENCES test/t2 ( id )
---
END OF INNODB TABLE MONITOR OUTPUT
==
-Original Message-
From: Harald Fuchs <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>
Cc:
In article <003b01c1b0a4$351665f0$540ec5c2@omnibook>,
"Heikki Tuuri" <[EMAIL PROTECTED]> writes:
> Harald,
> I tested the below with 3.23.48, and it worked ok.
> Could it be that you have not used DROP TABLE or DROP DATABASE to remove
> InnoDB tables? Then the internal data dictionary may be out
Harald,
I tested the below with 3.23.48, and it worked ok.
Could it be that you have not used DROP TABLE or DROP DATABASE to remove
InnoDB tables? Then the internal data dictionary may be out-of-sync from the
.frm files of your tables.
Please use innodb_table_monitor (section 9.1 in
http://www.
(MySQL 4.0.1-alpha-Max-log, your Linux binary)
The following works fine (just a slight variation of what is in the manual):
CREATE TABLE t1 (
id INT UNSIGNED NOT NULL AUTO_INCREMENT,
PRIMARY KEY (id)
) TYPE=InnoDB;
CREATE TABLE t2 (
id INT UNSIGNED NOT NULL AUTO_INCREMENT,
te: Saturday, February 09, 2002 3:59 PM
Subject: Re: InnoDB foreign keys crash MySQL
>> Harald,
>
>Hi, Heikki!
>
...
>
>> I tested now with the official Linux binary of 4.0.1 (not -max) and it
>> worked ok on our dual Xeon Linux-2.4.16-SMP-64GB. I did not define any
>
ages 1
FIELDS: t2id id
FOREIGN KEY CONSTRAINT 0_17: test/t3 ( t2id )
REFERENCES test/t2 ( id )
---
END OF INNODB TABLE MONITOR OUTPUT
==
-Original Message-
From: Harald Fuchs <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>
Cc:
Harald,
I tested the below with 3.23.48, and it worked ok.
Could it be that you have not used DROP TABLE or DROP DATABASE to remove
InnoDB tables? Then the internal data dictionary may be out-of-sync from the
.frm files of your tables.
Please use innodb_table_monitor (section 9.1 in
http://www.
