[debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

[Otto Kekäläinen]

2016-01-26 10:49 GMT+02:00 Stephan Seitz <stse+debian at fsing.rootsland.net>:
> On Tue, Jan 26, 2016 at 12:48:23AM +0000, Steven Chamberlain wrote:
>>
>> Assuming MariaDB is affected by the same issues, I may not be in a
>> technically better situation if I switched to using that.  (Although, it
>
>
> But as far as I understand it there is no guarantee that MySQL and MariaDB
> will stay compatible in the future.
>
> So what are you doing if MySQL is removed and other programs (e.g. cacti)
> are not working with MariaDB anymore?

Oracle people can fill in if I have the wrong info, but I think that
it is mostly Oracle MySQL that does not track MariaDB changes, while
the other way happens and at least MariaDB will be compatible with
MySQL for the forseeable future and migrating from MySQL to MariaDB
will work.

Also, I've read that Oracle has dropped some of the older code
(probably mostly a well justified clean-up) and therefore for example
5.6 and 5.7 are not fully backwards compatible, and some apps might
need to change to accomodate for changes. So Oracle MySQL is in this
sense not always "compatible" with itself either.

This compatiblity discussion is not very practical, its just corner
cases. For example for all Cacti or WordPress users any version fo
MySQL and MariaDB will most likely work just fine in the foreseeable
future.