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

See also: Error Codes for MariaDB Enterprise Server 10.6, in 10.5 ES, in 10.4 ES, in 10.3 ES, in 10.2 ES, in 10.6 CS, in 10.5 CS, in 10.4 CS, in 10.3 CS, and in 10.2 CS

See also: Error Codes for MariaDB Enterprise Server 10.6, in 10.5 ES, and in 10.4 ES

USAGE

DETAILS

SYNONYMS

SCHEMA

PARAMETERS

SKYSQL

PRIVILEGES

EXAMPLES

ERROR HANDLING

FEATURE INTERACTION

RESPONSES

DIAGNOSIS

ISO 9075:2016

CHANGE HISTORY

Release Series

History

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

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