I'm quite certain I don't have a shot at this, but here goes.  Find all the details here.

[Update #2/3: My mistake. It was 3.23 that it was only in mysql-max, so the article is correct. Second comment (under update) still stands :-) Cheers to those that provided the feedback (Markus, LenZ, Thomas) Next time I'll know how to get peer review quickly :-)]

I've been on holidays for a while now (and will be until 16th Jan. w00t!). One of my new found past-times has been contributing to Wikipedia. I spotted this on the InnoDB article:

"InnoDB is a storage engine for MySQL, included as standard in all current MySQL AB distributions. "

Technically I think InnoDB was only in the mysql-max distributions until 5.0.
Is it fair to say that 4.1 is not current *although* it is still listed as a generally available (GA) release?

I guess you could argue either way, but it could be made clearer. Second opinion wanted.

…

Happy New Year everybody!

Like most MySQL employees, I work from home when I'm not travelling. And you may have seen the photo with the hammock, but I do actually have a desk.

It used to be in a separate room, but we made it into a room for our daughter Phoebe. So I moved to another room, which was subsequently hijacked for my wife's home teaching business. All good causes, mind you, but my desk ended up next to the kitchen and the lounge room. Easy access to the fridge, but by no means optimal - particularly now with Phoebe - a fab distraction any time.

    

So over these past holidays, I shifted downstairs. It looks a bit bare still and we'll be doing some more work on the place, but it's pretty good already. …

Happy New Year everybody!

Like most MySQL employees, I work from home when I'm not travelling. And you may have seen the photo with the hammock, but I do actually have a desk.

It used to be in a separate room, but we made it into a room for our daughter Phoebe. So I moved to another room, which was subsequently hijacked for my wife's home teaching business. All good causes, mind you, but my desk ended up next to the kitchen and the lounge room. Easy access to the fridge, but by no means optimal - particularly now with Phoebe - a fab distraction any time.

    

So over these past holidays, I shifted downstairs. It looks a bit bare still and we'll be doing some more work on the place, but it's pretty good already. …

Daniel D. sent me some good info on analyzing MaxDB kernel trace output.

I still need to read it a few times and try it out myself, but here is the link so you can follow along :)

http://wiki.colliertech.org/index.php/MaxDB:kernel_trace

Daniel D. sent me some good info on analyzing MaxDB kernel trace output.

I still need to read it a few times and try it out myself, but here is the link so you can follow along :)

http://wiki.colliertech.org/index.php/MaxDB:kernel_trace

By nikolaj

MySQL CEO Marten Mickos' New Year greeting reminds us that "there will be a growing group of young software professionals not knowing that there was a time in the 20th century when software was not open and free."

With the OSCON '06 Call for Participation just open, and the MySQL User Conference only a few months away, there's no alibi for not enlisting.

If any of you are curious who my employer is, here is a good description:

http://dev.mysql.com/doc/refman/5.0/en/what-is-mysql-ab.html

I actually work for MySQL, Inc., the US subsidiary, but we subscribe to the same set of core values. And happen to be US citizens.

If any of you are curious who my employer is, here is a good description:

http://dev.mysql.com/doc/refman/5.0/en/what-is-mysql-ab.html

I actually work for MySQL, Inc., the US subsidiary, but we subscribe to the same set of core values. And happen to be US citizens.

Well, time to get back to work at MySQL. Here are the latest reno photos for those of you following my renovations:

BTW the post has its name because of a comment by my coworker Jon Stephens:

gee, i'm totally outclassed - you post photos of sludge, and my latest blog entry is about hacking a MySQL build script