Add the sad fact that …

Planned Falcon Blog posts: 4
Actual posts: 1
Team emails debating the cost of changing core components: 44
Post-debate emails suggesting a major change to a core component: 1
Days advance notice to change my LDAP password: 9
Nag emails to change my LDAP password: 9
Days of delay before changing my LDAP password: 9
Hours unable to access email after changing my LDAP password: 6
Calls to support after changing my LDAP password: 1
Falcon IRC non-system messages: 2022
IRC champ: Hakan (23%)
Runner-up: Vlad (21%)
Messages in German: 35
References to "Ramadan": 10
Best quote: "I try never to argue against clarity"
Source of quote: Ann
Intrusions by senior staff: 1
Number of times this week I typed a password into IRC: 1
Number of times this year: 3

You may recall that I was enthusiast about a Astronomy, Petabytes, and MySQL at the MySQL Users Conference 2008, and with reason. The engineers at Stanford have a plan of storing petabytes of data into a cluster of MySQL databases.
The technical …

MySQL, and thus currently Drizzle, logs stuff to it's error log. "Stuff" being errors, warnings, and info messages. Inside the code, they ultimately get sent to stderr, which is directed to whatever file is specified by the "log-error" option. It's all in the MySQL documentation at http://dev.mysql.com/doc/refman/6.0/en/error-log.html

I'm changing that in Drizzle, replacing the error logging stuff with a plugin interface.

The first implementation will, just like the current builtin system, write to a file, or to stderr. I expect soon after, plugins that send the messages to syslog, as SNMP traps, and to a CSV table, will be written.

Just like the query logging work, getting this going will shink the drizzle core even more, and likely remove still more unneeded locks.

There are relatively few markets that would benefit more from open source than home automation, with its myriads of different electrical nodes and associated complexity.

It is this opportunity that led to the creation of Marc Fleury and Mark Spencer's OpenRemote project, and that recently led them to release the Beehive database, ...

Well, I suppose its' true you can't use the official MySQL ALTER TABLE statement to do it, but if you're willing to trust your trigger coding abilities you can.All you need is an extra table and a couple triggers.The concept is fairly straight forward:Create a before insert trigger on the child table that validates the parent exists in the parent table.If there is no parent found, then insert a

I know, it's a very short notice. But if you are in or around London next week, you might want to come and visit us at the FOWA Expo. The venue is the London ExCel; some of you should know it, since it's a quite popular that hosts IT and social events.

Check the FOWA Website - http://london2008.futureofwebapps.com - for more details. The schedule is pretty packed with speakers from Amazon, Google, Digg, AOL, SalesForce, BT and many others... and of course from Sun.

As MySQL, we do not have any speech scheduled, but we have a booth and if you have any question or you want to get in touch with us, you are more than welcome to stop by! This time we promise the booth will be less minimalist - check what we had …

I have recently added some features to Maatkit’s mk-table-checksum tool that can make it easy to checksum the relevant parts of your data more frequently (i.e. continually, but not continuously). This in turn makes it possible for you to find out much sooner if a slave becomes different from its master, and then you [...]

I just realized that "Flush tables with Read Lock" will not work when a Select query is not yet done.

What happened was there was a runaway query where it was doing a self-join and aggregating the result. The table was about 10 million rows.

When the backup script ran, it issued the flush tables first but since it saw that a select query was still running, the flush table also waited until the query finished which it never did.

In the end, the backup did not work because of the runaway query.

I'm pretty sure that I have read the previous statement in the manual before but it is interesting when an actual warning / caution from the manual actually happens in production.

Want to promote OpenSQL Camp 2008? Use one of the sweet badges shown on this page. A big thank-you to Fixpert for the logo and badges!

There’s a PNG format and a GIF format. To use the badge, download the image, then save it to your server and use the HTML shown below [...]