--slave-type-conversions

Overview

This is a command-line option for the mariadbd & mysqld commands (arg: Required).

Configures how data type conversions are handled when row-based binary log events are applied. When set to the empty string, data types must match exactly, and no conversions are allowed.

See also: mariadbd & mysqld 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

USAGE

DETAILS

The --slave-type-conversions command-line option configures how data type conversions are handled when row-based binary log events are applied. Statement-based binary log events are not impacted by this system variable.

The --slave-type-conversions command-line option can impact anything that uses row-based binary log events, including MariaDB Replication, Galera ClusterGalera Cluster, and Point-in-time recovery (PITR).

Value

Description

ALL_NON_LOSSY

All safe conversions (no data loss) are allowed.

ALL_LOSSY

All lossy conversions are allowed, such as BIGINT to INT. This does not mean that safe conversions (lossless) are also allowed.

ALL_NON_LOSSY,ALL_LOSSY

All conversions are allowed, both lossy and lossless.

"" (an empty string)

The server returns an error if the table definition between the primary and replica differs and replication stops.

This command-line option is mapped to the slave_type_conversions system variable. For additional information the system variable, see "slave_type_conversions".

SYNONYMS

SCHEMA

PARAMETERS

SKYSQL

PRIVILEGES

EXAMPLES

Command-line

When MariaDB Server (mariadbd) is started via the command-line, the --slave-type-conversions command-line option can be specified:

$ mariadbd .. --slave-type-conversions='ALL_NON_LOSSY,ALL_LOSSY' ..

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.

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0.

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1.

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0.

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1.

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0.

EXTERNAL REFERENCES