MariaDB versus MySQL - Compatibility

Drop in replacement for MySQL

For all practical purposes, MariaDB is a binary drop in replacement of the same MySQL version (for example MySQL 5.1 -> MariaDB 5.1, MariaDB 5.2 & MariaDB 5.3 are compatible. MySQL 5.5 is compatible with MariaDB 5.5 and also in practice with MariaDB 10.0). What this means is that:

• Data and table definition files (.frm) files are binary compatible.
  • See note below for an incompatibility with views!
• All client APIs, protocols and structs are identical.
• All filenames, binaries, paths, ports, sockets, and etc... should be the same.
• All MySQL connectors (PHP, Perl, Python, Java, .NET, MyODBC, Ruby, MySQL C connector etc) work unchanged with MariaDB.
  • There are some installation issues with PHP5 that you should be aware of (a bug in how the old PHP5 client checks library compatibility).
• The mysql-client package also works with MariaDB server.
• The shared client library is binary compatible with MySQL's client library.

This means that for most cases, you can just uninstall MySQL and install MariaDB and you are good to go. (No need to convert any datafiles if you use same main version, like 5.1). You must however still run mysql_upgrade to finish the upgrade. This is needed to ensure that your mysql privilege and event tables are updated with the new fields MariaDB uses.

We do monthly merges with the MySQL code base to ensure we keep up our compatibility and get any and all features and bug fixes Oracle adds.

We have also done a lot of work on the upgrade scripts to the point where it is now easier to upgrade from MySQL 5.0 to MariaDB 5.1 than from MySQL 5.0 to MySQL 5.1.

That said, MariaDB has a lot of new options, extension, storage engines and bug fixes that are not in MySQL. You can find the feature set for the different MariaDB versions on the What is in the different MariaDB Releases page.

Replication Compatibility

Note X: Refer to MySQL documentation

Note: When replication from MySQL in GTID mode, MariaDB will remove the MySQL GTID events and replace them with MariaDB GTID events.

Incompatibilities between MariaDB 5.1 and MySQL 5.1

In some few cases MariaDB has to be incompatible to allow MariaDB to provide more and better information than MySQL.

Here is the list of all known user level incompatibilities you may see when using MariaDB 5.1 instead of MySQL 5.1.

• The installation package names start with MariaDB instead of MySQL.
• Timings may be different as MariaDB is in many cases faster than MySQL.
• mysqld in MariaDB also reads the [mariadb] sections of your my.cnf files.
• You can't use a binary only storage engine library with MariaDB if it's not compiled for exactly the same MariaDB version. (This is because the server internal structure THD is different between MySQL and MariaDB. This is common also between different MySQL versions). This should not be a problem as most people don't load new storage engines and MariaDB comes with more storage engines than MySQL.
• CHECKSUM TABLE may give different result as MariaDB doesn't ignore NULL's in the columns as MySQL 5.1 does (Future MySQL versions should calculate checksums the same way as MariaDB). You can get the 'old style' checksum in MariaDB by starting mysqld with the --old option. Note however that that the MyISAM and Aria storage engines in MariaDB are using the new checksum internally, so if you are using --old, the CHECKSUM command will be slower as it needs to calculate the checksum row by row.
• The slow query log has more information about the query, which may be a problem if you have a script which parses the slow query log.
• MariaDB by default takes a bit more memory than MySQL because we have by default enabled the Aria storage engine for handling internal temporary tables. If you need MariaDB to take very little memory (at the expense of performance), you can set the value of aria_pagecache_buffer_size to 1M (the default is 128M).
• If you are using new command options, new features of MariaDB or new storage engines, you can't move easily back and forth between MySQL and MariaDB anymore.

Incompatibilities between MariaDB 5.2 and MySQL 5.1

The list is the same as between MariaDB 5.1 and MySQL 5.1, with one addition:

• A new SQL_MODE value was added: IGNORE_BAD_TABLE_OPTIONS. If it is not set, using a table, field, or index attribute (option) that is not supported by the chosen storage engine will cause an error. This change might cause warnings in the error log about incorrectly defined tables from the mysql database, fix that with mysql_upgrade.

For all practical purposes, MariaDB 5.2 is a drop in replacement for MariaDB 5.1 and MySQL 5.1.

Incompatibilities between MariaDB 5.3 and MySQL 5.1 and MariaDB 5.2

• Views with definition ALGORITHM=MERGE or ALGORITHM=TEMPTABLE got accidentally swapped between MariaDB 5.2 and MariaDB 5.3! You have to re-create views created with either of these definitions!
• A few error messages related to wrong conversions are different as MariaDB provides more information in the message about what went wrong.
• Error numbers for MariaDB-specific errors have been moved to start from 1900 so as not to conflict with MySQL errors.
• Microseconds now work in all contexts; MySQL, in some contexts, lost the microsecond part from datetime and time.
• UNIX_TIMESTAMP(constant-date-string) returns a timestamp with 6 decimals in MariaDB while MySQL returns it without a decimal. This can cause a problem if you are using UNIX_TIMESTAMP() as a partitioning function. You can fix this by using FLOOR(UNIX_TIMESTAMP(..)) or changing the date string to a date number, like 20080101000000.
• MariaDB performs stricter checking of date, datetime and timestamp values. For example UNIX_TIMESTAMP('x') now returns NULL instead of 0.
• The old --maria- startup options are removed. You should use the --aria- prefix instead. (MariaDB 5.2 supports both --maria- and --aria-)
• SHOW PROCESSLIST has an extra Progress column which shows progress for some commands. You can disable it by starting mysqld with either --old-mode=NO_PROGRESS_INFO or with the --old flag (see OLD_MODE).
• INFORMATION_SCHEMA.PROCESSLIST has three new columns for progress reporting: STAGE, MAX_STAGE, and PROGRESS.
• Long comments which start with /*M! or /*M!##### are executed.
• If you use max_user_connections=0 (which means any number of connections) when starting mysqld, you can't change the global variable anymore while mysqld remains running. This is because when mysqld is started with max_user_connections=0 it does not allocate counting structures (which also involve a mutex for each connection). This would lead to wrong counters if you later changed the variable. If you want to be able to change this variable at runtime, set it to a high value at startup.
• You can set max_user_connections (both the global variable and the GRANT option) to -1 to stop users from connecting to the server. The global max_user_connections variable does not affect users with the SUPER privilege.
• The IGNORE directive does not ignore all errors (like fatal errors), only things that are safe to ignore.

Incompatibilities between MariaDB 5.5 and MariaDB 5.3 and MySQL 5.5

• Views with definition ALGORITHM=MERGE or ALGORITHM=TEMPTABLE got accidentally swapped between MariaDB and MySQL! You have to re-create views created with either of these definitions!
• INSERT IGNORE also gives warnings for duplicate key errors. You can turn this off by setting OLD_MODE=NO_DUP_KEY_WARNINGS_WITH_IGNORE (see OLD_MODE).
• Before MariaDB 5.5.31, X'HHHH', the standard SQL syntax for binary string literals, erroneously worked in the same way as 0xHHHH, which could work as a number or string depending on the context. In 5.5.31 this was fixed to behave as a string in all contexts (and never as a number), introducing an incompatibility with previous versions of MariaDB, and all versions of MySQL. See CAST and Hexadecimal Literals for more details and examples.
• MariaDB dynamic columns are not supported by MySQL.
• MariaDB virtual columns are not supported by MySQL.
• MariaDB's HandlerSocket plugin is not supported by MySQL.
• MariaDB's Cassandra Storage Engine is not supported by MySQL.
• See also a detailed breakdown of System variable differences between MariaDB 5.5 and MySQL 5.5.

Incompatibilities between MariaDB 10.0 and MariaDB 5.5 / MySQL 5.5

• SET OPTION syntax is deprecated in MariaDB 10.0 and MySQL 5.6. Use just SET.

Incompatibilities between MariaDB 10.0 and MySQL 5.6

• MySQL does not support MariaDB's Spider Storage Engine.
• All MySQL binaries (mysqld, myisamchk etc.) give a warning if one uses a prefix of an option (such as --big-table instead of --big-tables). MariaDB binaries work in the same way as most other Unix commands and don't give warnings when using unique prefixes.
• MariaDB GTID is not compatible with MySQL 5.6. This means that one can't have MySQL 5.6 as a slave for MariaDB 10.0. However MariaDB 10.0 can be a slave of MySQL 5.6 or any earlier MySQL/MariaDB version. Note that MariaDB and MySQL also have different GTID system variables, so these need to be adjusted when migrating.
• MariaDB 10.0 multi-source replication is not supported in MySQL 5.6.
• To make CREATE TABLE ... SELECT work the same way in statement based and row based replication it's by default executed as CREATE OR REPLACE TABLE on the slave. One benefit of this is that if the slave dies in the middle of CREATE ... SELECT it will be able to continue.
  • One can use the slave-ddl-exec-mode variable to specify how CREATE TABLE and DROP TABLE is replicated.
• See also a detailed breakdown of System variable differences between MariaDB 10.0 and MySQL 5.6.
• MySQL 5.6 has performance schema enabled by default. For performance reasons MariaDB 10.0 has it disabled by default. You can enable it by starting mysqld with the option --performance-schema.
• MariaDB 10.0 does not support the MySQL Memcached plugin. However, data stored using memcached can be retrieved because the data is stored as InnoDB tables. MariaDB is able to start successfully with an error message of not being able to find libmemcached.so library.
• Users created with MySQL's SHA256 password algorithm cannot be used in MariaDB 10.0.
• MariaDB 10.0 does not support delayed replication - MDEV-7145.
• Also see a detailed breakdown of System variable differences between MariaDB 10.0 and MySQL 5.6.
• The low-level temporal format used by TIME, DATETIME and TIMESTAMP is different in MySQL 5.6 and MariaDB 10.0. (In MariaDB 10.1, the MySQL implementation is used by default - see mysql56_temporal_format.)

Incompatibilities between MariaDB 10.1 and MySQL 5.7

• MariaDB 10.1 and above does not support MySQL 5.7's JSON. MariaDB follows the SQL standard and stores the JSON as a normal TEXT/BLOB. If you want to replicate JSON columns from MySQL to MariaDB, you should store JSON objects in MySQL in a TEXT column or use statement based replication. If you are using JSON columns and want to upgrade to MariaDB, you need to use mysqldump to copy these tables to MariaDB.
• MariaDB 10.1's InnoDB encryption is implemented differently than MySQL 5.7's InnoDB encryption.
• MariaDB 10.1 does not support the ngram and MeCab full-text parser plugins - MDEV-10267, MDEV-10268.
• MariaDB 10.1 does not support multiple triggers for a table - MDEV-6112.
• MariaDB 10.1 does not support CREATE TABLESPACE for InnoDB.
• Also see Incompatibilities between MariaDB 10.0 and MySQL 5.6.
• Also see a detailed breakdown of System variable differences between MariaDB 10.1and MySQL 5.7.
• MariaDB does not support MySQL 5.7's X protocol.

Incompatibilities between MariaDB 10.2 and MySQL 5.7

• System variable differences between MariaDB 10.2 and MySQL 5.7.
• Function differences between MariaDB 10.2 and MySQL 5.7.
• Note: Multiple triggers per table was added in 10.2
• The ROWS and RECURSIVE keywords are reserved words in MariaDB 10.2, but not in MySQL 5.7.
• MariaDB InnoDB encryption is implemented differently than MySQL 5.7's InnoDB encryption.
• MariaDB stores JSON as true text, not in binary format as MySQL. The reason is that our JSON functions are much faster than MySQL's so we didn't need to see a need for storing things in binary format as it adds a lot of complexity when manipulating JSON objects. If you want to replicate JSON columns from MySQL to MariaDB, you should store JSON objects in MySQL in a TEXT column or use statement based replication. If you are using JSON columns and want to upgrade to MariaDB, you need to use mysqldump to copy these tables to MariaDB.
• For the same reason, MariaDB's JSON data type is an alias for LONGTEXT.
• MariaDB 10.2 does not support MySQL's JSON operators (-> and ->>).
• MariaDB 10.2 supports the standard by producing null and a warning for JSON_SEARCH when given invalid data, while MySQL produces an error.
• MariaDB 10.2 does not support the ngram and MeCab full-text parser plugins - MDEV-10267, MDEV-10268.
• MariaDB 10.2 does not support the MySQL X plugin.
• MariaDB 10.2 does not support the MySQL general table spaces.
• Also see Incompatibilities between MariaDB 10.1 and MySQL 5.7.

Old, unsupported configuration options

If you are using any of the following options in your /etc/my.cnf or other my.cnf file you should remove them. This is also true for MySQL 5.1 or newer:

• skip-bdb

Replacing a MySQL RPM

If you uninstalled a MySQL RPM to install MariaDB, note that the MySQL RPM on uninstall renames /etc/my.cnf to /etc/my.cnf.rpmsave.

After installing MariaDB you should do the following to restore your old configuration options:

mv -vi /etc/my.cnf.rpmsave /etc/my.cnf

Incompatibilities between MariaDB and MySQL-Proxy

A MySQL client API is able to connect to MariaDB using MySQL-Proxy but a MariaDB client API will receive progress reporting informations that MySQL-Proxy does not implement, to get full compatibility in all case just disable progress reporting on the client or server side.

Another option is to use the MariaDB MaxScale proxy, that works with both MySQL and MariaDB.

Related Links

• MariaDB vs MySQL - Features
• Moving from MySQL
• Troubleshooting Installation Issues
• Projects and applications that works with MariaDB