rc3.org Rafe Colburn on software development (and other topics)

The inevitable MySQL fork

In Commentary on 14 May 2009 tagged , , with 2 comments

MySQL is near and dear to my heart — I use it for just about every project I work on. And like many people, Oracle’s acquisition of Sun leads me to worry about MySQL’s future. However, I’m not sure that the new MySQL fork from Percona and Monty Program Ab will lead us to the promised land.

What scares me most is that the new database will not support InnoDB. That makes sense, because InnoDB was already an Oracle property even before the Sun acquisition, but moving away from it will be scary for many users. Time to figure out whether Primebase XT is ready for prime time, I suppose.

Update (May 20): MariaDB will support InnoDB. See the comments.


2 Comments

…there’s always Postgresql.

You know, mature support for triggers, stored procs, tranactions and even ACID compliance (no more silent truncation!); stuff like that.

It’s fast, too.

Posted by bryan on 18 May 2009 @ 11am

MariaDB does support InnoDB. In fact, we use an optimized branch of InnoDB called XtraDB from Percona which means that you already in the MariaDB 5.1 release get most of the engine performance that MySQL promises in 5.4.

And of course, MariaDB, as MySQL, is fully ACID, transactional and has stored procedures since many years ago

Posted by Michael Widenius on 19 May 2009 @ 7pm

Leave a Comment

← →

About

This is the weblog of Rafe Colburn. I'm a software developer and computer book author, but this blog is really about whatever catches my interest on a day to day basis. I've been blogging since December, 1998.

Recently

Visit the full archive

Et Cetera

You can follow @rc3dotorg on Twitter here. My personal Twitter account is @rafeco. If you know what an RSS feed is, you can subscribe to the rc3.org feed here.


← Back to Home

© rc3.org. Powered by WordPress using the DePo Skinny Theme.