Error code
MySQL 1213
MYSQL1213
Database Error Code· An error code returned by a database server such as PostgreSQL or MySQL.
What it means
Deadlock found when trying to get lock — two transactions blocked each other.
How to fix it
- Retry the rolled-back transaction.
- InnoDB is designed for this — catch the error and retry.
- Ensure all transactions acquire locks in the same consistent order to prevent cycles.
- Reduce transaction scope and duration to minimize the window for conflicts.
Not affiliated with MySQL. Answer summarized from the manufacturer's manual linked above; consult that source for the authoritative procedure.
More MySQL codes
- 1216Cannot add a child row — foreign key constraint fails on INSERT
- 1217Cannot delete a parent row — foreign key constraint prevents DELETE
- 1040Too many connections — the server has reached its connection limit
- 1044Access denied for user to database — missing GRANT
- 1045Access denied for user — wrong credentials
- 1048Column cannot be null — a required column received a NULL
- 1050Table already exists — CREATE TABLE failed because the name is taken
- 1051Unknown table — a DROP or query referenced a table that does not exist
- 1054Unknown column — the column name is not defined on the table
- 1062Duplicate entry for key — unique constraint violated
- 1064SQL syntax error — the query contains invalid SQL
- 1136Column count does not match value count — INSERT column and value lists differ