Singapore. Last stop of my world tour. Shortly after my arrival, the new Lunar Year began. The year of the rat was happily celebrated, and its symbols can be seen everywhere in town.


In Singapore, the Freedom To Work Anywhere @ MySQL has a new meaning. Most of the town is connected via a free wireless net. While sitting on a public bench (in cool evenings) or while enjoying food and drinks at hawker centers and cafes, you can just fire up your laptop, connect to the free wireless, and start browsing. You will need to get a (free) username and password through your mobile, but you can live with it easily.
I am on vacation, so I am not "working from anywhere", but the ubiquity of the wireless connection was hard to resist!
By the way, in case you were wondering if the Sun acquisition …

Last week, we held a conference for leading financial and industry analysts from around the world. My keynote presentation is below - broken into two parts for ease of viewing. One analyst remarked, "but this is pretty much what you said last year."

I responded with, "That's the point."

If you'd like more specifics on our financial performance (directly from Mike Lehman, our CFO), views from the marketplace (from Don Grantham, our Global Sales and Services) or specific product roadmaps (from the heads of our Systems or Software businesses), just click here...)

A lot of people have repeatedly asked me why I’ve not mentioned my thoughts on the Sun-MySQL acquisition (and this blog post, clearly comes almost a month later). I’ve just been pre-occupied and have not had the time to come up with a lengthy blog post. I can however, recommend the following video, created by Mike Lischke, of MySQL Workbench fame.

Naturally, you should also read the Q&A Session with Marten Mickos, that was mostly whipped up almost immediately after the acquisition. Editorial kudos on that one goes to Lenz Grimmer, Steve Curry, and Zack Urlocker. I pretty much had those thoughts that Marten answered really …

The table t is defined thus:

  CREATE TABLE t (
   id INT NOT NULL,
   data CHAR(30) DEFAULT NULL,
   UNIQUE (id, data)
  );

You now do…

  INSERT INTO t VALUES (1, NULL);

Which causes one row to be inserted into the table. Keeping in mind that the UNIQUE index spans across both columns, what would happen if you were to repeat the INSERT command?
Spanish translation by Marcos Besteiro
(more…)

Since 2005, every year we have done some kind of "Mayflower weekend". As we're a bit of a distributed company (departments in Munich and Würzburg, called Herbipolis, several "on-site departments" at some of our biggest customers, an offshore department in beautiful Argentinia and since 2007 a sister company called SektionEins located at Cologne watching out for Web Security) it's always fun packing the crowd together and putting them into a hotel somewhere in Germany (or Barcelona, Spain in 2006 and Budapest, Hungary in 2007). If you followed Wolfram's blog you noticed that we also had some external guests (if you need a Dojo freelancer, I recommend hiring Wolfram although he's a Pythoneer ;-) ) alongside the camp. The event was located at the hotel …

One of the workshops on our Barcamp two weeks ago had to do with the MySQL-Proxy from Jan Kneschke.

Yet, we found out, that the proxy is rather unuseable for our task. Read here why.

Continue reading "Playing arround with the MySQL-Proxy on Mayflower-barcamp"

I’ve been giving presentations at work each week about MySQL DBA topics. An hour of speaking about the things one does on a daily basis is rather fun, and hopefully spreads the work about how efficient MySQL is to administer and setup, as well as optimize and troubleshoot vs MSSQL and Oracle - for which we also have weekly classes.

Recently I’ve been covering backup and recovery methods, which brings me to my next point - the talkback scripts I have been integrating into my Monolith application. These scripts are wrappers for mysqldump that do extensive error checking for file completion, directory pruning to rotate out old backups per the backup retention period policy, and then report back via email and to a separate database for tracking purposes.

Here is the create table for the reporting aspect. Note: this is part of the Monolith 1.2 release which is still in beta. Stay tuned for the release that includes this, as well as …

***All point news bulletin***Do not ever use NOW() - `datetime field`! Broadcast this from the mountaintops of open source to the valleys of companies who dabble in it.Instead, use the following:TIME_TO_SEC(TIMEDIFF(Now(),`datetime field`))There are other ways to do the above, just as long as you do not use NOW() - `datetime field`.Wanna see proof?mysql> SELECT RIGHT(NOW(),8) `Now`, RIGHT(

Someone asked me what applications were good/bad for MySQL Cluster. As I’ve now actually had experience with a Cluster setup and a real-life application of it, and dug through the manual, I present a few characteristics of applications that will work with Cluster, and why they are so (so that if you have an [...]

With MySQL 5.1 reaching release candidate stage, I have been reviewing ALL of the MySQL Certification exam questions to hunt down any items that may now have been superseded by the march of progress. And right now the Merge Storage Engine has caught my eye.

With 5.1 comes the ability to disable the Merge Storage Engine. It used to be that you could not disable the MyIsam, Memory, or Merge engines. They were compiled in and could not be disabled. They were a constant, solid and dependable. But now you can pass --skip-merge to mysqld and disable it.

Does this option effect a lot of people? I honestly don't know. But it will change a few questions on the certification exams. And it may make a great piece of knowledge if they ever publish the Trivial Pursuit MySQL Edition.