Spent today catching up with the lost data from yesterday. Somehow it's difficult to maintain the same enthusiasm when you're repeating work you've already done, and at the end of the day I wasn't much further than yesterday. Well, not as much further as I had hoped.

I'm still considering how to make the “low-level design” useful. Another problem is that the real issues with most algorithms in complicated products like the MySQL server is not the algorithm itself, but how it interfaces with the rest of the system. Consider a low-level design snippet like this:

  USE dbname;

  /* Stop DDL operations */
  stop_all_ddl ();

  write_backup_header ();

  /* Start the backup threads */
  for each atend engine
    spawn_thread (backup_worker, engine);

This nicely captures what I want to do; we select a database, stop DDL operations, write a header to the output stream, and spawn one worker thread for each storage engine.

That's just funny...
I just had a discussion with Beat, Giuseppe and Markus about the most preferable to write assignments in MySQL.

MySQL has a couple of ways to write an assignment:

inside the SET clause of an UPDATE statement to assign values to database columns

UPDATE sakila.film SET original_language_id := 1

inside a SET statement in to assign values to user defined variables or (in a stored routine context) local variables, parameters and trigger NEW.% values.

SET v_done := TRUE;

inside the SELECT list, where you can assign expressions to …

For the first time since the release of MySQL 5.0 the developers can keep up with the number of bugs reported: During May 2006 a total of 245 new bugs has been opened while 265 reports have been closed.

According to the MySQL Bug Statistics, that's the first month during which more bugs have been closed than opened, since MySQL 5.0 was announced production ready in October 2005. Before last month the number of open bugs had been increasing continuously.

The interesting thing is, that the turnaround wasn't only achieved because the rate of incoming bugs decreased during the last few months, but also because the rate at which reports could be resolved was steadily increased. This could be due to an improvement in bug handling and more work force assigned but also to the decreasing complexity of later bug reports.

This is definitely a major turnaround. There is …

There is many ways to populate vales into a HTML select element. Here is one example I’ve come up with.

PHP Code Example

1
2
3
4
5
6
7
8
9
10
11
12
13
14

      <select size="1" name="szFooBar[]" multiple="multiple">
< ?php
$i=0;
while($obResults = mysql_fetch_row($saResults))
{
    if ($_POST['szFooBar'] == $obResults[0])
    { $szSelectedValue[$i] = " selected=\"selected\""; }
    else { $szSelectedValue[$i] = ""; }
 
    printf("<option value=\"%s\"%s>%s\n",$obResults[0], $szSelectedValue[$i], $obResults[1]);
    $i++;
}
?>                                                   
</select>

…

A recent article at CNN talks about how MySQL operates.

As one of the MySQL team, I can attest that works, but it requires a significant amount of coordination, and lots of online communication through email, IRC, Skype and other methods to keep everbody talking and all the projects working together.

The flip side to that process is that we all get involved in different areas, and you tend to be much more aware of what is going on company wide. There is also better cooperation - because we can all get involved we can all provide our experience and expertise to a wide range of problems and projects. Also, because we come from such a wide range of backgrounds and environments, we have a much wider perspective.

So not only does remote, and earth-wide staffing work, but it provides us with a level of cooperation …

Many of the MySQL team use IBM computers by preference to do their developing on; and I know that, for some, a lot of the reason was the support for Linux.

Now Lenovo owns IBM’s hardware business, but it seems they are dropping support for Linux (that’s a Slashdot link, because, as always, the comments are as interesting as the story).

read more

As some of you may already know, there are plans afoot (actually well underway) to standardize the myriad tools currently used to manage MySQL backup and restores into a generalized online backup API. Those regular readers of SysAdmin magazine will have noticed the excellent dual-part article by Thomas Weeks in the May and June 2006 editions. In both articles, Weeks hints at the online backup API in the works at MySQL.

One of the frustrations that MySQL DBAs currently have is the lack of a consistent, recommended backup strategy that is storage-engine agnostic. Currently, you have a wealth of choices which work best depending on your use of MyISAM, InnoDB, as well as the size of your data set and the downtime interval you can afford.

Greg Lehey, a senior software engineer at MySQL, has been tasked with the design and implementation of a generic online backup API for MySQL. …

“reserved for child molesters and people who talk at the theatre”

(also Malcolm Reynolds if he takes sexual advantage of “Mrs. Reynolds”[1])

I’d like to add to that people who don’t merge their patches.

Special hell.

[1] If you don’t get the Firefly reference you haven’t watched Firefly enough. Go do that. Now. No, you can’t do work first. Firefly, now!

it’s also good to note that this is mostly tongue in cheek. although MERGE YOUR FRIGGEN PATCHES BEFORE PUSHING. Every time you don’t, a cute bunny and baby dies.

One of the things that MySQL is particularly good at it is supporting many different platforms, from Linux to Windows to Mac to really weird flavors of operating systems. In general, our documentation and, especially, our community ecosystem of authors and article contributions does tend to be heavily biased towards the *nix operating systems.

However, download statistics show that a significant (>40%) of MySQL Community Edition server downloads are for the Windows platform. My gut instinct is that a large percentage of these downloads are from developers who use Windows as their main development platform, regardless of whether their production platform runs on Windows.

Over the past six months or so, I have heard a number of complaints regarding the lack of quality articles and documentation that specifically focus on the Windows platform, from either an administrative or development angle. The MySQL forums for …