MySQL ERROR 1136 (21S01): Column count doesn't match value count at row 1
An INSERT supplies a different number of values than columns.
Exact message you may see
Column count doesn't match value countINSERT has more expressions than target columns
Seen on:
SQL
Meaning
Omitting the column list and inserting fewer values, a missing comma, or a schema change adding columns.
Common causes
- INSERT without a column list after the table gained columns
- Missing/extra value
- Missing comma between values
⚡ Quick fix
- Always list columns explicitly in INSERT
- Count values per row
Detailed fix by platform
SQL
INSERT INTO users (email, name) VALUES ('a@b.com', 'Asha');
How to diagnose
- Counts — Columns vs values?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SQL
- unable to open database sqlite3.OperationalError: unable to open database file
- readonly database sqlite3.OperationalError: attempt to write a readonly database
- pool timeout Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. All pooled connections were in use and max pool size was reached.
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026