1614
MariaDBERRORNotableReplicationHIGH confidence
STATEMENT binlog mode but engine requires row-based logging
Production Risk
Medium — the statement fails; no data is written.
What this means
The binary log format is STATEMENT, but the storage engine used requires row-based logging.
Why it happens
- 1binlog_format=STATEMENT is set, but the statement writes to a storage engine (such as certain NDB configurations) that mandates row-based logging.
How to reproduce
trigger — this will error
trigger — this will error
SET GLOBAL binlog_format = 'STATEMENT'; -- Execute DML against a row-required engine
expected output
ERROR 1614 (HY000): Cannot execute statement: impossible to write to the binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.
Fix
Use ROW or MIXED binlog format
Use ROW or MIXED binlog format
SET GLOBAL binlog_format = 'ROW';
Why this works
Switching to ROW format satisfies the engine's logging requirement.
Sources
Official documentation ↗
MySQL 8.0 — 1614 ER_BINLOG_STMT_MODE_AND_ROW_ENGINE
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev