1963
MariaDBERRORNotableDDLHIGH confidence

The storage engine for the table does not support BLOB/TEXT or GIS columns

Production Risk

Low — DDL is rejected.

What this means

An attempt was made to create or alter a table to add a BLOB, TEXT, or GIS (spatial) column using a storage engine that does not support these types.

Why it happens
  1. 1Creating a MEMORY or BLACKHOLE table with BLOB or TEXT columns.
  2. 2Adding a spatial column to a storage engine without GIS support.
How to reproduce
trigger — this will error
trigger — this will error
CREATE TABLE t (id INT, notes TEXT) ENGINE=MEMORY;

expected output

ERROR 1963 (HY000): The storage engine for the table does not support TEXT column types.

Fix

Switch to InnoDB or MyISAM which support BLOB/TEXT/GIS

Switch to InnoDB or MyISAM which support BLOB/TEXT/GIS
CREATE TABLE t (id INT, notes TEXT) ENGINE=InnoDB;

Why this works

InnoDB supports all column types including BLOB, TEXT, and spatial types.

Sources
Official documentation ↗

MySQL 8.0 — 1963 ER_TABLE_CANT_HANDLE_BLOB_OR_GIS

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

← All MariaDB errors