In August Productions

First of all, I'd like to thank everyone who has helped translating messages for Drizzle so far.

Secondly, congratulations to Dutch and French speakers, since you have translations of all translatable strings! (so far, Mark Atwood is working on an overhaul of the error message system, so I imagine we'll find some more strings that need work)

Italian speakers are close - there are only 76 of 1413 messages untranslated.

After the top three, things fall off a bit. German has 744 untranslated, English (UK) has 905 untranslated (although honestly, there probably aren't that many needing translation). Spanish has 1019 untranslated, Norwegian Bokmal has 1049 and Brazillian Portuguese has 1078. Hindi and Polish round out the top ten with 1243 and 1251 untranslated respectively.

So good job everybody, and thanks for all the hard work! For anyone who wants to pitch in who hasn't, you can just head over to http://translations.launchpad.net/drizzle and jump in

Vadim announced Percona's XtraDB a couple of days ago, and then followed up with some really fun benchmarks. Of course, the first thought I had was "I need another cup of coffee," which was shortly followed by "I should merge that in to Drizzle!"

First step was merging it in to a branch of the innodb-plugin-upstream branch, making an

lp:~mordred/drizzle/xtradb-upstream

Merged it up to drizzle trunk, and now we have:

lp:~mordred/drizzle/xtradb

But what I really want is for our changes to InnoDB/XtraDB to get merged in. So I also make a branch of XtraDB and applied our stuff to it:

lp:~mordred/percona-xtradb/drizzle

My goal there would be a chunk of code that will compile for either MySQL or Drizzle. I've done what I can for that - with the exception of actually attempting to compile it under MySQL, so it might need a new patch or two.

That has been proposed for merge into the percona-xtradb trunk. 

As far as I can tell, that's just about all of the permutations of the code that could possibly be interesting to anyone. Have fun!

At least, that's the title of one of the talks I'm giving at this year's MySQL User's Conference. I'm not going to spoil it by telling you everything here - but feel free to bring rotten vegetables to throw at me for when I say disagreeable things that make me sound like a kook.

Title pretty much says it all. Today I uploaded the latest tarball in of the NDB/Bindings project to Launchpad.

NDB/Bindings is a project which provides Java, Python, Perl, Ruby, C# and Lua bindings to the NDB API and the MGM API for talking to MySQL Cluster. 

As the version number indicates, it's not quite ready for full production use yet, although for Java and Python it is mostly functionally complete (unless something has been missed that I'm unawa - also, for those of you hardcore NDB API hackers out there, no we are not providing direct NdbRecord support at this time - but we probably won't for the 1.0 release anyway so there) There are a few projects who have already been working with the code, one of which found a performance bug that I've been considering in the back of my head.

As Brian mentioned earlier, I merged in version 1.0.2 of the InnoDB Plugin last night. Took about 2 hours - most of which was compiling and testing on a couple of different machines to make sure I hadn't b0rked anything.

Getting bzr to help me do all of this was actualy quite easy, once I corrected one mistake about how I had merged the code into the tree in the first place. (oops) 

In a move that's sure to shock my former boss, I wrote up a quick wiki page on the process, just in case anyone is interested.