MariaDB versus MySQL - Compatibilité
Contents
MariaDB est un remplacement de MySQL prêt à exécuter
À toutes fins pratiques, MariaDB est un remplacement de la même Version de MySQL (par exemple, MySQL 5.1 -> MariaDB 5.1, MariaDB 5.2 & MariaDB 5.3 sont compatibles. MySQL 5.5 sera compatible avec MariaDB 5.5). Cela veut dire que:
- Les fichiers de données et de définition des tables (.frm) sont compatibles au niveau binaire.
- Tous les APIs clients, les protocoles et les structures sont identiques.
- Tous les noms de fichiers, fichiers binaires, chemins, ports, sockets et etc.... devraient être les mêmes.
- Tous les connecteurs de MySQL (PHP, Perl, Python, Java.NET, MyODBC, Ruby, connecteur MySQL C
etc.) travaillent de la même manière avec MariaDB.
- Il y a quelques installation issues with PHP5 dont il faut tenir compte (il s'agit d'un bug sur la manière utilisé par l'ancien PHP5 pour contrôler la compatibilité de la librairie client).
- Le paquet
mysql-client
fonctionne aussi avec le serveur MariaDB.
Cela veut dire que pour la plupart des cas, vous n'avez qu'a désinstaller MySQL et installer MariaDB pour pouvoir l'utiliser. (Il n'y a pas besoin de convertir les fichiers de données si vous utilisez la même version principale, telle que 5.1).
Tous les mois on fait le merge avec le code de MySQL afin de garder la compatibilité et pour avoir accès à toutes les fonctionnalités et les corrections des bugs développés par Oracle. Nous avons également fait beaucoup de travail sur la mise à niveau des scripts ce qui fait que maintenant il est plus facile upgrade depuis MySQL 5.0 à MariaDB 5.1 que depuis MySQL 5.0 à MySQL 5.1.
MariaDB dispose d'une grande quantité de nouvelles options , extensions, moteurs de stockage et correction de bugs qui n'étaient pas présentes dans MySQL. Vous pouvez trouver les caractéristiques des différentes versions de MariaDB dans la page Qu' y-t-il dans les différentes versions de MariaDB.
Voir aussi MariaDB versus MySQL - caractéristiques.
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 starts with MariaDB instead of MySQL.
- Timings may be different as MariaDB is in many cases faster than MySQL.
- mysqld in MariaDB reads also 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
, theCHECKSUM
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
to1M
(the default is128M
). - 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:
- 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 themysql
database, fix that withmysql_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
- 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 has been moved to start from 1900 to not conflict with MySQL errors.
- Microseconds now works in all contexts; MySQL did, in some contexts, lose the microsecond part from datetime and time.
- 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 extraProgress
column which shows progress for some commands. You can disable it by startingmysqld
with the--old
flag.INFORMATION_SCHEMA.PROCESSLIST
has three new columns for progress reporting:STAGE
,MAX_STAGE
, andPROGRESS
.- 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 withmax_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 theGRANT
option) to-1
to stop users from connecting to the server. The globalmax_user_connections
variable does not affect users with theSUPER
privilege. - The IGNORE directive does not ignore all errors (like fatal errors), only things that are safe to ignore.
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