MariaDB maintains high levels of compatibility with MySQL, and most applications that use MySQL will work seamlessly with MariaDB. However, take note of the following incompatibilities and feature differences between MariaDB 11.0 and MySQL 8.0. It is based on the versions MySQL 8.0.34 and MariaDB 11.0.2. Note that MySQL 8 is an 'evergreen' release, so features may be added or removed in later releases.
In addition to the standard , , , , , , and storage engines, the following are also available with MariaDB 11.0:
utilizes a massively parallel distributed data architecture and is designed for big data scaling to process petabytes of data.
, a storage engine with great compression
allows one to archive MariaDB tables in Amazon S3, or any third-party public or private cloud that implements S3 API.
, MyISAM replacement with better caching.
(drop-in replacement for Federated)
The most notable , but not in MySQL, are:
is a standard part of MariaDB Server.
in the form of:
(allow you to query and operate on historic data).
(allow you to query and operate on a temporal range of data), including the clause.
When moving from MySQL 8.0 to , please take note of the following incompatibilities:
For a list of function differences, see
For a list of system variable differences, see
MariaDB does not support MySQL's SET PERSIST -
MariaDB's GTID is not compatible with MySQL's. Note that MariaDB and MySQL also have different , so these need to be adjusted when migrating.
(which combine both system-versioning and application-time periods).
, allowing instances, databases or tables to be rolled back to an old snapshot.
MariaDB supports in a number of additional languages: Bulgarian, Chinese, Georgian, Hindi, Serbian, and Ukrainian.
MariaDB has made major improvements to the optimizer.
support
merged into the server
OR REPLACE syntax for statements, such as , , etc
, ,
syntax for setting the lock wait timeout.
data type for storing UUIDs.
and data types for storing IPv6 and IPv4 addresses.
made more granular.
Multiple
Number of supported decimals in has increased from 30 to 38
Number of parts of an index increased from 16 to 32.
Added catchall for list partitions
Oracle-style statement
Lots of new
MariaDB (506) than MySQL (266).
command to reload SSL certificates without server restart.
IF NOT EXISTS clause added to and IF EXISTS clause added to and
. This makes replication notably faster!
allows one to implement very efficient backups with minimal locking.
Progress reporting for and
gives the EXPLAIN plan for a query running in another thread. MySQL introduced the EXPLAIN FOR CONNECTION syntax to do the same thing.
(including )
and faster calls
MySQL 8 does not support
MySQL 8 does not support the use of as an alias for
The is now default on Unix-like systems, which is a major change to authentication in MariaDB. See for an overview of the changes.
All mysql* binaries are now named mariadb* (the previous mysql named is retained as a symlink for compatibility purposes)
Not all are across both MySQL and MariaDB. As of 11.0, MariaDB supports 40 character sets and 506 collations . As of 8.0.34, MySQL supports 41 character sets (gb18030 being the additional one - MDEV-7495) and 286 collations.
MariaDB indicates collation pad status as part of the name (e.g. utf8mb3_unicode_nopad_ci), while MySQL indicates pad status by means of an extra column in .
To make CREATE TABLE ... SELECT work the same way in statement based and row based replication it's by default executed as 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 variable to specify how CREATE TABLE and DROP TABLE is replicated.
Users created with MySQL's SHA256 password algorithm cannot be used in MariaDB 11.0 - MDEV-9804.
MariaDB 11.0 does not support Lateral Derived Tables - MDEV-19078.
MariaDB 11.0 does not support CIDR notation for user accounts - MDEV-25515.
MariaDB stores as true text, not in binary format as MySQL. MariaDB's JSON functions are much faster than MySQL's so there is no need to store in binary format, which would add complexity when manipulating JSON objects.
For the same reason, MariaDB's is an alias for . If you want to replicate JSON columns from MySQL to MariaDB, you should store JSON objects in MySQL in a TEXT or LONGTEXT column or use statement-based replication. If you are using JSON columns and want to upgrade to MariaDB, use the plugin to automatically convert MySQL JSON to TEXT, or alternatively you need to either convert them to TEXT or use to copy these tables to MariaDB.
In MySQL, JSON is compared according to json values. In MariaDB JSON strings are normal strings and compared as strings.
MariaDB 11.0 does not support MySQL's JSON operators (-> and ->>) - MDEV-13594
MariaDB 11.0 supports the standard by producing null and a warning for when given invalid data, while MySQL produces an error.
MariaDB never allows authentication via roles, while MySQL permits this.
MySQL permits activating multiple roles at the same time. MariaDB can achieve the same result by creating an intermediate aggregate role.
In the , MySQL reports just the direct list of enabled roles, while MariaDB reports the enabled role, plus the effective inherited roles.
MySQL extends the .
MySQL includes the tables INFORMATION_SCHEMA.ROLE_TABLE_GRANTS, INFORMATION_SCHEMA.ROLE_ROUTINE_GRANTS, INFORMATION_SCHEMA.ROLE_COLUMN_GRANTS, and INFORMATION_SCHEMA ADMINISTRABLE_ROLE_AUTHORIZATIONS.
MySQL has the enabled by default. For performance reasons MariaDB 11.0 has it disabled by default. You can enable it by starting mariadbd with the option --performance-schema.
MariaDB has removed the .
In MariaDB 11.0, using without any table list will only close tables not in use, and tables not locked by the FLUSH TABLES connection. If there are no locked tables, FLUSH TABLES will be instant and will not cause any waits, as it no longer waits for tables in use. When a table list is provided, the server will wait for the end of any transactions that are using the tables. In MySQL, FLUSH TABLES only waits for the statements to complete.
MariaDB binaries (mariadbd, etc.) give a warning if one uses a unique prefix of an option (such as --big-table instead of --big-tables). MySQL binaries require the full option name.
MariaDB 11.0 implements in a different way to MySQL 8.0.
MySQL's implementation of can only kill SELECTs, while MariaDB's can kill any queries (excluding stored procedures).
MariaDB 11.0 does not support MySQL's SELECT /*+ MAX_EXECUTION_TIME(n) */ ... - see Aborting Statements that Exceed a Certain Time to Execute.
MySQL 8.0 does not support the .
MariaDB 11.0 does not support the MySQL Memcached plugin (which has been deprecated in MySQL 8.0). 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.
In MySQL, X'HHHH', the standard SQL syntax for binary string literals, erroneously works in the same way as 0xHHHH, which could work as a number or string depending on the context. In MariaDB, this has been fixed to behave as a string in all contexts (and never as a number). See and for more details and examples.
In MariaDB 11.0, does not quote the DEFAULT value of an integer. MariaDB 10.2 and earlier, and MySQL, do. Since MariaDB can support defaults for and fields, while MySQL does not, will also append DEFAULT NULL where no default is explicitly provided to nullable BLOB or TEXT fields in MariaDB.
As a result of implementing , the has been renamed to VALUE().
MariaDB's supports SELECT statements, LOCK TABLES and various DDL statements, while MySQL's NOWAIT only supports SELECT.
MariaDB's cannot be added on and while MySQL's can - MDEV-25247
MariaDB does not support table while it is write-locked - MDEV-30814
MariaDB returns an ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction when unable to lock within the time, while MySQL returns ERROR 3572 (HY000): Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set
MariaDB does not support the optional init_vector argument for and or the block_encryption_mode variable - MDEV-9069
MariaDB does not support the --initialize option. Use instead. - MDEV-19010
MariaDB 11.0 does not support the ngram and MeCab full-text parser plugins - MDEV-10267, MDEV-10268.
MariaDB 11.0 does not support the MySQL X plugin.
MariaDB 11.0 before MariaDB 11.0.3 does not support MySQL 8's “native” InnoDB partitioning handler - MDEV-29253
MariaDB 11.0 does not support for InnoDB.
The MySQL 8.0 and MariaDB 11.0 table contain slightly different fields.
MariaDB 11.0 client executables allow the connection protocol to be forced by specifying only connection properties on the command-line. See
The MySQL binary log includes the thread_id, while MariaDB's does not - MDEV-7850
The MariaDB syntax supporting Spatial Reference System IDs for spatial data type columns with is not supported by MySQL. MySQL 8 introduced CREATE SPATIAL REFERENCE SYSTEM, which is not supported by MariaDB - MDEV-29953
MariaDB 11.0 does not support the RESTART statement - MDEV-30813
uses a different compression algorithm, and different system variables to manage.
MariaDB 11.0 does not support the SELECT FOR UPDATE and FOR SHARE locks - MDEV-17514