--slave-type-conversions
This page is part of MariaDB's Documentation.
The parent of this page is: mariadbd & mysqld for MariaDB Enterprise Server
Topics on this page:
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 11.4, in 10.6 ES, 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
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, , and Point-in-time recovery (PITR).
Value | Description |
---|---|
| All safe conversions (no data loss) are allowed. |
| All lossy conversions are allowed, such as |
| 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_
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' ..
CHANGE HISTORY
Release Series | History |
---|---|
11.4 Enterprise |
|
10.6 Enterprise |
|
10.6 Community |
|
10.5 Enterprise |
|
10.5 Community |
|
10.4 Enterprise |
|
10.4 Community |
|
10.3 Enterprise |
|
10.3 Community |
|
10.2 Enterprise |
|
10.2 Community |
|