Today, 24 March 2008, the student application period opens. And it remains open for a week, until 31 March 2008, presumably at one minute before midnight UTC.

If you haven’t already discussed the MySQL related ideas published on forge.mysql.com/wiki/SummerOfCode2008Ideas, do so now.

A good place to first silently lurk in and then actively participate in is lists.mysql.com/soc.

As opposed to last year, you can now also apply for MySQL Worklog Items Open for Community Development listed on forge.mysql.com/wiki/ComContribution_Worklog. Worklog items are internal “todo items” or coding tasks identified (but not yet necessarily being …

If you are part of a big company and would like to recommend to them a list of open-source and cheap commercial alternatives, I have compiled a list that I use for my company.

These options might make your company more competitive in certain markets and might let you react faster to changes.


Here is the list:

Database - DataWarehouse
InfoBright - Commercial DataWarehouse Engine (highly recommended) that runs inside MySQL. review about it

EnterpriseDB - Commercial Enterprise Scale Database that runs inside PostgreSQL

Vertica - A very high-scale, …

MySQL has a reputation of being a lightweight database. This definition can be intended either as having limited features or as requiring little hardware.

In my experience, I have seen MySQL used in quite heavy load situations, and thus I will discard the first meaning of lightweight. As for expensive hardware, my own experience is mixed. Yahoo! and Google have shown the world that using an array of inexpensive boxes in replication is often the most sensible way of scaling. However, there are many users who don't feel comfortable with replication, and therefore buy more iron when their current box has reached its limits. Sometimes, an upgrade could be avoided by proper configuration, but this is beyond the point. Given the choice, what is your favorite hardware for MySQL?
There is a …

The work on subquery optimizations goes on, and we're already curious how the assortment of new 6.0 subquery optimizations compares to what is found in other DBMSes. MySQL's new strategies are not DBMS theory breakthroughs, similar ideas have been implemented in other DBMSes, but when you take this list of strategies and put them into this kind of optimizer, the result has no direct equivalents in any other DBMS (or at least we believe so).

The first thing we did was to take a look at PostgreSQL as it is easily available and seems to have at least decent subquery handling (or even better than decent, I have not heard much complaints). And the first interesting difference was handling of correlated subqueries. With exception of materialization, MySQL's new subquery strategies do not care if the subquery is correlated or not.

For example, …

While working with a client we found a query that can crash MySQL. It has to do with ref_or_null outer joins where the table contains a null value. MySQL fails to tell the storage engine to initialize the index before reading from it. It crashes when used with MyISAM tables but it could result in an incorrect key file for table error with other storage engines. You can find the test case and patch in bug #34945. I’ve waited to blog about it until MySQL approved my patch. As of this writing my patch has been approved and committed for release in 5.0.60.

Apache is a fairly straight forward setup if you use some utility or distribution to help you. A manual installation will take more time. You can Google installation instructions or use a utility like XAMPP to simplify the installation. XAMPP is a distribution that will walk you through an Apache, MySQL, PHP, phpMyAdmin installation. Once you get comfortable with XAMPP these software

The Conference Speakers of the 2008 MySQL Conference provides some common and interesting names of companies not common in MySQL circles such as eBay, Microsoft Corporation, HP, Symantec. I see speakers outside of MySQL from countries including USA, Canada, Brazil, Germany, Japan and Australia.

I did some data analysis of the speakers list. There are 150 speakers, there are 45 from MySQL. Other companies with multiple speakers include Sun Microsystems, Kickfire, Linbit, Cafepress, Open Query, Proven Scaling, Standford Linear Accelerate Center, UC Berkeley, Siz Apart, The Hive, Zmanda, MySQL Performance Blog, Infobright, Digg, Grazr and of course PrimeBase Technologies.

Only two MySQL speakers have listed “MySQL/Sun” the rest are “MySQL”. I wonder what the policy is here? You have “Oracle / Innobase” and “Innobase / Oracle Corp.” …

Following A day with Jan Kneschke - Architect of MySQL Proxy, today I’m with Michael Zinner in Vienna, Austria. Michael is Team Lead of the MySQL GUI tools team at MySQL.

I met Michael two years ago the 2006 MySQL Users Conference. We had communicated prior to that and I’d even used his very successful DB Designer a number of years prior to this. The present project of the GUI team is the MySQL Workbench which is a beta release.

Again, I find a key MySQL developer using a Mac, this time as …

I’ve been accepted to speak at the upcoming 2008 OSCON Conference in Portland Oregon July 21-25 2008, where I’ll be speaking with Giuseppe Maxia on MySQL Proxy. I haven’t seen a schedule yet, so I’m interested if there are any other presenters on MySQL topics!