Skip to content

Instantly share code, notes, and snippets.

@alch

alch/mysql-error-150.md

Last active August 29, 2015 13:57
Show Gist options
  • Save alch/9912624 to your computer and use it in GitHub Desktop.
Save alch/9912624 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
mysql-error-150.md

From http://stackoverflow.com/questions/9018584/error-code-1005-cant-create-table-errno-150

Error Code: 1005. Wrong primary key reference in your code

Usually it's due to a reference FK field not exist. might be you have typo mistake,or check case it should be same, or there's a field-type mismatch. FK-linked fields must match definitions exactly.

Known causes may be:

  • The two key fields type and/or size doesn’t match exactly. For example, if one is INT(10) the key field needs to be INT(10) as well and not INT(11) or TINYINT. You may want to confirm the field size using SHOW CREATE TABLE because Query Browser will sometimes visually show just INTEGER for both INT(10) and INT(11). You should also check that one is not SIGNED and the other is UNSIGNED. They both need to be exactly the same.
  • One of the key field that you are trying to reference does not have an index and/or is not a primary key. If one of the fields in the relationship is not a primary key, you must create an index for that field. The foreign key name is a duplicate of an already existing key. Check that the name of your foreign key is unique within your database. Just add a few random characters to the end of your key name to test for this.
  • One or both of your tables is a MyISAM table. In order to use foreign keys, the tables must both be InnoDB. (Actually, if both tables are MyISAM then you won’t get an error message - it just won’t create the key.) In Query Browser, you can specify the table type.
  • You have specified a cascade ON DELETE SET NULL, but the relevant key field is set to NOT NULL. You can fix this by either changing your cascade or setting the field to allow NULL values. *Make sure that the Charset and Collate options are the same both at the table level as well as individual field level for the key columns.
  • You have a default value (ie default=0) on your foreign key column
  • One of the fields in the relationship is part of a combination (composite) key and does not have it’s own individual index. Even though the field has an index as part of the composite key, you must create a separate index for only that key field in order to use it in a constraint.
  • You have a syntax error in your ALTER statement or you have mistyped one of the field names in the relationship
  • 10 The name of your foreign key exceeds the max length of 64 chars.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment