The name of your foreign key exceeds the maximum length of 64 characters.Applies to: Windows 10 - all editions Original KB number: 2564571 Summary.You have a syntax error in your ALTER statement or you have mistyped one of the field names in the relationship.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.
One of the fields in the relationship is part of a combination (composite) key and does not have its own individual index.You have a default value (that is, default=0) on your foreign key column.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 can fix this by either changing your cascade or setting the field to allow NULL values. You have specified a cascade ON DELETE SET NULL, but the relevant key field is set to NOT NULL.(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. In order to use foreign keys, the tables must both be InnoDB. One or both of your tables is a MyISAM table.Just add a few random characters to the end of your key name to test for this. Check that the name of your foreign key is unique within your database. The foreign key name is a duplicate of an already existing key.If one of the fields in the relationship is not a primary key, you must create an index for that field. One of the key field that you are trying to reference does not have an index and/or is not a primary key.You should also check that one is not SIGNED and the other is UNSIGNED.
For example, if one is INT(10) the key field needs to be INT as well and not BIGINT or SMALLINT or TINYINT. The two key fields type and/or size doesn’t match exactly.Foreign key-linked fields must match definitions exactly. It might be you have a typo mistake, or check case it should be same, or there's a field-type mismatch. Usually it's due to a referenced foreign key field that does not exist.
Error Code: 1005 - there is a wrong primary key reference in your code
0 kommentar(er)
