Re: Serious bug (or my foolishness) with alter table and InnoDB

[Chris]

There was a serious (threat of data loss) bug in 4.1.7 InnoDB . I'm not 
very familiar with the specifics, but this problem could be that.

In any case I'd be scared to run InnoDB on a 4.1.7 without fully 
understanding the problem. You should definitely consider upgrading to 
4.1.8 , or, at the very least, look into the bugs that were fixed in 
4.1.8 and their workarounds.

Chris
Karam Chand wrote:
Hello,
I am running mysql 4.1.7 on Win2K.
I have two tables:
CREATE TABLE `child` (                      
         `id` int(11) NOT NULL default '0', 
         `name` char(1) NOT NULL default '', 
         PRIMARY KEY  (`id`,`name`)                  
                                                     
                                                     
     
       ) ENGINE=MyISAM DEFAULT CHARSET=utf8;
       
CREATE TABLE `master` (                               
                                                     
                                                     

         `id` int(11) NOT NULL default '0', 
         `name` char(10) NOT NULL default '', 
         PRIMARY KEY  (`id`,`name`) 
         ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

If I execute the following statement:
alter table child add foreign key (id) references
master (id), type = innodb;
the mysql server hangs and needs to be killed. After
restarting the table child is also lost.
Is this a known bug?
Karam
         


	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail

 


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]