I created a new MySQL Forge wiki page entitled "Server Variables" and have started adding content to it. My plan for the page is to get as much information about all the specific server variables as possible, including recommendations for usage, specifications on what is global vs. per-thread, whether it is specific to a storage engine, etc.

I've gone ahead and created a linked page for the key_buffer_size variable, to give folks a starting point for contributions to the pages. The point is not to duplicate the content in the excellent MySQL manual. The point is to expand on that content with community experiences and advice and give a single place to go for tuning information.

Got some good experience on how one server variable affects the server? Put it in there! Got experience on how …

I've fallen victim to the flashing red lights of doom.  Yes, Virginia, my Xbox 360 has died.  And let me just say requiring $129 to fix a known manufacturing issue after 90 days is a total rip.  However I have my stick it to Microsoft card in the form of a 1 year service plan purchased with my Xbox.  So I?m off to find a service center and renew my service contract!

It’s been a hectic week, and it’s only Tuesday.

My wife and I recently made a decision to move on from MySQL. My passion is software development, and my experience doesn’t lend itself well to database development. Therefore, I’m returning to Amazon on Monday, if my intel is correct.

Through a strange series of coincidences, my resume was submitted to the same group which I left 14 short months ago. I will be returning to HTML, JavaScript, Perl, shell script and a tad bit of Java development.

It has been a pleasure working for and with MySQL AB. They make a wonderful database, and their support folks are top notch. I’ll miss them all. But heck, I can stay in touch just as easily as ever. That’s one nice thing about working in a virtual company: you learn to keep in touch by any means necessary.

The roses are blooming. The lawn is mowed. Summer vacation starts Real Soon Now™, and I’ll be taking …

just a few days before reports surfaced that hp would be cutting back on telecommuting, mysql was cited in an article about great teams because we operate without a headquarters. (not quite true, except relative to most companies.)

working from home is great for me, but i can understand how a boss with control issues couldn?t stomach it.

Please share good ideas implemented poorly you have seen.

For example, in the past 24 hours I have come across 2 such beasts:

1) A company doing vertical scaling based on username. Unsurprisingly, they found that 70% of their users had usernames beginning with 1 of 2 letters. A better idea? Do it by last 2 digits of a user id. That way, even though users are created and perhaps deleted all the time, the distribution is effectively random. Language is not.

With 2 significant figures, you can divide vertically many different ways — 1 large table of all the uids, 2 tables of uids ending in 00-49 and 50-99, 4 tables, 10 tables, 25 tables, 50 tables, 100 tables. This eliminates the need for a separate table for each user.

For example, the online dating site I work for uses this method for messaging. So a user’s inbox is just one part of a table. If the user has uid 12345, their “Inbox” is the result of …

I’m sure most would agree when one does a programming mistake they are a lot of times trivial mistakes. However when one stares at the code for long periods of time we seem to go blind and then in the process of frustration loose all logically thinking as to what could be causing the problem. Here is one such problem with arrays.

ShareThis

While I was at the FOSDEM 2006 in Brussels, I got approached by the folks from Source21.nl about performing an interview about MySQL with them. But as David Axmark (who is one of the co-founders of MySQL) was around as well, I quickly directed them to talk with him instead. The vidcast (length is ~10 minutes, the WMV is ~30MB) is now available online in various formats (OGG, MP4 and WMV) from their web site. Have fun.

ApacheCon Europe is the official European conference of the Apache Software Foundation (ASF). This outstanding event creates a unique platform for the Open Source community in Europe to come together to gain deep insight into techniques and methodologies critical to the advancement of Open Source technologies, and gain skills to optimize the power and versatility of Apache software. The event also provides a forum to discuss key issues facing the community and to hear about developments to come in 2006.

At ApacheCon Europe, you can experience first-hand what the ASF technologies and development communities do for you and your enterprise. You will meet the big players, project leaders, inside experts and independent innovators at this annual gathering of all things Apache. Come share your knowledge, hit upon new ideas, find solutions and connect with your peers at this educational, fun-filled gathering of users, developers, and vendors …

Continued work on the backup API. I'm pretty much done with the logic; now I need to look at interfacing, which could take longer. Set up a test server with debug tracing enabled to investigate what happens when the client issues specific commands:

• Build a tree (in this case, the most recent 5.1).

• === grog@eucla (/dev/pts/1) /home/MySQL/5.1-Online-Backup 7 -> cd mysql-test/
  === grog@eucla (/dev/pts/1) /home/MySQL/5.1-Online-Backup/mysql-test 8 -> ./mysql-test-run \
  --skip-ndb --start-and-exit --debug
  Logging: ./mysql-test-run --skip-ndb --start-and-exit --debug
  Installing Test Databases
  Removing Stale Files
  Installing Master Databases
  running  ../sql/mysqld --no-defaults --bootstrap --skip-grant-tables     --basedir=.
  --datadir=./var/master-data --skip-innodb --skip-ndbcluster --skip-bdb
  --language=../sql/share/english/ --character-sets-dir=../sql/share/charsets/
  Installing Slave Databases
  running  ../sql/mysqld …

The German translation of the MySQL 5.1 Reference Manual is complete.