Following compatibility report was done on 10.2.4 and may get some fixing in next minor releases

• MySQL unix socket plugin can be different. MariaDB can get similar usage via INSTALL PLUGIN unix_socket SONAME 'auth_socket.so'; you may have to enable this plugin in config files via load plugin.

• When using data type JSON , one should convert type to TEXT, virtual generated column works the same after.

• When using InnoDB FULLTEXT index one should not use innodb_defragment

• MySQL re-implemented partitioning in 5.7, thus you cannot perform in-place upgrades for partitioned tables. They will require mysqldump/import to work correctly in MariaDB.

_{This page is licensed: CC BY-SA / Gnu FDL}

If you upgrade to from MySQL 5.1 you don't have to do anything with your data or MySQL clients. Things should "just work".

When upgrading between different major versions of MariaDB or MySQL you need to run the mysql_upgrade program to convert data that are incompatible between versions. This will also update your privilege tables in the mysql database to the latest format.

In almost all cases mysql_upgrade should be able to convert your tables, without you having to dump and restore your data.

After installing MariaDB, just do:

If you want to run with a specific TCP/IP port do:

If you want to connect with a socket do:

To see other options, use --help.

"mysql_upgrade" reads the my.cnf sections [mysql_upgrade] and [client] for default values.

There are a variety of reasons tables need to be converted; they could be any of the following:

• The collation (sorting order) for an index column has changed

• A field type has changed storage format

  • and changed format between MySQL 4.1 and MySQL 5.0

• An engine has a new storage format

in SHOW TABLES until you convert them.

If you don't convert the tables, one of the following things may happen:

• You will get warnings in the error log every time you access a table with an invalid (old) file name.

• When searching on key values you may not find all rows

• You will get an error "ERROR 1459 (HY000): Table upgrade required" when accessing the table.

• You may get crashes

"mysql_upgrade" works by calling mysqlcheck with different options and running the "mysql_fix_privileges" script. If you have trouble with "mysql_upgrade", you can run these commands separately to get more information of what is going on.

Most of the things in the section also applies to MariaDB.

The following differences exists between "mysql_upgrade" in MariaDB and MySQL (as of ):

• MariaDB will convert long table names properly.

• MariaDB will convert tables (no need to do a dump/restore or ).

• MariaDB will convert old archive tables to the new 5.1 format (note: new feature in testing).

• "mysql_upgrade --verbose" will run "mysqlcheck --verbose" so that you get more information of what is happening.

_{This page is licensed: CC BY-SA / Gnu FDL}

There is a for upgrading from MySQL 5.1.55 to MariaDB. Watch this example to see how easy this process is. It really is just a "drop in replacement" to MySQL.

_{This page is licensed: CC BY-SA / Gnu FDL}