Industry


Ads by TechWords

See your link here


Which SQL is MySQL?

I can be an idiot some days. As proof I'll only mention that I thought Sun buying MySQL was a great move. Boy was I wrong.

First, the crème de la crème of MySQL's developers and founders started leaving Sun. Then, Michael 'Monty' Widenius, MySQL's founder and, then Sun's CTO for its MySQL division, announced the release of the next version by publicly stating that the latest MySQL release contained "many known and unknown fatal bugs. That must have gone over well at Sun's HQ.

It probably wouldn't surprise you to know that Widenius has since left Sun. He's now working on his own community branch of MySQL, MariaDB. Its purpose? "To provide a community developed, stable, and always Free branch of MySQL that is, on the user level, compatible with the main version."

But, wait there's more. Patrick Galbraith, a senior MySQL developer, noted in his blog that we don't know "What will be the official development branch of MySQL," As it is, Galbraith continued, "There is now one fork and one major branch of MySQL [MariaDB] … both are exciting projects-- and neither of them is coming from official MySQL/Sun."

The fork, which is officially sanctioned by Sun, is called Drizzle. It's being directed by Brian Aker, a senior Sun developer. Drizzle, according to the site is a "database optimized for Cloud and Net applications. It is being designed for massive concurrency on modern multi-cpu/core architecture."

What about MySQL itself? Darn good question.

Galbraith would like to know the answer too. He wrote, "My question is then: what is the official tree? The project lead is Monty, and if he is now saying 'MariaDB' is the official tree. Does that mean that the tree at Sun is now dead? Open source projects usually have their souls found in whoever personally leads the project, not in who owns the copyright of the name. Monty and Brian certainly are open source leaders, so my inclination is to follow them. This is not a slight to MySQL/Sun either, but a question that me as a both a user and developer of MySQL, as well as a former employee and team member of the MySQL development team."

I don't think he's going to get an answer soon. Both Sun, which just laid off 1,500 employees this week, and MySQL are in disarray.

I think the best thing that could happen to the 'official' MySQL is for IBM to complete its acquisition of Sun as fast as possible. That deal, by the way, no matter what rumors you may have heard, is still very much alive.

Once that's done, maybe we'll get to see what can be done by merging the best features of MySQL and DB2. Or, considering IBM's usual hands-off management approach to major open-source projects, perhaps Big Blue will just give its blessings to one or the other, or even both, of the existing MySQL branches and let them roll.

What People Are Saying

Anyone remember mSQL?

Yes, mSQL. It must be 11 or 12 years ago (I left that job > 10 years ago) when I found that a guy in Australia had created this nice little open source rdbms that was just right for my little network monitoring app.

It became popular and so he decided to try to make money from it. Trouble was that he thought that the way to do this was to take it closed. Boy was he wrong; development just forked away from him. As my app used Perl DBD, I just changed one letter, ported the db and was up and running with MySQL - as the new fork was named.

The web site is still there as a lesson to anyone who doesn't understand that opening up code is how you make a project succeed (and make money) nowadays. I don't think mSQL made him a millionaire...

So - when anyone holds forth about effect of a new owner trying to re-license (or even destroy) MySQL, just remember how it started out. Once code is GPLed, no-one can undo it. Not even the copyright owner.

Can you cite your sources?

Can you cite your sources? I can't find any evidence that MySQL was a fork of mSQL. Wikipedia at least is unaware of this.

mSQL and MySQL are different...

For background on the differences and origins of these two distinct platforms, there was an O'Reilly book on both of them back when MySQL was considered an infant and mSQL was the prominent player, smaller, simpler, but quickly being overtaken by Monty's juggernaut.

I hope that helps :)

Kindest regards,

-Bradley-

Don't make a storm on a glass of water...

MySQL is a very valuable software asset. It won't suffer. Over the years, it hasn't be controlled by a single company or individual. Let's see only the case of the storage engines:

  • The storage engine InnoDB was developed and owned by an independent company, InnoBase OY, bought some years ago (2005) by Oracle.
  • Oracle has also owned for some years the Berkeley/SleepyCat storage engine
  • OurDelta distributes MySQL binaries that include patches to InnoDB from Google, Percona, and others. It also offers XtraDB, a fork of InnoDB.
  • IBM offers SolidDB, another quick and robust storage engine.
  • NitroEDB, BrightHouse and others offer another set of storage engines

Again, MySQL WON'T SUFFER at the merger of Oracle and Sun. Even if Oracle tries to kill it (at a big-and-stupid expense, because the same Oracle owns crucial parts of it) MySQL will remain. The problems may even spur the development, and make it even stronger.

Don't know why they bought it

I can't figure out what Sun was gaining by buying MySQL. Brand name recognition of some kind? Cutting edge techno points with executives who learn everything they know about IT from reading airplane magazines?

Sun was already a supporter of PostgreSQL. Given the choice between PostgreSQL and MySQL Sun should just have stuck with PostgreSQL.

PostgreSQL

with all the upset with mysql, I think it's a good time for people to give postgresql another look. I think it's the better of the 2 databases, and has been for a long time, but that's my opinion...

check it out, http://www.postgresql.org/ can't hurt.

missing the point...

You are totally missing the point here. This might actually help MySQL get better in the long run for it's different audiences. At least the community branches acknowledge what MySQL is used for and don't try to push things that are unneeded outside of marketing.

I am really getting tired of the unqualified "postgres is better!!!11" reaction when MySQL gets mentioned

A very good advice. The

A very good advice. The moment the news of the acquisition of MySQL by Sun (preceeded by the acquisition of InnoDB by Oracle), I started looking around to go away from MySQL, ending up at PostgreSQL. And now I am wondering why I was not using pgsql all those years...

Missing the point...

It's not about which one is "the real MySQL" but it's about capabilities.

Here's more on that: http://jeremy.zawodny.com/blog/archives/011046.html

Jeremy

Thanks for the pointer

I'll check it out.

Steven