Follow Slashdot stories on Twitter


Forgot your password?
Databases Open Source Oracle Sun Microsystems

Why You Shouldn't Panic About Closed Source MySQL Extensions 171

jfruhlinger writes "Oracle has released proprietary extensions to the open source MySQL database, seeming to reinforce the worst fears of those in the open source community who opposed Oracle's acquisition of MySQL in the first place. But open source observer Brian Proffitt urges you not to panic: This dual source strategy really isn't unusual in the commercial open source world, Oracle has already released a bevy of open source improvements to the database, and anyway the EU extracted a commitment to keep MySQL open for another four years when it approved the Sun-Oracle merger."
This discussion has been archived. No new comments can be posted.

Why You Shouldn't Panic About Closed Source MySQL Extensions

Comments Filter:
  • by Anonymous Coward on Tuesday September 20, 2011 @04:23AM (#37453784)

    Its already forked :)

  • because (Score:3, Informative)

    by roman_mir ( 125474 ) on Tuesday September 20, 2011 @04:24AM (#37453786) Homepage Journal

    because of postgresql?

  • Re:Migration Window (Score:4, Informative)

    by GPLHost-Thomas ( 1330431 ) on Tuesday September 20, 2011 @05:18AM (#37453972)
    Wake up. MariaDB has been around for some time already!
  • by hholzgra ( 6914 ) on Tuesday September 20, 2011 @05:46AM (#37454080) Homepage

    As if PostgreSQL didn't have it's own ecosystem of commercial-only extensions, too (EnterpriseDB, GreenPlum, just to name a few) ... the big difference here is that in the MySQL ecosystem Oracle is the only one that can do such dual-license stunts while in the PostgreSQL ecosystem anybody can ... (whether that's good or bad is a different story)

    For "improvements"/"what's been added":

    * lots of multi CPU scalability work (although part of it came from Google/Facebook and other sources where Sun/Oracle 'just' did the integration work)
    * MySQL Cluster got a *lot* better in Sun/Oracle days
    * the InnoDB plugin improved InnoDB affairs a lot (and this has been Oracles baby even in the Sun days)
    * connectors, e.g. PHP/mysqlnd
    * more interesting InnoDB improvements (e.g. fulltext indexes, finally) are in the queue, how these are going to be licensed remains to be seen though

    It's not that everything is going into the optimal direction with MySQL under Oracle (i'm not working for them anymore for a reason), but saying there has been no development ever since the Sun acquisition is not fair, and i don't see any reason to believe that things will radically change on day 1462 either ...

  • by buchner.johannes ( 1139593 ) on Tuesday September 20, 2011 @06:02AM (#37454140) Homepage Journal

    Migrating from MySQL to PG may be easy, but migrating from MySQL to MariaDB is trivial.

  • by Dark$ide ( 732508 ) on Tuesday September 20, 2011 @06:49AM (#37454340) Journal

    Its already forked :) []

    And to []

  • Re:Migration Window (Score:4, Informative)

    by GPLHost-Thomas ( 1330431 ) on Tuesday September 20, 2011 @09:49AM (#37455898)

    What features will be added to MySQL that MariaDB doesn't have?

    Oh, maybe you meant "what killer features that have been already in MariaDB are still not in MySQL"? Yeaaarh, I'm sure you made a mistake. In this case...

    Ever wonder why MySQL is still stuck with a single core taking 100% of your CPU, while other cores are idling doing nothing? MariaDB, and it's been more than a year it does, had multi-threading. If you didn't know, it's been written by one of the main authors of MySQL in the first place, that felt he shouldn't stay in this Oracle world. And he's doing very well, by himself... The good thing: MariaDB is ABI compatible. Yes, it's a pure replacement. Remove MySQL, install MariaDB instead, and there you go, you got a multi-threaded MySQL. That alone is enough to convince any decent admin.

"The fundamental principle of science, the definition almost, is this: the sole test of the validity of any idea is experiment." -- Richard P. Feynman