MySQL error "Error 1215: Cannot add foreign key constraint" is usually caused by the foreign key setting that does not meet the prerequisites. 1. Data type mismatch: The data type, length, and symbol attributes of the foreign key and the primary key field must be the same; 2. Engine inconsistency: Only the InnoDB engine supports foreign keys, so make sure that the table uses InnoDB; 3. Different character sets or sorting rules: It is recommended to unify the character set and sorting rules; 4. Fields are not indexed: Foreign key fields should be explicitly indexed; 5. Table or field names are spelled incorrectly: Check whether they exist and whether they are spelled correctly. During the investigation, the above reasons can be corrected one by one.
MySQL error "Error 1215: Cannot add foreign key constraint" is a common problem that many people encounter when creating tables or adding foreign keys. This problem is usually not a syntax error, but is caused by the foreign key settings that do not meet certain prerequisites.

Here are some common reasons and solutions, and directly add the information:
Data type mismatch
The foreign key field and the primary key field it references must have exactly the same data type and length , including whether it is signed/unsigned.

For example, if your primary key is INT UNSIGNED
and your foreign key is INT
, it will fail.
? Solution:

- Confirm whether the two fields are consistent
- Length, accuracy, and symbols must be matched one by one
Engine inconsistency (MyISAM and InnoDB)
Only the InnoDB engine in MySQL supports foreign key constraints . If your table is using MyISAM or other engine, an error will be reported even if the structure is not problem.
? Check method:
SHOW CREATE TABLE your_table_name;
? Modify the engine:
ALTER TABLE your_table_name ENGINE=InnoDB;
Character set or sorting rules are different (utf8mb4 vs utf8)
Although this effect is not as direct as the previous two, sometimes inconsistent character sets or collations can lead to failure in creating foreign keys, especially when cross-table references.
? It is recommended to unify character sets and collation rules, such as:
CREATE TABLE example ( id INT PRIMARY KEY ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
Fields have no index
If the foreign key field is not explicitly indexed, in some cases MySQL will automatically add one for you. But if the field has no index when you manually add a foreign key, an error may occur.
? It is recommended to add indexes in advance:
CREATE INDEX idx_name ON table_name(foreign_key_column);
Table does not exist or is spelled wrongly
Sometimes you just write the table or field name incorrectly, especially under case-sensitive systems, which are easily overlooked.
? Checkpoint:
- Is it spelled correctly
- Whether the table exists
- Is the field name wrong
Basically these common reasons. This type of problem is not complicated, but it is easy to get stuck due to negligence in details. When encountering 1215 errors, it is recommended to check them one by one according to the above points, and most cases can be solved.
The above is the detailed content of mysql error 1215 cannot add foreign key constraint. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

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

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

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

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

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_
