We have a new April labs release that you can download from labs.mysql.com. There are more labs releases. Please try them all, but for now let’s focus on the one called “MySQL GIS, InnoDB R-tree, Parser Refactoring”.

The release contains InnoDB R-trees, the first step of our new GIS implementation, a refactored and faster parser and improved condition filtering cost calculations. You can download and run the binaries just like before, but if you want to build it from source, there are some details you should know. Otherwise you may fail to build MySQL (bug #72172).

This labs release requires Boost to build. Specifically, it requires Boost 1.55. But don’t go running off to boost.org looking for the latest tarball just yet — there’s no need for that. The MySQL build system will do everything …

The latest version of Sun Studio, which is a terrible name for something which is a compiler and not an IDE, which has now been re-titled Solaris Studio in an attempt to underscore even more its general uselessness, has added a new antifeature to its installer.

It requires X.

You know one of the things that makes MySQL better than Oracle? You can install it in 5 minutes and you don't have to launch a Java GUI.

You know when it makes sense to launch a Java GUI to install server software?

NEVER

EPIC FAIL 

When you rely on something like Jenkins to help manage your project, if you don't have a feature regularly tested in it, that feature often bitrots pretty quickly. This was the case for our Windows compile of libdrizzle. It worked months ago, but then some folks tried it recently and, well - not so much with the working. That meant I had to do three things this weekend:

1. Get the Windows machine that was sitting at my old office powered off and actually plug it in in my new office
2. Fix the build
3. Connect that machine to Jenkins

I'm happy to report all three are done, and we now have a Jenkins slave building libdrizzle on every push. I believe I should also be able to build the client programs, so I'll add them soon - and then it's only a few steps away from having Jenkins produce an msi or something that people can download.

In case you're wondering, we …

Thanks to Jobin's work with mingw and getting libdrizzle to compile on Windows at all, I have been able to get it working in Visual Studio natively. The code is in trunk now.

The approach I took, which is how I'm going to approach Windows and Visual Studio for all of our stuff, is to not worry with analogues to things like configure on Windows. Windows is a very different platform from Linux, and there is no need to attempt to duplicate Linux process there. To that end, the goal at least for now will be static VS Solution files and a set of instructions of how to get depends installed so that the Solution can find them. 

I'm excited to start poking at Garrett Serack's CoApp Project, which has some tools do do tracing of things like make to help with the initial project creation... …

Recently, Jobin took up the mantle of starting to poke at Windows support for Drizzle. We decided that step 1 is getting libdrizzle building on Windows - not to mention we could solve a few systemic "how to go about it" problems on a much simpler codebase.

We decided to go the mingw route - for two reasons.

1. on windows we wouldn't have to solve the build problem yet
2. on linux we can cross-compile, and then I can spend less time connecting to a windows machine 

I'm happy to say that the branch implementing support for building under mingw has been merged in to trunk - so please go hammer at it and tell me that I'm an idiot.

If you're on linux and want to play, you'll need mingw32 and mingw32-pthread. You may notice that mingw-pthread isn't in the …

Why does this change make me feel better? Because cmake configuration is more user friendly than the old autoconf/automake/libtools horror syntax. Not only that, but there is a GUI!
I am a command line guy, as you probably know, but when the purpose of a GUI is not only to show off but to make …

We are pleased and excited to announce the availability of 1.0.0 Release Candidate 1 of InfiniDB Community Edition.  This is our initial release candidate and is not recommended for production work.

This release includes a number of bug fixes that you can see at http://bugs.launchpad.net/infinidb.  We will continue with weekly releases this month marching towards our GA release in early February.  You can download the latest InfiniDB binaries, source code, aRead More...

We are pleased and excited to announce the availability of 1.0.0 Release Candidate 1 of InfiniDB Community Edition.  This is our initial release candidate and is not recommended for production work.

This release includes a number of bug fixes that you can see at http://bugs.launchpad.net/infinidb.  We will continue with weekly releases this month marching towards our GA release in early February.  You can download the latest InfiniDB binaries, source code, aRead More...

We are pleased to announce the availability of the 0.9.5.4 beta release of InfiniDB Community Edition.  This is our second beta release and is not recommended for production work.

This release includes a number of bug fixes that you can see at http://bugs.launchpad.net/infinidb.  Here are a few items of note that we have included in this release after valuable feedback from the community:

Increased maximum length allowed for char and varchar colRead More...

We are pleased to announce the availability of the 0.9.5.4 beta release of InfiniDB Community Edition.  This is our second beta release and is not recommended for production work.

This release includes a number of bug fixes that you can see at http://bugs.launchpad.net/infinidb.  Here are a few items of note that we have included in this release after valuable feedback from the community:

Increased maximum length allowed for char and varchar colRead More...