I have been very busy this past months, with both personal crisis
and mega-patches. This is my MySQL blog so lets keep it to
topic.
A couple of weeks ago, the plugins mega-patch was finally pushed
and was released to the world in version 5.1.18. Thanks to Ingo
and Sergei for keeping up the effort while I was occupied. As
part of the code push, InnoDB code was stripped out of the main
mysqld code and stored where it belongs, within Innobase's code.
This is an exciting development as it now makes it easier than
ever for plugin developers to create plugins without having to
modify any existing code within mysqld. It has taken many months
to get to this point but we are finally there. Anyone remember
our CEO announcing the plugin initutive back when Innobase was
acquired by Oracle? October 2005, I believe.
Since that push, I am back on bug-fixing... I have an annoying
bug on Itanic with Intel's Itanic Compiler. (Yeah, I know the …
The latest from the MySQL community
Ideas, releases, practical guides, and perspectives from the people building with MySQL.
I came back from a two-week snowboarding trip to Zermatt -- my first to Switzerland, and what an excellent trip that was. Great powder, great freeriding, great weather. Will post some photos once I've sorted through them, but in the meantime, Sanna took some as well and posted them to her moblog.
On another note, I haven't mentioned Jim Starkey's comments to my previous post, but they're good reading to everyone interested in MySQL, with clarifications to some things I misunderstood in the documentation. I'm glad to hear that the "serial writes" don't in fact mean just one thread writing, as well as that he believes the engine will at a later stage allow multiple tablespaces per logical database.
One of the unique elements of MySQL is the ability to use a different storage engine to store your data. You can even mix and match storage engines within the same database.