Incompatibilities and Feature Differences Between MariaDB 10.2 and MySQL 5.7
You are viewing an old version of this article. View
the current version here.
This article is currently incomplete.
The following is a list of incompatibilities and feature differences between MariaDB 10.2 and MySQL 5.7
- For a list of functions differences, see Function Differences Between MariaDB 10.2 and MySQL 5.7
- For a list of system variable differences, see System Variable 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. 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 JSON data type is an alias for LONGTEXT.
- MariaDB 10.2 does not support MySQL's JSON operators (
->
and->>
). - 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.
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.