darx@sent.com - 8:51 19.01.13 wrote:
I can certainly understand the interest in switching to MariaDB -- though personally I'm not at all convinced 12.3 is the right time/place to do so -- but I am concerned about the assumption that "drop in replacement" really is.
That may be a goal, but it most certainly in not 100% true. Starting here, @MariaDB project itslef,
https://kb.askmonty.org/en/mariadb-versus-mysql-compatibility/ http://blog.mariadb.org/mariadb-10-0-and-mysql-5-6/
Yes, there are some differences, otherwise it would be pointless to call it differently. But if you want to hit these, you are having heavily optimized database/application relation and you depend on specific version/configuration of database, so you could hit them anyway, as there are some small incompatibilities even between minor releases.
and recognizing that large projects that use MySQL API/libs/engines (e.g., Drupal, PHP, etc) still recognize/experience differences between MySQL and the main forks, making that assumption has real potential to wreak havoc.
Well, these are using MySQL API, which is the same.
I'd suggest that if a change of distro default is being made to MariaDB, *and* there is an ongoing commitment to offer an official MySQL pkg in the distro, that the pkg namespaces should be completely & clearly separated
They are since 11.3 IIRC
and that -- unless and until 100% compatibility can be guaranteed
That can't be guaranteed even between maintenance updates ;-)
-- a separate devel pkg , libs & includes, be made available.
I was thinking about that, but it would made it more confusing, transitions harder and there would be people in obs building against one and people building against the other one and it will be more messy in general...
I haven't yet thought through the differences between MySQL packaging for a integrated-distro-default-switch, vs. as a standalone server ... if any.
Michal's packages for MySQL56 (which I use ... ), e.g., have been great/stable for ages. These MariaDB changes percolated quietly into server:database repo, and caught me unaware -- causing some breakage.
IIRC it was weird looking library downgrade. btw. MySQL 5.6 is not 100% compatible with MySQL 5.5: http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html
Michal was great about helping in #irc, and the issues were easily fixed, and this announcement is great to see,
but,
I think this switch should be done carefully. True, many users won't notice a difference. Otoh, there's real potential to cause trouble, as well.
Yes, I know, but we are testing them living together for many openSUSE versions so I believe that most of the issues were polished over the years already. -- Michal HRUSECKY SUSE LINUX, s.r.o openSUSE Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org