Comments on: MySQL (errno: 150)

By: CMR

CMR — Sun, 05 Feb 2012 02:25:00 +0000

I recently ran into this error when trying to create tables through mysql workbench’s outputted script.

Specifically, the primary key table had a compound primary key (product_id, vendor_id), and the child table had both of these as well, but for some reason MySql Workbench kept outputting the key sequence in the wrong order – (vendor_id, product_id) instead of (product_id, vendor_id). The key sequence must match the order of the primary key index on the parent table.

A quick edit of the script and it works, but I’m kind of mad at MySQL workbench right now…

By: Chris

Chris — Sun, 05 Feb 2012 03:41:00 +0000

I’m so glad I found this blog. I’m taking a course in mySQL and ran up against this error. Googled it, came here and problem solved. Thanks! No doubt, I’ll be back.

By: Piers

Piers — Sun, 05 Feb 2012 16:41:00 +0000

Bah! thanks for the tip… saved my sanity

By: Confuzed

Confuzed — Sun, 05 Feb 2012 01:43:00 +0000

Andreas: it did.

By: Andreas

Andreas — Sun, 05 Feb 2012 19:13:00 +0000

Even though this is an old post, I would also like to add that I had the same error. My solution was that I changed the table to MyISAM instead of previously set innoDB.

I have a slight memory that I’ve read that innoDB dosen’t support FK. Anyways, hope that this help someone!

By: Giannis

Giannis — Sun, 05 Feb 2012 06:26:00 +0000

Thanks!
that was really helpfull!

By: Liam O'Boyle

Liam O'Boyle — Sun, 05 Feb 2012 14:29:00 +0000

I found another case where the same error occurs. If the foreign key is not nullable, then this error is thrown if you try to set the foreign key constraint to ON DELETE SET NULL.

e.g, using the above example

ALTER TABLE vik_energy MODIFY COLUMN energy_id energy_id INT NOT NULL;

ALTER TABLE vik ADD FOREIGN KEY(energy_id) REFERENCES vik_energy(energy_id) ON DELETE SET NOT NULL;

By: D Miller

D Miller — Sun, 05 Feb 2012 06:42:00 +0000

Thanks!!

By: myyellowshoe

myyellowshoe — Sun, 05 Feb 2012 04:46:00 +0000

Hey there,
Thanks for the clear write up on this issue, though I might have found yet another caveat. Take a gander.
This code will run up untill I ad the foreign key. Funny part is, it was working like yesterday. Which I added an on cascade delete, though it is removed in this.
Gotta love sql!

CREATE TABLE vik (
vik_id INT NOT NULL AUTO_INCREMENT,
nid INT NOT NULL,
description BLOB,
PRIMARY KEY(vik_id),
energy_id INT
)ENGINE = INNODB;

CREATE TABLE vik_energy(
vik_id INT,
energy_id INT,
FOREIGN KEY(vik_id) REFERENCES vik(vik_id)

)ENGINE=INNODB;

ALTER TABLE vik ADD FOREIGN KEY(energy_id) REFERENCES vik_energy(energy_id);