and why? it is and where it isn't unintentional report it and help to get it fixed, that said from a admin which dozens of MariaDB servers where the datadir was originally created on Windows under MySQL 3.x, got moved in prduction for some years to MacOS, later to Linux and now is running MariaDB 10.1 just fine with the same datadirs and the help of "mysql_upgrade" over the years Am 05.04.2017 um 16:50 schrieb MARK CALLAGHAN:

Maybe someone should edit the too strong claims on https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/

In bold at the top of the page...

MariaDB is a binary drop in replacement for MySQL

On Tue, Apr 4, 2017 at 9:58 PM, Sergei Golubchik <serg@mariadb.org <mailto:serg@mariadb.org>> wrote:

Hi, Mark!

On Apr 04, Mark Callaghan wrote: > With upstream (5.6 and 5.7) MySQL when I use cmake > -DCMAKE_INSTALL_PREFIX=$X, then after I install the build, mysqld searches > in $X/etc for my.cnf. That is not true for MariaDB Server 10.2. Why can't > this match upstream?

It certainly can. It just doesn't. Because we merge from 5.6 into MariaDB feature by feature, and nobody has requested this particular feature so far. At least I couldn't find it in Jira.

Regards, Sergei Chief Architect MariaDB and security@mariadb.org <mailto:security@mariadb.org>

-- Mark Callaghan mdcallag@gmail.com <mailto:mdcallag@gmail.com>

Am 05.04.2017 um 18:57 schrieb MARK CALLAGHAN:

It is different from upstream MySQL in many ways as that page explains.

bla - if it woul dbe just a recompile from the mysql sources it would not be a fork - in 99.9% of all cases IT IS a drop-in-replacement - if you have REAL issues name them - period

On Wed, Apr 5, 2017 at 8:03 AM, Reindl Harald <h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>> wrote:

and why?

it is and where it isn't unintentional report it and help to get it fixed, that said from a admin which dozens of MariaDB servers where the datadir was originally created on Windows under MySQL 3.x, got moved in prduction for some years to MacOS, later to Linux and now is running MariaDB 10.1 just fine with the same datadirs and the help of "mysql_upgrade" over the years

Am 05.04.2017 um 16:50 schrieb MARK CALLAGHAN:

...

Maybe someone should edit the too strong claims on https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/ <https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/>

In bold at the top of the page...

MariaDB is a binary drop in replacement for MySQL

On Tue, Apr 4, 2017 at 9:58 PM, Sergei Golubchik <serg@mariadb.org <mailto:serg@mariadb.org>> wrote:

Hi, Mark!

On Apr 04, Mark Callaghan wrote: > With upstream (5.6 and 5.7) MySQL when I use cmake > -DCMAKE_INSTALL_PREFIX=$X, then after I install the build, mysqld searches > in $X/etc for my.cnf. That is not true for MariaDB Server 10.2. Why can't > this match upstream?

It certainly can. It just doesn't. Because we merge from 5.6 into MariaDB feature by feature, and nobody has requested this particular feature so far. At least I couldn't find it in Jira.

Regards, Sergei Chief Architect MariaDB and security@mariadb.org <mailto:security@mariadb.org>

Am 05.04.2017 um 19:14 schrieb MARK CALLAGHAN:

Why do you need to shout about this?

why don't you bring ANY specific reasoining for your sloppy "Maybe someone should edit the too strong claims" - anyways - if someone is too dumb to respond just to the list instead reply-all and convert plaintext mails in the quote to HTML all is said....

On Wed, Apr 5, 2017 at 10:04 AM, Reindl Harald <h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>> wrote:

Am 05.04.2017 um 18:57 schrieb MARK CALLAGHAN:

It is different from upstream MySQL in many ways as that page explains.

bla - if it woul dbe just a recompile from the mysql sources it would not be a fork - in 99.9% of all cases IT IS a drop-in-replacement - if you have REAL issues name them - period

On Wed, Apr 5, 2017 at 8:03 AM, Reindl Harald <h.reindl@thelounge.net <mailto:h.reindl@thelounge.net> <mailto:h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>>> wrote:

and why?

it is and where it isn't unintentional report it and help to get it fixed, that said from a admin which dozens of MariaDB servers where the datadir was originally created on Windows under MySQL 3.x, got moved in prduction for some years to MacOS, later to Linux and now is running MariaDB 10.1 just fine with the same datadirs and the help of "mysql_upgrade" over the years

Am 05.04.2017 um 16:50 schrieb MARK CALLAGHAN:

Maybe someone should edit the too strong claims on https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/ <https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/>

<https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/ <https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/>>

In bold at the top of the page...

MariaDB is a binary drop in replacement for MySQL

On Tue, Apr 4, 2017 at 9:58 PM, Sergei Golubchik <serg@mariadb.org <mailto:serg@mariadb.org> <mailto:serg@mariadb.org <mailto:serg@mariadb.org>>> wrote:

Hi, Mark!

On Apr 04, Mark Callaghan wrote: > With upstream (5.6 and 5.7) MySQL when I use cmake > -DCMAKE_INSTALL_PREFIX=$X, then after I install the build, mysqld searches > in $X/etc for my.cnf. That is not true for MariaDB Server 10.2. Why can't > this match upstream?

It certainly can. It just doesn't. Because we merge from 5.6 into MariaDB feature by feature, and nobody has requested this particular feature so far. At least I couldn't find it in Jira.

Regards, Sergei Chief Architect MariaDB and security@mariadb.org <mailto:security@mariadb.org> <mailto:security@mariadb.org <mailto:security@mariadb.org>>