Mike Zinner and team have put an absolutely wonderful set of tutorials on MySQL Forge targeted at understanding and extending the GUI Tools platform. The first article, MySQL Workbench Scripting, gives you a quick introduction on how to write scripts for the MySQL Workbench tool, complete with sample Lua code in zip files. The second article focuses on writing plugins for MySQL Workbench.

OK, so here is the challenge to the community. The first one of you to write a useful, documented plugin for MySQL Workbench and post it into the Forge will get a signed copy of Pro MySQL and …

The 2nd Monday of the month is already here which means tonight is the Boston MySQL Meetup. Jacob Nikom from MIT Lincoln Labs is giving a presentation entitled Measuring MySQL Server Performance for the Sensor Data Stream Processing.

I attended Jacob's session at the MySQL UC. It's pretty amazing the amount of data they are processing and the depth that they went to get performance benchmarks across multiple versions of MySQL.

If you aren't in town, or can't make it this month, I've got the camera batteries charging and will post the video later this week.

Start of a new blog for only my MySQL stuff.

For a migration, I needed a latin1_german1_cs collation, that is, I needed German umlauts to sort as their base characters.

Here is what to do: Find your charsets directory with "SHOW VARIABLES LIKE 'char%dir%'".

Inside that directory will be a file Index.xml. Find a free id and add your new collation using an unused id. Add a description and a name.

Inside the same directory is a file latin1.xml. Inside that file, copy the block of the collation matching your new collation most closely, and adapt it as needed. In my case, I changed latin1_german1_ci to _cs, and modified the character values to match.

Patch attached after the break.

How to use:

After applying the patch, the server must be restarted. "SHOW COLLATION" will now show the new latin1_german1_cs collation. "ALTER TABLE t CHANGE COLUMN oldcol newcol varchar(80) CHARSET latin1 COLLATE …

It gives us great pride to announce the release of MyComponents V4.4 native Delphi/Kylix VCL suite. This update includes mainly fixes to issues as it has been reported to Support and on this and other forums.

What's new?

TMySQLDataset:
New: RemObjects' DataAbstract driver 3 and 4 API included.
Fix: Various issues as has been reported to SciBit Support

This update is free of charge for all customers whom own a 2005.4.x MyComponents serial. Everyone still using a pre-2005.4 MyComponents may upgrade to the newest version by logging into their Secure accounts: simply click the Secure link at the top of this page.

Previous articles concerning MyComponents 4.x are:
…

A Googly MySQL Cluster Talk - Google Video

The talk I gave at Google is now up on Google Video for all to see. I don’t think I gave it as well as I did at the User Conference (largely because, I think, by this time I was really tired), but it still went well (I think).

Feedback is much appreciated - always looking for ways to improve my talks.

Oh, I’m also wearing an Augie March t-shirt.

Update: watching yourself give a presentation is a bit strange… but hopefully I can learn from watching my own talk.

Things I’ve learnt so far:

• some words are spoken a bit quickly/mumbly. probably due to not knowing how long this presentation would go for (it was a bit cobbled together in the two sessions …

In this photo: Gallery :: MySQL Users Conference 2006 :: 3 it seems that Jeremy managed to capture me (in the background) explaining to the O’Reilly conference woman (I forget her name…. Arjen knows) that it really wasn’t too hard for them to get me lunch considering that inside the building the restaurant staff managed to get food for me (so why can’t they do it outside). I also expressed my dismay at my interaction with the staff around an (afternoon/morning… i forget now) interaction involving a request for an apple (see “How not …

Greg, a fellow MySQL'er is visiting for the next couple of days and he mentioned an article he read at the airplane in Fortune called How I Work: Bill Gates. It got me to thinking about how I do my own work.

My days are segmented into three parts. In the evening I talk to people in Russia, in the morning I reserve time for people in Europe, and I work with Americans in the early afternoon. My week starts on Sunday evenings, and I try to go walking or sort my notes from the week on Friday afternoon when the work week for MySQL is tailing off.

Today I use Mail.app on an Apple 15in laptop to handle incoming email. I have filters that have been placed on servers using procmail to squelch the incoming email I get on both my personal and work email account. I …

At this years LinuxForum I was manning the MySQL booth together with Carsten Pedersen. We were kept quite busy with lots of people coming to tell about their use of the MySQL database for their particular project and ask about or discuss a particular issue of theirs. Which was fine, since the talks did not appeal a lot to me anyway.

One guy (I forgot who) had a small performance problem in his application. The application is a database of about 550,000 companies, storing name and various other bits of information about each company. What I would call a "small" database (since it is easily kept completely cached in ram), though not a trivial one.

This application has a facility to search for a company using any part of the company name:

    SELECT ... FROM company WHERE name LIKE …

Anyone who has used an automated unit testing framework such as Junit knows just how life-changing an automated test suite can be.   Once you've  experienced validating that recent changes have not broken old code, or discovering subtle bugs via junit that would otherwise have remained undetected , you naturally want to have this capability in all your programming environments.

Guisseppe Maxia has written a few stored procedure snippets to assist with automated unit testing of MySQL routines.  Unfortunately, the MySQL stored procedure language itself does not have the necessary abilities to fully implement the sort of unit testing we would like.  In particular, the inability for a stored procedure to capture the result sets generated by another stored procedure prevents a stored procedure from fully unit testing another. 

So I decided that …