EC
1072
MariaDBERRORCommonDDLHIGH confidence

Key column doesn't exist in table

Production Risk

Low — DDL fails; no data loss.

What this means

ER_KEY_COLUMN_DOES_NOT_EXIST (1072, SQLSTATE 42000) is raised when CREATE TABLE or ALTER TABLE specifies an index on a column that does not exist in the table definition.

Why it happens
  1. 1Typo in the column name in the index definition
  2. 2Column was removed from the table definition but the index reference was not updated
  3. 3Index definition references a column from a different table
How to reproduce
trigger — this will error
trigger — this will error
CREATE TABLE t (id INT, INDEX idx_name (nonexistent_col));

expected output

ERROR 1072 (42000): Key column 'nonexistent_col' doesn't exist in table

Fix

Correct the column name in the index definition

WHEN Always — verify the column name exists before adding an index.

Correct the column name in the index definition
DESCRIBE t; -- verify column names
CREATE TABLE t (id INT, name VARCHAR(50), INDEX idx_name (name));

Why this works

Checking DESCRIBE or SHOW CREATE TABLE before writing DDL prevents column name typos.

What not to do

✕ Add the wrong column to the table just to satisfy the index

Adding an unneeded column bloats the row size and creates a misleading schema.

Sources
Official documentation ↗

MySQL 8.0 — 1072 ER_KEY_COLUMN_DOES_NOT_EXIST

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All MariaDB errors