Some distros dropping Mysql for MariaDB

[Red Squirrel]

Never heard of MariaDB but I'll have to check it out. Looks like it's a fork of MySQL.

While this may be tough as lot of apps may rely on MySQL, I think it's a good move as MySQL being owned by a big company, could vanish any time. It's not the GPL that will stop a megacorporation from doing a decision that renders it no longer free. So may as well get ahead of the curve and have an alternative now, and eventually break away from needing MySQL. Of course, it will take a while for stuff like forum software etc to be coded to support it.

http://www.h-online.com/open/news/item/Slackware-Linux-switches-to-MariaDB-1829261.html

https://www.archlinux.org/news/mariadb-replaces-mysql-in-repositories/


I don't know if outright replacing MySQL with it is the best course of action though, there should still be an option to get MySQL.

 

[Demo24]

We almost did this when we did a massive version upgrade to 5.5 ,which for awhile created some data corruption. Most of that seemed to be related to innodb vs myisam changes. Maria is more or less a direct drop in for mysql, which is to be expected since it came from some of the more original developers. We never did use it though as it wasnt in Ubuntu repositories, so no idea how well it works.

 

[sourceninja]

Never heard of MariaDB but I'll have to check it out. Looks like it's a fork of MySQL.

While this may be tough as lot of apps may rely on MySQL, I think it's a good move as MySQL being owned by a big company, could vanish any time. It's not the GPL that will stop a megacorporation from doing a decision that renders it no longer free. So may as well get ahead of the curve and have an alternative now, and eventually break away from needing MySQL. Of course, it will take a while for stuff like forum software etc to be coded to support it.

http://www.h-online.com/open/news/item/Slackware-Linux-switches-to-MariaDB-1829261.html

https://www.archlinux.org/news/mariadb-replaces-mysql-in-repositories/


I don't know if outright replacing MySQL with it is the best course of action though, there should still be an option to get MySQL.

It really doesn't matter which one you use. The guy who founded mysql forked it (after selling out) to make make maria. So it's still the mysql you love, just not owned by oracle.

It's like if debian sold out to microsoft then forked debian into freddy linux.

Finally, you can always get mysql from oracle if it's that big of a deal.

 

[Stone Rain]

I've never used Maria, but if there's no real changes in how the distro operates at the user end, then whatever, I suppose.

 

[Broheim]

It really doesn't matter which one you use. The guy who founded mysql forked it (after selling out) to make make maria. So it's still the mysql you love, just not owned by oracle.

It's like if debian sold out to microsoft then forked debian into freddy linux.

Finally, you can always get mysql from oracle if it's that big of a deal.

:hmm: that does not compute

 

[Red Squirrel]

It really doesn't matter which one you use. The guy who founded mysql forked it (after selling out) to make make maria. So it's still the mysql you love, just not owned by oracle.

It's like if debian sold out to microsoft then forked debian into freddy linux.

Finally, you can always get mysql from oracle if it's that big of a deal.

Yeah but still need to use whatever plugins etc that are made for it otherwise it wont find it. Kinda like when a program requires apache2 but you have httpd installed. They're both the same program but the names are different.

Of course this wont really be a huge deal and it's nice to see that we wont have to depend on a commercial product anymore, if this catches on all distros, and software.

 

[bobross419]

There are ways around package naming issues. Compiling from source and throwing soft links at it usually work pretty well.

Realistically though, a migration shouldn't be a major issue. If you are doing things right and testing in a dev environment before moving into prod, you'll find most compatibility issues before hand.

With that said, I'd be more concerned with the under the hood kind of stuff that might affect how certain queries are run and how some of the things like bin logging/replication function. I haven't looked at change logs or anything, but compatibility issues at that level would be more difficult to resolve (requiring code changes at the least).