Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL)
-
None
Description
We need to define to which extent MariaDB 10.2 should be compatible with MySQL 5.7.
For MariaDB 10.0/10.1 the major obstacle is MDEV-9904 (closed as "Won't fix").
For MariaDB 10.2, it is not a problem after InnoDB 5.7 has been merged; but it still can't start on MySQL 5.7 datadir due to MDEV-11170.
I expect there will be other issues, so this entry will be an umbrella bug until we are satisfied with the level of compatibility we provide.
Not supported in 10.2
This section will contain random features, syntax and options that I encounter during testing as not supported in 10.2, while supported in MySQL 5.7.
It is not intended to be a full list!
CREATE USER ... PASSWORD EXPIRE ... (see MDEV-7597)
CREATE USER ... ACCOUNT [UN]LOCK
CREATE USER ... IDENTIFIED WITH ... BY ... (see MDEV-11180)
Attachments
Issue Links
- includes
-
MDEV-10346 Create bind-address as a system variable
- Closed
-
MDEV-13117 mysqldump to support --skip-definer
- Open
- is blocked by
-
MDEV-6113 merge 5.7 innodb
- Closed
-
MDEV-11170 MariaDB 10.2 cannot start on MySQL 5.7 datadir: Fatal error: mysql.user table is damaged or in unsupported 3.20 format
- Closed