


Why Am I Getting MySQL Error 1005 (errno: 150) When Creating a Foreign Key Constraint?
Error Code: 1005. Can't create table ... (errno: 150)
In your attempt to create a foreign key constraint between tables sira_no and metal_kod, you encountered Error Code 1005, indicating an inability to create a table due to errno 150.
This error arises due to an incorrect primary key reference in your code. When defining a foreign key relationship, the referenced field in the parent table must exist, match the data type and size of the foreign key field, and have an index or be a primary key.
Troubleshooting Steps:
- Check Field Definitions: Ensure that the METAL_KODU fields in both tables have identical data types and sizes (e.g., both should be VARCHAR(4), not VARCHAR(5)), including signed or unsigned properties. Check the case sensitivity as well.
- Create an Index: Verify that the referenced METAL_KODU field in the metal_kod table has an index. Without an index, the foreign key constraint cannot be established.
- Check Table Types: Both tables involved in the relationship must use the InnoDB storage engine to support foreign key constraints.
- Inspect Foreign Key Name: Ensure that the name of your foreign key (METAL_KODU) does not duplicate an existing key.
- Handle Null Values: If the METAL_KODU field in the parent table is set to NOT NULL and you have specified ON DELETE SET NULL in the foreign key constraint, change either the column property or the cascade behavior.
- Charset and Collation: Check that the character set and collation settings match for both tables and the key columns.
- Remove Default Values: If your foreign key column has a default value (e.g., default=0), remove it.
- Check Composite Keys: If the METAL_KODU field is part of a composite key in the parent table, create a separate index for that field to support the foreign key constraint.
- Review Syntax: Double-check your ALTER TABLE statement and ensure that the field names are typed correctly.
- Foreign Key Length: Ensure that the name of your foreign key does not exceed the maximum length of 64 characters.
By addressing these potential issues, you can resolve the Error Code 1005 and successfully establish the foreign key relationship between the sira_no and metal_kod tables.
The above is the detailed content of Why Am I Getting MySQL Error 1005 (errno: 150) When Creating a Foreign Key Constraint?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The article discusses using MySQL's ALTER TABLE statement to modify tables, including adding/dropping columns, renaming tables/columns, and changing column data types.

Article discusses configuring SSL/TLS encryption for MySQL, including certificate generation and verification. Main issue is using self-signed certificates' security implications.[Character count: 159]

Article discusses popular MySQL GUI tools like MySQL Workbench and phpMyAdmin, comparing their features and suitability for beginners and advanced users.[159 characters]

Article discusses strategies for handling large datasets in MySQL, including partitioning, sharding, indexing, and query optimization.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The article discusses dropping tables in MySQL using the DROP TABLE statement, emphasizing precautions and risks. It highlights that the action is irreversible without backups, detailing recovery methods and potential production environment hazards.

Article discusses using foreign keys to represent relationships in databases, focusing on best practices, data integrity, and common pitfalls to avoid.

The article discusses creating indexes on JSON columns in various databases like PostgreSQL, MySQL, and MongoDB to enhance query performance. It explains the syntax and benefits of indexing specific JSON paths, and lists supported database systems.
