Hi, I'm using MySQL-Max-4.0.1-alpha on WinNT4SP6 with InnoDB as default table type. I have a database creation script like this:
//Section A CREATE TABLE AParents ( Id int unsigned not null auto_increment, Parent int unsigned not null, primary key (Id), index Parent (Parent) ) TYPE = InnoDB; CREATE TABLE AChildren ( Id int unsigned not null auto_increment, Parent int unsigned not null, primary key (Id), index Parent (Parent), foreign key (Parent) references AParents (Id) ) TYPE = InnoDB; //Section B CREATE TABLE BParents ( Id int unsigned not null auto_increment, Parent int unsigned not null, primary key (Id), index Parent (Parent) ) TYPE = InnoDB; CREATE TABLE BChildren ( Id varchar(13) not null default '', Parent int unsigned not null, primary key (Id), index Parent (Parent), foreign key (Parent) references BParents (Id) ) TYPE = InnoDB; When I run the section A and B in any order, MySQL crashes and InnoDB tablespaces go wrong and they cannot be repaired (as I restart MySQL). The crash appears when I create the second table with a foreign key constraint. Do I do something wrong or this is a real bug in InnoDB? Thx, Dani -------------------------------------------------- http://www.mailbox.hu - Mert levelezni kell... --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
