Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Databases Open Source Oracle Sun Microsystems

MySQL's Creator On Why the Future Belongs To MariaDB 208

angry tapir writes "When Oracle purchased Sun, many in the open source community were bleak about the future of MySQL. According to MySQL co-creator Michael "Monty" Widenius, these fears have been proven by Oracle's attitude to MySQL and its community. In the wake of the Sun takeover, Monty forked MySQL to create MariaDB, which has picked up momentum (being included by default in Fedora, Open SUSE and, most recently, Slackware). I recently interviewed Monty about what he learned from the MySQL experience and the current state of MariaDB."
This discussion has been archived. No new comments can be posted.

MySQL's Creator On Why the Future Belongs To MariaDB

Comments Filter:
  • by SJHillman ( 1966756 ) on Thursday March 28, 2013 @08:29AM (#43301723)

    Because JesusDB would drop tables for your sins. Perhaps NoahDB would be better. Built-in disaster recovery - it saves just enough data to replicate everything after the disaster is over.

  • by Anonymous Coward on Thursday March 28, 2013 @08:38AM (#43301769)

    NoahDB is not bad, a duplicate record of each kind.

    How about JewDB though? You know it has to be good with business transactions. You definitely don't want a AlQaidaDB, it'll blow up ever so often and the DHS will be on your ass at all times.

  • Re:Me, too! (Score:3, Funny)

    by Anonymous Coward on Thursday March 28, 2013 @09:10AM (#43302045)

    PostgreSQL date handler error?

  • Re:Me, too! (Score:5, Funny)

    by Waffle Iron ( 339739 ) on Thursday March 28, 2013 @11:48AM (#43303571)

    Because everyone in the open source community has this insufferable "Me, too!" attitude, resulting in half a dozen needlessly duplicative efforts.

    That's right. Open source developers should take a cue from the commercial database market: The vendors like IBM, Microsoft and Oracle don't waste resources on duplicate efforts, but instead they collaborate on the one single commercial SQL database engine available on the market today.

I've noticed several design suggestions in your code.

Working...