15

When using MySQL Workbench 6.3 on Kubuntu 15.10 and MariaDB Server version: 10.0.22-MariaDB-0ubuntu0.15.10.1 (Ubuntu), I get the following warning.

Is this expected?

Incompatible/nonstandard server version or connection protocol detected (10.0.22).

A connection to this database can be established but some MySQL Workbench features may not work properly since the database is not fully compatible with the supported versions of MySQL.

MySQL Workbench is developed and tested for MySQL Server versions 5.1, 5.5, 5.6 and 5.7

Succcessfully made the mysql connection

Information related to this connection:

Host: localhost Port: 0 User: serg SSL: not enabled

A successful MySQL connection was made with the parameters defined for this connection.

Improve this question
3
  • It does make sense that Oracle doesn't bother supporting a fork competing with their product... But the warning says that already...
    – Gert van den Berg
    Commented Dec 30, 2015 at 5:21
  • There has been several requests to provide an option to disable the message: bugs.mysql.com/bug.php?id=83369
    – CrazyTim
    Commented Mar 1, 2018 at 22:16
  • Workbench 8.0.12 and later have an option to disable this message when it pops up. Although that version seems to work on Gnome, it sadly crashes Unity on Ubuntu (bugs.mysql.com/bug.php?id=91967).
    – smhg
    Commented Sep 26, 2018 at 8:22

1 Answer 1

Reset to default
17

TL;DR
Yes this is expected, because MySQL Workbench is an Oracle product and it does not officially support MariaDB which is actually a MySQL competitor. Workbench is warning you about potential incompatibilities, not necessarily detected ones. In most cases, it can be safely ignored.

Details

The MariaDB knowledge-base article on MySQL compatibility describes the relationship best (emphasis mine):

For all practical purposes, MariaDB is a binary drop in replacement of the same MySQL version (for example MySQL 5.1 -> MariaDB 5.1, MariaDB 5.2 & MariaDB 5.3 are compatible. MySQL 5.5 is compatible with MariaDB 5.5 and also in practice with MariaDB 10.0). What this means is that:

  • Data and table definition files (.frm) files are binary compatible.
    • See note below for an incompatibility with views!
  • All client APIs, protocols and structs are identical. All filenames, binaries, paths, ports, sockets, and etc... should be the same.
  • All MySQL connectors (PHP, Perl, Python, Java, .NET, MyODBC, Ruby, MySQL C connector etc) work unchanged with MariaDB.
    • There are some installation issues with PHP5 that you should be aware of (a bug in how the old PHP5 client checks library compatibility).
  • The mysql-client package also works with MariaDB server.
  • The shared client library is binary compatible with MySQL's client library.

This means that for most cases, you can just uninstall MySQL and install MariaDB and you are good to go. (No need to convert any datafiles if you use same main version, like 5.1). You must however still run mysql_upgrade to finish the upgrade. This is needed to ensure that your mysql privilege and event tables are updated with the new fields MariaDB uses.

We do monthly merges with the MySQL code base to ensure we keep up our compatibility and get any and all features and bug fixes Oracle adds.

All that being said, there are some incompatibilities that may or may not affect you. The linked KB article has a section on known incompatibilities between different versions of MySQL and MariaDB. Refer to the section for your MariaDB version for notes that may affect you.

Improve this answer
1
  • For reference, the compatibility list continues as: MySQL 5.6 <==> MariaDB 10.1, MySQL 5.7 <==> MariaDB 10.2, MySQL 8.0 <==> MariaDB 10.3. These are not exact equivalencies, of course, and there is some overlap, but it's a pretty close guideline.
    – SherylHohman
    Commented Jun 24, 2019 at 19:09

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .