1726
MariaDBERRORNotableStorage EngineHIGH confidence

Storage engine does not support the requested operation

Production Risk

Low — DDL fails; no data affected.

What this means

The requested SQL operation is not supported by the storage engine used for the table.

Why it happens
  1. 1Using FULLTEXT indexes with a non-InnoDB/MyISAM engine.
  2. 2Requesting transactions on a non-transactional engine like MEMORY or CSV.
  3. 3Using partitioning on an engine that does not support it.
How to reproduce
trigger — this will error
trigger — this will error
CREATE TABLE t (body TEXT, FULLTEXT(body)) ENGINE=MEMORY;

expected output

ERROR 1726 (HY000): Storage engine 'MEMORY' does not support FULLTEXT indexes.

Fix

Use an engine that supports the required feature

Use an engine that supports the required feature
CREATE TABLE t (body TEXT, FULLTEXT(body)) ENGINE=InnoDB;

Why this works

InnoDB and MyISAM support FULLTEXT indexes; other engines do not.

What not to do

Sources
Official documentation ↗

MySQL 8.0 — 1726 ER_UNSUPPORTED_ENGINE

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

← All MariaDB errors