ER_GTID_UNSAFE_NON_TRANSACTIONAL_TABLE

Overview

When ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables

CHANGE HISTORY

Release Series

History

10.6 Enterprise

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

10.6 Community

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

10.5 Enterprise

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

10.5 Community

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

10.4 Enterprise

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

10.4 Community

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

10.3 Enterprise

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

10.3 Community

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

10.2 Enterprise

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

10.2 Community

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

Release Series

History

10.6 Enterprise

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

10.5 Enterprise

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

10.4 Enterprise

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