ER_FAILED_ROUTINE_BREAK_BINLOG

Overview

A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes

USAGE

DETAILS

SYNONYMS

SCHEMA

PARAMETERS

SKYSQL

PRIVILEGES

EXAMPLES

ERROR HANDLING

FEATURE INTERACTION

RESPONSES

DIAGNOSIS

ISO 9075:2016

CHANGE HISTORY

Release Series

History

11.4 Enterprise

  • Not present.

10.6 Enterprise

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

10.6 Community

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

10.5 Enterprise

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

10.5 Community

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

10.4 Enterprise

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

10.4 Community

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

10.3 Enterprise

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

10.3 Community

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

10.2 Enterprise

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

10.2 Community

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

Release Series

History

11.4 Enterprise

  • Not present.

10.6 Enterprise

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

10.5 Enterprise

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

10.4 Enterprise

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

EXTERNAL REFERENCES