Although, hosting the event on a weekend, which is an inconvenience to those who have family, and ignoring the fact that it's Oracle's third MySQL Connect event, I would have to say that this year's Oracle MySQL Connect conference was the best one yet.

This past year, I have been mostly heads-down working at +LinkedIn so I haven't been paying close attention to what Oracle has been doing for +

Just mentioning it here because hard work deserves to be recognised and mentioned: Andrew McDonnell is doing an awesomely good job of testing, understanding and fixing bugs in OQGraph... which is no mean feat because the core of the code is based on the Boost Graph Library which isn't a trivial C++ library.

Over at David Stoke's Open Source DBA blog, the following was posted: http://opensourcedba.wordpress.com/2013/07/05/mysql-is-looking-for-external-contributions My reply: Allow me to contribute code with a BSD (3-clause) license without having to sign anything new and then we can talk. Don’t tell me that it can’t be done: Oracle already has some code of mine in another product which was

A collection of thoughts, quotes, jokes, .. which I posted as status updates on Facebook. My favorites are bold (no pun intended).

They say sucking is a newborn instinct we forget; some people, however, keep sucking their whole lives.

Love has the symbol ♡; what symbol would hate have?

Putting MySQL Cluster on virtual machines and expect it to behave.

If only my wallet was as big as my heart..

If you dwell long enough in shit, you forget it stinks.

A System that is not Intuitive is not a System.

Sometimes it’s better to wait for the fire to see how to actually extinguish it. Standing ready with a bucket of water, just to find out that the flames come out of a frying pan is not productive.

What’s a Miss eating a steak? .. A mistake!

What’s a t-shirt with an issue? .. A tissue!

…

MySQL v5.5 is GA and my blog, using WordPress 3.0, runs on it.

My personal highlight of this new MySQL version? The fact that it is released by Oracle.

A few SQL queries are worth a thousands words:

mysql> SELECT VERSION();
+----------------+
| VERSION()      |
+----------------+
| 5.5.6-rc-debug |
+----------------+

mysql> SELECT @@global.storage_engine;
+-------------------------+
| @@global.storage_engine |
+-------------------------+
| InnoDB                  |
+-------------------------+

(Note: the above is without using the default storage engine option)

Scary! Excitement! MySQL!

A few SQL queries are worth a thousands words:

mysql> SELECT VERSION();
+----------------+
| VERSION()      |
+----------------+
| 5.5.6-rc-debug |
+----------------+

mysql> SELECT @@global.storage_engine;
+-------------------------+
| @@global.storage_engine |
+-------------------------+
| InnoDB                  |
+-------------------------+

(Note: the above is without using the default storage engine option)

Scary! Excitement! MySQL!

This is a friendly reminder to check the publication date and discussed version you MySQL books before starting out hacking or even posting about limitations. Lots of old books are still going around. Maybe it's good to destroy them rather than giving them to students or newbies.

Few days ago (28 May 2010), for example, we had a word-for-word copy of a book on a blog post (now removed) which was discussing MySQL Cluster limitations from years ago. Well, it was funny at first and we had a good laugh. But it's a bit worrisome. My colleague Matthew posted a rebuttal post.

How would you recycle the old, technical books? It's not worth giving them to public libraries, it's maybe unhealthy to burn them? How would you do it?

There is no denying that MySQL has a huge amount of momentum behind it. 10+ years as the leading free SQL database kinda does that. It has successfully changed the perception of databases - where people used to visualise big-iron mainframes in specially cooled rooms to where anyone can install it for free within 15 minutes.That is not what this blog post is about. The topic of today is the "Save

I let a couple of these pass by but just thought I'd mention it (just in case any other ex-MySQLer is experiencing anything similar...Why does the MySQL bugs system remove former employees from the historical record?Date: Thu, 17 Sep 2009 20:26:35 +0200From: Bug Database Subject: #29838 [Csd]: myisam corruption using concurrent select ... and updateIn-reply-to: X-Originating-IP: [140.98.193.23]To