ER_BINLOG_UNSAFE_AND_STMT_ENGINE

Overview

Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %s

USAGE

DETAILS

SYNONYMS

SCHEMA

PARAMETERS

SKYSQL

PRIVILEGES

EXAMPLES

ERROR HANDLING

FEATURE INTERACTION

RESPONSES

DIAGNOSIS

ISO 9075:2016

CHANGE HISTORY

Release Series

History

23.08 Enterprise

  • Present starting in MariaDB Enterprise Server 23.08.0 as error number 1663

23.07 Enterprise

  • Present starting in MariaDB Enterprise Server 23.07.0 as error number 1663

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 1663

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0 as error number 1663

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 1663

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0 as error number 1663

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 1663

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0 as error number 1663

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1 as error number 1663

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0 as error number 1663

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1 as error number 1663

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0 as error number 1663

Release Series

History

23.08 Enterprise

  • Present starting in MariaDB Enterprise Server 23.08.0 as error number 1663

23.07 Enterprise

  • Present starting in MariaDB Enterprise Server 23.07.0 as error number 1663

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 1663

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 1663

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 1663

EXTERNAL REFERENCES