Slashdot Mirror


Mickos Urges EU To Approve Oracle's MySQL Takeover

mjasay writes "Former MySQL CEO Marten Mickos has written to EU Commissioner of Competition Neelie Kroes to urge speedy approval of Oracle's proposed purchase of Sun, including the open-source MySQL database. The EU has been worried that Oracle's acquisition of Sun could end up hurting competition by dampening or killing MySQL's momentum. But in his letter, Mickos separates MySQL-the-community from MySQL-the-company, arguing that Oracle's takeover cannot hurt the MySQL community: 'Those two meanings of the term "MySQL" stand in a close, mutually beneficial interaction with each other. But, most importantly, this interaction is voluntary and cannot be directly controlled by the vendor.' In a follow-up interview with CNET, Mickos indicated that he has no financial interest in the matter, but instead argues he 'couldn't live with the fact that [he's] not taking action,' and is 'motivated now by trying to help the employees still at MySQL and Sun, and by an urge to bring rational discussion to the matter.'"

16 of 67 comments (clear)

  1. Good! by Futurepower(R) · · Score: 4, Insightful

    I'm happy he is taking action.

    Too often, technically-knowledgeable people don't recognize or accept the need for them to be social leaders.

  2. Alternatives by Anonymous Coward · · Score: 3, Interesting

    if they mess MySql up(even more that is), people can just move to Postgre, Firebird, Couchdb, Drizzle, etc.. There's anything but a shortage of open-source databases.

    1. Re:Alternatives by jadavis · · Score: 4, Insightful

      Moving from one database system to another is no trivial matter, even if that other system is a fork.

      I agree with Marten Mickos here. There's no benefit to dragging this process out. If Oracle owning MySQL would be a problem, the time to fix it was months ago (I realize that may have been impossible); leaving it in extended purgatory is worse. MySQL has some degree of protection by using the GPL license, anyway.

      Disclaimer: I'm a PostgreSQL user, and I haven't used MySQL for a while.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    2. Re:Alternatives by Zontar+The+Mindless · · Score: 2, Informative

      They have already killed mysql 6.0 "MySQL 6.0 was not developed beyond Alpha status and new releases have not been made for some time, so the manual has been withdrawn as well."

      http://dev.mysql.com/doc/refman/6.0/en/index.html

      Wrong. We have NOT 'killed' 6.0, but it not going to be the focus of our development for a while, and we won't do any more official 6.0 releases for some time to come. But we HAVE moved it to the back burner, so to speak.

      If you really want 6.0, you can get it right here:

      https://code.launchpad.net/~mysql/mysql-server/mysql-6.0-codebase

      No guarantees right now as to how well it'll build and run on any given day; I think I last built it last Tuesday or Wednesday, and it seemed to do okay, but of course YMMV. That being said, go get the code and knock yourself out.

      In the meantime, we're backporting what we think are the best bits of 6.0 to 5.X.

      so what is next ?

      You'll find some answers to that question here...

      http://dev.mysql.com/doc/refman/5.1/en/mysql-next-series-plans.html

      And here...

      http://dev.mysql.com/doc/refman/5.4/en/

      And what's this? The latest release, from less than a week ago:

      http://dev.mysql.com/doc/refman/5.4/en/news-5-4-3.html

      That's the clone-off date, BTW. Binaries should be available here

      http://dev.mysql.com/downloads/mysql/5.4.html

      in a few days.

      5.x on the death row

      I think that's a bit of a stretch. Why don't you see what we say about it on the site?

      http://www.mysql.com/about/legal/lifecycle/

      NB: We have a choice between (a) honouring the policies on this page and (b) breaking contacts with paying customers.

      Can you guess which of these we're more likely to do?

      maybe is time to move to postgresql , firebird ...

      That's one of the reasons why it's called Free Software -- you're absolutely free to move to something else if you like, and we wish you every success with it if you choose to do so.

      --
      Il n'y a pas de Planet B.
  3. Fork it by Ghubi · · Score: 2, Insightful

    It's not that easy to kill an open source project.

    1. Re:Fork it by Z00L00K · · Score: 5, Informative

      There is already a fork: MariaDB by Monty, one of the MySQL founders.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    2. Re:Fork it by jadavis · · Score: 4, Interesting

      It's not that easy to kill an open source project.

      It takes a long time to put together a real community; it doesn't happen overnight. However, dismantling one can happen overnight, and that may be what has taken place already.

      There is a promising amount of development, excitement, and support behind some of the forks like Drizzle and MariaDB. But losing a development team and then trying to reassemble it somewhere else is going to be a serious setback, and it will fracture the community.

      When the forks start to diverge there will be even more problems. Application developers will pick fork X, and then people will start asking in the mailing lists "I am having a problem and I am using fork Y". Whether or not the difference between X and Y is causing the problem is not important -- what's important is that it will take effort for the application developers to figure it out.

      The "open source can't be killed" idea is great in theory, but in practice it takes more than a license. It takes a real community effort, and requires real leadership, full-time people, a consistent message, and they have to be able to deliver a product, not a stream of patches. These challenges are all magnified for a database system, where it's hard to find those critical few developers that you can rely on, and the need for quantized releases is greater (to avoid the pain of data migration).

      All that being said: I think MySQL can pull itself together. But it takes a lot of work, and the thinking that "open source can't be killed" is a sure-fire way to make sure the necessary work is not done, and that will lead to the death of the project.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    3. Re:Fork it by Anonymous Coward · · Score: 5, Informative

      "The name MySQL (just like the MyISAM storage engine) comes from Monty's first daughter "My". MariaDB continues this tradition by being named after his younger daughter. "

  4. Let them by Norsefire · · Score: 2, Informative

    I use MySQL exclusively and it would nice if Oracle were given a shot at supporting MySQL. Even if they do try and kill it to gain leverage for their own database, there's always MariaDB (a MySQL fork by Monty Widenius, the original creator of MySQL).

    1. Re:Let them by lordandmaker · · Score: 3, Insightful

      The problem is that there's also all sorts of other forks, each with their own claim to being the first heir to MySQL.

      Were Oracle to kill of MySQL and there to be One True Fork that everyone switches to, that'd be fine. But there isn't. There're several, and they seem to be multiplying.

  5. Good news for PostgreSQL by ZipK · · Score: 3, Interesting

    Even the threat of Oracle owning MySQL is motivating commercial users to look more closely at the BSD-licensed PostgreSQL. If the sale goes forward, it may the biggest boost yet to the PostgreSQL community.

  6. what competition? by mcover · · Score: 2, Informative

    I don't see why the EU is worried in the first place. First of all MySQL could never compete with Oracle's DB. They will never compete and never have. Completely different use-cases. Apart from that, I'm still using PostgreSQL and if i had an app specifically designed for MySQL, I'd go with Drizzle(fork).

    1. Re:what competition? by jadavis · · Score: 2, Insightful

      Completely different use-cases.

      There's some truth to that, but that's hyperbole. The use cases are not disjoint.

      Additionally, MySQL may represent a general shift away from the traditional SQL architecture towards things like MySQL and non-SQL database systems. In some sense, Oracle is not just fighting to keep its customers on Oracle, it's trying to keep customers using traditional SQL systems.

      I happen to think that the traditional SQL architecture is a pretty good one, and much better for general purpose development than the alternatives. But some people disagree, and Oracle doesn't want to lose part of the market, even if that part of the market is misguided.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
  7. Re:Oracle already owns an open source database by nxtw · · Score: 2, Informative

    Oracle owns Berkeley DB, from when they bought Sleepy Cat Software. Has anyone heard of _any_ useful progress in Berkeley DB, which used to rule Linux for lightweight, small databases?

    Berkeley DB is still being developed with new features - such as those in version 4.8, released less than a month ago.

    Anyway, Berkeley DB is a different kind of database than MySQL or Oracle Database.

    I thought not: they supported it a little bit, and it's been profoundly ignored for years now, by both its owners and the open source community at large.

    Surely the rise of SQLite has something to do with what you perceive to be Berkeley DB's decline?

  8. Berkeley DB back to first tier please! by IGnatius+T+Foobar · · Score: 3, Interesting

    Once upon a time, MySQL supported the use of Berkeley DB as one of its back end storage engines. Then Oracle acquired Sleepycat Software, the makers of Berkeley DB (which was, and still is, open source). MySQL didn't like the idea of Oracle controlling their back end, so they phased out its support.

    Now it doesn't matter anymore. Oracle is going to own MySQL and Berkeley DB. In my opinion, Berkeley DB is the finest storage engine on the planet. Either with a relational/schema layer on top of it (like MySQL), or all by itself (in which case it's simple key/value pairs), it is insanely reliable and its performance is excellent. I can't say enough good things about it. So how about it, Oracle? Can we get these two great pieces of software together again?

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
  9. Re:Not so fast by jadavis · · Score: 2, Informative

    Granted, there are some exceptions, but that's just what they are: EXCEPTIONS.

    They aren't just "exceptions", you have hand-waved away a majority of the free software people use.

    I don't know of any free software compiler that uses that approach (not gcc, ghc, python, ruby, perl, etc.); nor any OS (GNU+linux, freebsd, opensolaris); nor any desktop environment or GUI tools; nor any browsers or email clients; nor text editors/IDEs. For database systems, MySQL and BerkeleyDB do, but postgresql, firebirdsql, and sqlite do not. Let's say that OO.o does, as well.

    When I think about the volume of quality software that I use, the part that uses a dual licensing model is there, but it's not the predominant portion. For one thing, any dual licensed software project requires that you sign over the rights if you are an outside contributor. Not many open source projects do that, because it generally eliminates outside development except from some special cases.

    the mere possibility of support or no-business development model means there is no cause for concern

    There's plenty of cause for concern, as with any project using any model. Ultimately, a lot of things need to line up for a project to really take off and sustain itself. The "hybrid licensing model", however, is not the only way to do it.

    or have been subsidized heavily by some other business for other reasons

    That is very common, and it's a very different model than the "single company plus dual licensing" model. I would also add that it's often many businesses. It's probably a lot better in many cases -- PostgreSQL and Linux are both backed by various companies. I don't think you should marginalize this as a model for a successful project.

    Google contributes heavily to MySQL, yet they are a second-class citizen in mainline MySQL, because they have to sign over rights to get improvements accepted. I don't think this state of affairs will last very long -- they will throw their weight behind one of the forks, and become a first-class contributor to the project, among others.

    I do not think it is an accident that those few open vibrant open source products

    Which few? I use a lot of free software from vibrant projects, and a lot of it quite simply does not follow your "hybrid licensing" explanation at all.

    --
    Social scientists are inspired by theories; scientists are humbled by facts.