"I head Monty has 20/30 people ready to leave, do you know when you are going to start?"

The answer is that is not in my plans. I continue to be pretty happy at Sun and continue to find and enjoy new co-workers to interact with.

So what am I doing?

For one the Drizzle team is completing its Cirrus milestone and preparing the project for source/tarball release. We set up the milestone back in October and we have been making great headway in getting it completed. There has been a lot of effort from what is roughly a hundred or so folks working on making that happen (40+ in code, but there are a lot of tasks that have nothing to do with programming). It will be an exciting spring for the project and we are moving like a rocket toward it. We have seen the …

This little project is quickly growing into a pretty big movement, the response at and after Linux.conf.au in Hobart was tremendous! Ah sorry, should tell what this is all about eh!

Well, many among us have dealt with or are struggling with depression and related hassles. It's not because we're geeks, but because we're all human. However, in our line of work we may have particular non-optimal work environments: working inside, lack of movement, lack of daylight. Also many companies are pretty high stress through understaffing, short deadlines, ad-hoc management and the like.

Also, one of the key issues with depression is the feeling of being alone, and it's not something that commonly gets talked about. That of course doesn't help people cope and recover.

While there are many excellent sites and organisations that provide help, BlueHackers acts as a …

Arjen & Monty @ LCA2009 in Hobart

I did a couple of sessions on OurDelta at the Linux.conf.au database miniconf: an overview of the project, a short delve into the features, and a “hacking the mysql server for dummies” which was found of particular interest. It’s a pity that session didn’t get accepted into the MySQL conference, it even had MySQL-uberguru Antony Curtis as co-speaker.

In the hacking talk in Hobart, I showed people the basic infrastructure of the source tree, then going through one particular patch and which changes it makes inside the server (and why). This is an excellent way to learn, as patches have a neat limited scope yet they do something significant. The good news is that the sessions were recorded, so when the LCA team finishes transcoding the hundreds of sessions we might be able to put ours up here!

Original author and MySQL …

Monty Widenius leaves MySQL behind, but the company still abides by the open-source principles that originally made it great.

I have now departed from Sun and joined my own company, Monty Program Ab.

There were a lot of rumors around me resigning in August/September last year. I didn't back then want to comment on the rumors, because I was still trying to work something out with Sun. Now I can finally describe a bit of what was going on.

In this case, the rumors had some elements of truth to them. I had told management that I thus would be submitting my resignation immediately as I strongly believed that the 5.1 release was not ready and that those problems needed to be fixed before it went GA. This action, together with other peoples´ efforts, did have the wanted effect and I made an agreement with Sun´s upper management to not initiate my resignation but instead stay around for three more months to help Sun …

One year after Sun acquired MySQL we see the positive results of this acquisition. Things are going very well in terms of collaboration, the teams are getting closer together and share the experience and the knowledge. If you want to know how the teamwork is seen from the Sun Cluster engineers, Thorsten Frueauf and myself, you should read this.

It was interesting for us to see that this interview was well observed by MySQL customers and community members. Although the interviews were not technical, they lead to technical questions. You can get more information here.

So if you are keen to see what the MySQL community wants to know about Sun Cluster, read the blog entry about MySQL and Sun Cluster.

Detlef …

One year after Sun acquired MySQL we see the positive results of this acquisition. Things are going very well in terms of collaboration, the teams are getting closer together and share the experience and the knowledge. If you want to know how the teamwork is seen from the Sun Cluster engineers, Thorsten Frueauf and myself, you should read this.

It was interesting for us to see that this interview was well observed by MySQL customers and community members. Although the interviews were not technical, they lead to technical questions. You can get more information here.

So if you are keen to see what the MySQL community wants to know about Sun Cluster, read the blog entry about MySQL and Sun Cluster.

Detlef …

Phipps speaks to ZDNet Australia about the MySQL acquisition and community engagement on OpenOffice.org and OpenSolaris.

I thought I would write a few blog posts on what I am calling the 5 minute DBA. The content of these is  interesting or frequently asked questions that I get when out on a gig, you know those ones were a developer or a dba runs up and says: “Hey how do I do this?” I figure, If nothing else maybe it will save me some time in future.

There are two audiences here. The first is the true 5 minute dba. Their seems to be a lot of folks out their who end up responsible for fixing or maintaining a MySQL database who are not really DBA’s. They maybe developers, sysadmins, or even network guys who know just a  little about databases. These guys and gals become DBA’s five minutes at time during the day generally when something goes wrong.  They tend to be  looking for the quick fix, something that can be done in five minutes or less so they can get back to their other important tasks.

The second group are comprised …

Innodb source code is organized into directories where each directory holds the C source code files for a given module. Within the directory are 1 or more files that are part of the module. The file names have a structure which I will describe below.

The first part of the file name indicates the module name. The module name is followed by a '0' character which is a separator. The second part of the file name represents the sub-module. Most modules have one file where the sub-module is the same name as the module, this file represents the primary file in the module.

For, example the main file for Btree is located in the btr directory and named: btr0btr.c
The first btr indicates the module name, the 0 is a separator and the the second btr is the sub module name which is the same for the primary file.

The file that handles the Btree cursor is also located in the btr directory and named: btr0cur.c …