Adding Foreign Key Fails in MySQL (errno 150)

问题:

I've read many other posts about receiving MySQL errno 150 when trying to add a foreign key copnstraint, however I haven't found a solution yet. I hope I'm not doing something stupid. I made a simple test case.

1. Both tables are InnoDB.
2. Both tables are UTF-8.

3. Both columns are int(11) unsigned (making color_id NOT NULL doesn't make a difference). (EDIT: I WAS WRONG ABOUT THIS, AND THIS WAS THE SOLUTION)

   Here are my two tables:

Table widgets:

CREATE TABLE `widgets` (
`id` int(11) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(100) NOT NULL DEFAULT '',
`color_id` int(11) DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Table colors:

CREATE TABLE `colors` (
`id` int(11) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(10) NOT NULL DEFAULT '',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

I just created these tables, there is no content. When I try to add a foreign key constraint to link widgets.color_id to colors.id, this happens:

mysql> ALTER TABLE `widgets` ADD FOREIGN KEY (`color_id`) REFERENCES `color` (`id`);

ERROR 1005 (HY000): Can't create table 'production.#sql-7b1_2dd7' (errno: 150)

I'll just add that I haven't been able to use my GUI tool of choice -- Sequel Pro on OSX -- either. I get the same error message when trying to create a foreign key relationship.

SHOW ENGINE INNODB STATUS returns this:

130531 17:23:06 Error in foreign key constraint of table production/#sql-7b1_2c80: 
FOREIGN KEY (`color_id`) REFERENCES `colors` (`id`): Cannot find an index in 
the referenced table where the referenced columns appear as the first columns, 
or column types in the table and the referenced table do not match for constraint.

Am I doing something ridiculously stupid??

回答1:

color_id is not unsigned and has a DEFAULT NULL. The column types must be identical.

回答2:

Its almost always a case of type mismatch between the primary key and the foreign key.

Some tips to help in most cases:

• Check to see if the table you area trying to relate uses an engine that supports foreing keys like InnoDB
• Check if the columns are identically typed and nulled. eg (the 2 columns MUST match type, type size and sign)
• Check if the destination column have an index or primary key.