"Save MySQL"; my 2 cents.

There is no denying that MySQL has a huge amount of momentum behind it. 10+ years as the leading free SQL database kinda does that. It has successfully changed the perception of databases - where people used to visualise big-iron mainframes in specially cooled rooms to where anyone can install it for free within 15 minutes.

That is not what this blog post is about. The topic of today is the "Save MySQL" campaign and how I believe it is unnecessary.

In fact, I believe that it could be harmful.

Like Anders, I have mostly been refraining from participating in this campaign but now I think it would be helpful for people to know my reasoning why.

Let us consider some scenarios:

1. Oracle acquires Sun, ceases MySQL development.
   
   This would be a Pyrrhic victory for Oracle as the community would immediately coalesce around MariaDB / popular forks. Everything continues... except the MySQL trademark.
   
   Oracle is not that stupid.
   
   
2. Oracle acquires Sun, allows MySQL development to continue as before.
   
   In my opinion, this would be the worst possible scenario for MySQL/MariaDB/forks as it would divide and fragment the community as the codebases diverge.
   
   Are the "Save MySQL" campaigners really trying to achieve this goal?
   
   
3. Oracle does not acquire Sun, Sun continues MySQL development as before.
   
   See previous point. Equally disastrous.
   
   
4. Sun sells MySQL intellectial property to third party. Oracle may or may not acquire Sun.
   
   Who would the third party be? Sun shareholders would be very annoyed if the sale was for less than $1bn... and rightfully so! Who has the cash to pay $1bn for a open-source database? I doubt that IBM would come to the rescue here as I doubt that there is enough IP in MySQL alone to interest them and the SAP bridge has already been burned.
   
   

So, what do I want to happen? That is a good question. There are a lot of tough decisions which has to be made to complete MySQL/MariaDB/etc. I like that MariaDB is being developed by Monty and many other long-time MySQL developers: A part of me wishes to be working with them to help shape it's future.

Perhaps "MySQL" should become like "Linux". A brand owned by a benevolent organization and permits many distributions to use it to name their database product. The "MySQL" brand would require that so named software be GPL, share a common protocol and SQL dialect. There would be an open MySQL Compatibility Test kit which would test distros for compatibility to some "gold standard".

Perhaps that is what I would like.

Version Number 5 point WTF?

What is going on with the version numbers coming out of Sun/MySQL?

Once upon a time, we had 5.2.

Then, to incorporate Falcon, it became 6.0.

Somewhere along the line, there was a 5.3.

Then a 5.4 appeared which seemed to be 5.1 with performance fixes for InnoDB.

Now there is a 5.5, which claims to be a 5.4 with a few stuff added.

Stop confusing your community.

And whatever happened to community participation?

People would like to know.

2010 will be a good year,

I suppose I should make it official: 2010 should see me being much more active in the Community.

Why? Simply because I am now working for Blizzard Entertainment where I hope to help them make better, more efficient, use of MySQL/MariaDB. I expect to be working on some of MySQL's internals and storage engines in order to achieve what is wanted and helping them enhance their existing use of MySQL.

Exactly what my role will be and the other little details, is still taking form but hopefully, we would be able to contribute some stuff back into the community.