We've added some new options in MySQL Cluster 6.3.22 which makes it possible to selectively restore tables. The new options for ndb_restore are:

  --include-databases=name 
      Comma separated list of databases to restore.
      Example: db1,db3
  --exclude-databases=name 
      Comma separated list of databases to not restore.
      Example: db1,db3
  --include-tables=name 
      Comma separated list of tables to restore. Table name
      should include database name. Example: db1.t1,db3.t1
  --exclude-tables=name 
      Comma separated list of tables to not restore. Table name
      should include database name. Example: db1.t1,db3.t1

To demonstrate in a few examples, lets assume you have the following tables:

 mysql> SELECT …

Wondering really what happened at MySQL? And how it happened? And when Sun Microsystems acquired us? Well, that story in it's entirety still remains to be told, although there is at least one book on the subject.

But what I wanted to Blog on here is a similar situation, way back, that actually has been documented, and not by some anomymous writer, but by someone, and a technical person, who was actually there. The subject is the growth of the very early years of commercial computing, more specifically Univac (later Sperry, later Unisys), CDC (Control data) and Cray. The story is told by David E Lundstrom in the book "A Few Good Men from Univac" (ISBN 0-262-12120-4). This is a highly entertaining and interesting book, and the story has many similarities to what goes on here at MySQL / Sun these days. As some of you has probably noticed, there is a certain amount of political game going on here at MySQL / Sun, but that was expected, and …

CodeGen_MySQL_Plugin had basic support for status variables (for SHOW STATUS) for quite a while, now it also has basic support for system variables (SHOW [GLOBAL|SESSION] VARIABLES, SET) in the 0.9.2 package version i just released as well

Continue reading "MySQL Plugin generator now supporting system variables"

“Groovy, baby!”, as international man of mystery likes to say.

It seems converting character and text data to utf8 character set is a common task for MySQL, especially during an upgrade. In fact, I had trouble with it during server and WordPress database upgrade for this blog site. I wrote about it in this post, where I explained how to do it step-by-step using a command line tool such as mysql, taking advantage of some nifty code generation trick with information_schema.

One drawback of that method is that it’s a manual process, therefore time-consuming and error-prone.

I spent some time today to cook up a simple Perl script to automate this task. See below. Remember to change MyDatabase to your database name (there are 3 places that need to be changed), and adjust the user name and password accordingly. This …

I see my collague Anders wrote some thoughts on date handling in MySQL. I recently had to explain this really down to fine details for a customer, so Anders, everyone else, here's my conclusions...

All the fine details of allowed ways to enter dates are explained here:
http://dev.mysql.com/doc/refman/5.1/en/datetime.html

With dates, just as in many other cases, MySQL is very flexible in how you can input data. But one thing is that, between the multitudes of formats that are allowed, MySQL does *not* by default allow you to enter a non-existant date, e.g. "31st of February 2009". I know some other DB products allow that - they then store it as a correct date automatically (3rd of March 2009). This is mentioned at the end of …

General

Being quite busy with my full-time job at PrimeBase Technologies and quite limited in time for QOT development I was looking for ways to optimize the process around QOT.

I came to a conclusion that instead of preparing and releasing milestone binary releases it will be more optimal to declare the main project trunk to be the permanent release place and “release” the new features and bug-fixes by simply pushing them to the main trunk. This way I will be able to make individual features and bug fixes available as soon as possible. So

to install QOT for the first time you do:

1. install Bazaar

2. run “bzr branch lp:qot” from the shell to get the latest stable QOT sources

3. follow the usual QOT …

During the last few months I was the only person working on the MySQL packages in Debian, and I could really need some help. Currently there is MySQL 5.0.32 in etch, 5.0.51a in lenny, 5.0.75 in unstable and 5.1.31 in experimental, and I am also trying to get MySQL Cluster and MySQL Workbench into Debian. All in all it is way too much work for only one developer.

If you are an interested Debian developer/maintainer with a good knowledge in MySQL and shared library packaging, drop me a mail.