Slashdot Mirror
Fedora 19 Nixing MySQL in Favor of MariaDB
An anonymous reader writes "Red Hat developers are planning to replace MySQL with MariaDB in Fedora 19. For the next Fedora update, the MariaDB fork would replace MySQL and the official MySQL package would be discontinued after some time. The reasoning for this move is the uncertainty about Oracle's support of MySQL as an open-source project and moves to make the database more closed." Update: 01/22 13:47 GMT by T : Note: "Nixing" may be a bit strong; this move has been proposed, but is not yet officially decided.
Probably most important to Fedora is this:
Wikipedia, too, is moving from MySQL to MariaDB.
Just use it.
We've begun to move away from MySQL offical release also. Although we went with Percona rather than MariaDB.
The point of the move is to replace MySQL, not to have some killer database.
And for those of us who are tied to MySQL, it's nice to have an alternative now without the hassle of moving to a completely different DBM.
How easy is it to migrate from MySQL to MariaDB?
Is it truely drop-in replacement as in "you can develop to MySQL, then run MariaDB in production without worrying"?
Does it require converting current tables? Will it take a 10GB database all day to convert or will MariaDB just use the raw MySQL data files automagically?
Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
That is one thing I always loved about Open Source Software, you can't hold it hostage. If something happens to threaten the project, its fork you, and bye bye!
The users and developers take what was there (and theirs) pack up and resume life a usual somewhere else, and give the finger to all the Larrys that come along and try to (ab)use them as part of their own personal plot.
If you take care of them they will stay, and you might even see your user and developer base grow, but try and take advantage of them and you will soon be left with nothing. They take the short term pain of starting over instead of the long term pain of taking orders from someone who does not have their best interests in mind.
Cheers!
Eh, fuck 'em both.
Larry Ellison responded with the comment, "you are all spelling it wrong, I renamed it MY sql some time ago."
Just move to PostgreSQL and be done with it?
Zoid.com
I think this is not good news for developer and users who use open source Red Hat.Some people don't know how to use this latest DB because MySQL is mostly use as DB in all leading Programming language..... http://tiny.cc/qbgbrw
Just looked at Percona.
While it is open-source. it has a profit-making arm. This can change with the stroke of a pen. There is enough "sales talk" to make me wary.
MariaDB has no such constraints. Its developers embrace the open-source concepts. Its team is made up of MySQL's developers, one of whom developed MySQL. One can only guess at the reason they split from MySQL. I would prefer to believe that it's not because of Oracle's business philosophy and practices with its other products, its ownership of many database programs, its upper management, or its litigiousness.
Every vendor wants their own proprietary extenstions, and even fight each other on who gets the most proprietary lockin, apis, and extensions on top of their own SQL to maximize pain leaving their shit ecosystem. ADO.NET, ODBC, and other things where you can't just use sql, but another vendor $$$ framework that locks you in further and add dozens of lines of ugly code and before you add another proprietary layer of Vendor X SQL inside it.
Then gee you can't leave it. Larry grins and then raises the cost knowing you are hostage etc (dramatization here).
HTML and CSS was that way in the 1990s as well. We bash IE 6 here but Netscape didn't follow standards either. Today that is fixed.Why can't we do that with data access?
What will it take for all of them to work together like ansi ascii text, C++, or HTML?
I admit Oracle and SQL Server will be a bitch to get rid of in the enterprise due to these sneaky moves, but slowly change will come when PostgresSQL, MariaDB, and others who want to play nice come up with one standard, one way to do things, and get oustracized here on slashdot as crap if they do not follow the spec? This is 2013 and these proprietary games are oldschool before the internet when corps were in a pissing match on who could make the most crappiest proprietary system out there so customers could never leave... cough unix.
http://saveie6.com/
Why is *any* database a part of an OS? This isn't required functionality. It isn't even day-to-day useful as a browser, or a word processor.
After installing the base OS, a distro can offer to optionally install packages - such as a database - but I don't see why that choice should be limited to just one example. Make both MySQL and MariaDB available, and any others you want.
Tehe, mariadb.org no workie.
Bad reporting by Phoronix here. The feature has been proposed, but it has not yet been voted on by the Fedora Engineering Steering Committee (FESCo). It may or may not be approved for Fedora 19. I don't want to speak for Jaroslav Reznik, but he doesn't necessarily support the proposal. As the Fedora Program Manager, it's part of his job to post these proposed features to the mailing list for discussion prior to the FESCo vote.
MariaDB is Monty Widenius' fork after leaving Oracle. MySQL is in Oracle's hands in the first place because Widenius sold MySQL to Sun. The man responsible for MySQL is also responsible for the fragmentation of the community into a bunch of forks with growing incompatibility problems.
Anyone who loves or hates any language, platform, or manufacturer, doesn't know what they're talking about.
If this gets taken far enough, and MariaDB replaces MySQL elsewhere, at least we won't have to change the way we spell LAMP.
I use mariadb in a production situation and actually regret the move from mysql. Mariadb is cool or at least as "cool" as any mysql variant can be (bias: I'm from a postgresql background and tend to choose that for any personal project). But it has some stability problems that I didn't have with mysql. I know how to crash any mariadb server (though it'll just restart) with a handful of queries (provided I have table creation rights), and yes, I filed a bug report. Over 6 months ago. (I also have some situations where maria fucks up (and mysql didn't) but it involves some data that I was never able to distill down to a small recreatable test case.) Mariadb is "over-optimized." Don't use it.
I wrote a .NET application back in 2004 that used ADO.NET to interface with a MySQL database. It was quite painful to code compared to just using MS SQL. Once I got the connector working (it wasn't a mature product at the time), the final application worked pretty well.
And really, Debian's big selling point is their "stable" branch. They're famous for being slower to change things than other distros (which increasingly seems like a big advantage to me, in a world where everyone thinks they have a right to broadcast UI changes to you at the designer's whim).
Anyway, while the threat from Oracle taking over MySQL has always been obvious, I don't think the other shoe has ever really dropped, has it? A situation to keep an eye on, but not necessarily any need to act quickly.
Part of the problem is that ANSI SQL is fairly unfeatured. That's why everybody adds to it.
ANSI SQL really needs some official extensions so that much of the proprietary nonsense can go away.
Fedora should first get all memory leaks sorted out in Fedora 18. Instead of going forward with experimental broken shit, they should make things become reliable and stable.
Nice move. I find MariaDB better than MySQL in any way. Small things like statistics, user prompt makes it more user friendly. Performance is better. With big data set you don't need benchmark, you can see it. Replacement of MyISAM with crash safe Aria engine, for those who think MyISAM is quicker. nicely optimized Percona-XtraDB replacement of InnoDB engine. Build in Sphinx. better replication performance. some extra information in the binary and slow logs. Plenty of new features coming in next MariaDB 10 release like multi-source replication and full text search in InnoDB engine. When I joined our company, the first thing I did replaced all MySQL 5.0 - 5.1 databases with MariaDB 5.5. The process of migrating is painless. few things to remember: pay attention to my.cnf file. better use MariaDB template and put what ever needs in it. move origial my.cnf out of the way. The same about mysql.d config folders.
I think this will be a good thing. This is for similar reasons that Fedora also chose LibreOffice over OpenOffice. Fedora continues to be an open distribution and I trust their judgement on which products they choose to include with the distribution.