Event Schedulers are "temporal" triggers.

More at http://dev.mysql.com/doc/refman/5.1/en/events-overview.html

One way to look at a database is that

1. 
   
2. there is data, and
   
3. there are ways to access data.
   

This dichotomy was actually coined (whether intentional or not) by Vinay in the MySQL telecom team when discussing the MySQL Cluster vision some months ago.

Even if you typically think of MySQL Cluster as just a clustered version of the plain old MySQL server, it is actually more like the opposite is true, if you consider the architecture and history of MySQL Cluster. The original cluster was just the data store called Network DataBase or NDB as we familiarly know it still. Then MySQL Server was integrated on top of that to provide an SQL interface. The original and "native" NDB interface is still there though, and many prefer to use direct C++ or Java access to their …

This week I've worked with the customer doing certain work during maintenance window which involved a lot of data copying around between MySQL boxes. We had prepared well and had measured how fast we could copy the data between servers of these kind connected to the same network, and we did the same thing before. Using simple tar+netcat based copy we can get 80-90MB/sec on 1GigE assuming RAID is powerful enough. This applies to large Innodb tables with not overly fragmented tablespace, or it is easy to become IO bound rather than network bound.

As I mentioned you can get even better with using fast parallel compression like LZO or QuickLZ but there was no need in this case.

So estimates were great but once we had started the real copy process we saw the copy speed about …

One way to look at a database is that

1. 
   
2. there is data, and
   
3. there are ways to access data.
   

This dichotomy was actually coined (whether intentional or not) by Vinay in the MySQL telecom team when discussing the MySQL Cluster vision some months ago.

Even if you typically think of MySQL Cluster as just a clustered version of the plain old MySQL server, it is actually more like the opposite is true, if you consider the architecture and history of MySQL Cluster. The original cluster was just the data store called Network DataBase or NDB as we familiarly know it still. Then MySQL Server was integrated on top of that to provide an SQL interface. The original and "native" NDB interface is still there though, and many prefer to use direct C++ or Java access to their …

One way to look at a database is that

1. 
   
2. there is data, and
   
3. there are ways to access data.
   

This dichotomy was actually coined (whether intentional or not) by Vinay in the MySQL telecom team when discussing the MySQL Cluster vision some months ago.

Even if you typically think of MySQL Cluster as just a clustered version of the plain old MySQL server, it is actually more like the opposite is true, if you consider the architecture and history of MySQL Cluster. The original cluster was just the data store called Network DataBase or NDB as we familiarly know it still. Then MySQL Server was integrated on top of that to provide an SQL interface. The original and "native" NDB interface is still there though, and many prefer to use direct C++ or Java access to their …

Marten Mickos, who runs the MySQL business inside of Sun, will be featured next week on Sun's "Innovation Insider" interactive web radio show.  Marten will be talking about the upcoming Software Feedom Day (September 20), business & technology innovation, MySQL 5.1, Swedish drinking songs and more.  Best of all, Marten will be available to answer the questions you post to the show.  The show is live Thursday September 4 at 12:30 pm pacific time and will be available for replay.

I have challenged Marten that he should do the show in a penguin suit to show our commitment to all platforms, but since it's radio, it may be hard to tell... 

• Blog Talk Radio: …

I am pleased to announce that the Beta version of PBXT has just been released. You can download the source code of the storage engine from www.primebase.org/download. I have also updated the documentation for this version.

Configuring and building the engine is easier than ever now. To configure PBXT all you have to do is specify the path to the MySQL source code tree (after building MySQL), for example:

./configure --with-mysql=/home/foo/mysql/mysql-5.1.26-rc

The PBXT configure command will retrieve all required options from the MySQL build. For example whether to do a debug or optimized build and where to install the plugin are determined automatically, depending on how you configured MySQL.

This was a source …

I recently needed to configure mysql failover on some of our test machines. Thanks to Sheeri’s helpful blog entry which provides a simple failover lua script, configuring failover is a simple matter. However, the machines are running centos-5.2 and centos doesn’t provide an rpm for mysql-proxy. This blog entry describes how to build your own.

The latest mysql-proxy (0.6.1) is apparently not backward-compatible with 0.6.0 and earlier. It incorrectly handles the case when one of the backend machines is down. Instead of just marking it as down, it errors out completely. This makes it rather difficult to use it for failover scenarios. People have complained about this for a while. Bugs 34793 and …

On August 22 2008, after reading a post by Lewis Cunningham, I did for the first time a quick evaluation of iCloud, an Internet Operating System by Xcerion.

From a User prospective, an O.S. is a set of applications and a kernel - i.e. the basis on which other applications run. An Internet O.S. is an O.S. that runs in the cloud. You have to image a Desktop with its own icons and a “start” toolbar - running on your browser.

When you double-click on an icon the application linked by that icon will be opened. You can move the window, resize it, maximize it and minimize it - all within your browser.

If you maximize you browser (F11 if you use Internet Explorer) an external …

Flying to Auckland this arvo (that's afternoon in Aussie ;-) for a week and a bit. If you would like to catch up, have dinner, talk MySQL, Drizzle, Open Source in general, smart business innovation, or any other interesting stuff, drop me a line or SMS (not call please I might be teaching) +61-438 210 269. I'll have transport.