When I started with MySQL 3.22 I would start running MySQL from early beta (if not alpha) and update MySQL the same date as release would hit the web. Since that time I matured and so did MySQL ecosystem. MySQL is powering a lot more demanding and business critical applications now than 12 years ago and it also a lot more complicated product with more things which can go wrong.
MySQL Community Server 5.1.60 has been released and I am very happy because the release notes state that bug #12704861 has been fixed. I know this bug quite well. As my readers are very busy let me provide all of the details that have been made available to the community:
Wordpress is a very popular Content Management System, usually built on top of a MySQL Database. Recently I attended a local Wordpress user group an that started me wondering what the database tables look like. So I installed a new Wordpress installation on a Ubuntu test box running MySQL 5.6.2.
Wordpress creates eleven tables: wp-commentmeta, wp_comments, wp_links, wp_options, wp_postmeta, wp_posts, wp_term_relationships, wp_term_taxonomy, wp_terms, wp_usermeta, and wp_users.
Today we will get MySQL Cluster running on a single node.
A few years ago I created as presentation on running MySQL Cluster 5.1 on a laptop using Virtualbox that has proven to be the most popular download from NorthTexasMySQL.org with over nine hundred downloads. Now MySQL 7.2 is in development milestone release and I find that I have some catching up to do.
I’ve just arrived at ANU in Canberra for the Open Source Developers Conference 2011 (OSDC). I’ve spoken at several of the past OSDCs that have been held around Australia: 2005, 2007, 2008, 2010 and now 2011. It’s one of those conferences with great energy and great people that’s organised by dedicated members in the community who build the conference they want to go to.
I’ll be giving two talks this year:
My friends at Sphinx Technologies have finally released new beta of Sphinx – Sphinx 2.0.2. It includes about 6 months of development and includes over 30 new features and tons of bug fixes. I’m happy to see how Sphinx 2.0 is shaping up a lot of rough corners are being polished and I’m hopeful we will see very solid Stable Sphinx 2.0 within next 3 to 6 months. In fact Sphinx 2.0.3-rc is promised within 1 month.
I tend to speak highly of the random query generator as a testing tool and thought I would share a story that shows how it can really shine. At our recent dev team meeting, we spent approximately 30 minutes of hack time to produce test cases for 3 rather hard to duplicate bugs. Of course, I would also like to think that the way we have packaged our randgen tests into unittest format for dbqp played some small part, but I might be mildly biased.