What happened with the MySQL Winter of Code? It was hit by Global Warming. Specifically, the Community Team got heated up working on the MySQL Conference & Expo 23-26 April 2007, left with little bandwidth to pursue the ideas and action items for Winter of Code.

When winter warms up, it slowly turns into summer. But the coding work remains. Colin Charles was smart enough to combine these two facts with Sheeri Kritzer’s blog entry and hints about the Australian Winter, and took action related to the Google Summer of Code. Colin spoke to Chris DiBona and Leslie Hawthorn of Google and has now signed us up for Google Summer of Code.

In short: …

Its that time of the year again when time changes and we have to make sure our servers are using the right zone with right time. Out of many servers I admin, I found 3 servers which had wrong time displaying. All of them had one thing in common, Fedora Core 4. So I fixed it by doing the folowing.

mv /etc/localtime /etc/localtime.old

ln -s /usr/share/zoneinfo/PST8PDT /etc/localtime

March 12, 2007 -- The schedule is nearly complete for the 2007 MySQL Conference & Expo, happening April 23-26 at the Santa Clara Convention Center in Santa Clara, California. This year's program promises to be the most exciting ever, offering more than 110 sessions and workshops for every type of user -- from experienced database administrators and programmers to MySQL beginners. Attendees who register by March 14 will save $200 off the standard fee. Other discounts are also available that may be used in conjunction with early registration for additional savings.

So, within MySQL it's not 'allowed' to release or name anything prefixed with 'My' (but MySQL of course). An example is MyODBC doesn't exists anymore, it's Connector/ODBC.

But you see lots of successful MyThis and MyThats.

• 
  
• MySQL.com (duh)
  
• MySpace.com
  
• MyVideo.de
  
• MyWunderwelt.prosieben.de
  

Bah, anyway, there are lots of them of course. What's 'yours' on the net?

In August 2006 I made a post about the MySQL blackhole engine and its possible use for replication scenarios.

Back then the primary focus was to reduce the amount of data being transferred between master and possible many slaves during normal business. This speeds up processing on the slaves, because they have considerably less data to first store to their relay logs and then immediately discard again.

What still takes a lot of time is the initial setup of a slave system. This is because there is a potentially large SQL based dump file to be executed on maybe relatively low-end systems (e. g. Celeron CPUs and single IDE hard drives). While this can be made to work reliably with a set of scripts to automate the process of downloading a zipped SQL file from a local server and running it against the clients' databases, it …

In August 2006 I made a post about the MySQL blackhole engine and its possible use for replication scenarios.

Back then the primary focus was to reduce the amount of data being transferred between master and possible many slaves during normal business. This speeds up processing on the slaves, because they have considerably less data to first store to their relay logs and then immediately discard again.

What still takes a lot of time is the initial setup of a slave system. This is because there is a potentially large SQL based dump file to be executed on maybe relatively low-end systems (e. g. Celeron CPUs and single IDE hard drives). While this can be made to work reliably with a set of scripts to automate the process of downloading a zipped SQL file from a local server and running it against the clients' databases, it …

There’s a lot of things about the MySQL bug tracking system i like… but there’s a few things that annoy the heck out of me.

Today it’s the fact that if you put a term in the “with any of the words” field on advanced search that’s an number (e.g. ‘839′ as you’re looking for bugs that talk about error 839) you get taken to bug numebr 839. Funnily enough, this has nothing to do with an NDB problem I’m trying to see the status of. grr…

and now, back to your regular programming…

So, within MySQL it's not 'allowed' to release or name anything prefixed with 'My' (but MySQL of course). An example is MyODBC doesn't exists anymore, it's Connector/ODBC.

But you see lots of successful MyThis and MyThats.

• 
  
• MySQL.com (duh)
  
• MySpace.com
  
• MyVideo.de
  
• MyWunderwelt.prosieben.de
  

Bah, anyway, there are lots of them of course. What's 'yours' on the net?

Back around November 2005, I started working on query profiling in MySQL via the SHOW PROFILE and SHOW PROFILES commands. It’s been an interesting ride, but profiling support is finally available in public releases of MySQL starting with MySQL Community 5.0.37!

I had a few thoughts on the process and the feature that I’d like to share:

It’s been rough — Although everyone at MySQL who had seen the patch had wildly positive feedback about it, it took almost a year and a half to get things committed. Chad Miller took up my cause (back in December?) with the profiling patch as well as many others, and things actually started making progress. …

I am a fan of using GUIDs as primary keys. They are database
independent, object independent and I can either create them in my
application or in the database (MySQL since 5.0 has had a UUID()
function but since it does not replicate I don't use it normally...
this has been fixed in 5.1 though).

What I have heard for years was that Innodb didn't handle them very
well. I have had my doubts, but never taken the time to see if this
was true or not.

This week I finally got around to putting this to a test.

/mysqlslap --concurrency=1,50,100,150,200,250,300 --iterations=10 --
number-int-cols=2 --number-char-cols=3 --auto-generate-sql --auto-
generate-sql-add-autoincrement --auto-generate-sql-load-type=update --
auto-generate-sql-execute-number=10000 --auto-generate-sql-unique-
write-number=10 --auto-generate-sql-write-number=100000 …