You know how to build MySQL Connector/C++ and write applications, because you have read my previous post MySQL Connector/C++: compiling, using and debugging. And, of course, its not working. therefore you try the debug trace. Are you capable of handling all the information in it? I am a lamer. The only Vi command I know is ":q".And I know nothing about sed and grep, therefore none of these can help me filtering the debug log. But I know a bit of PHP. I wrote myself a PHP script for filtering MySQL Connector/C++ debug traces when we started working on MySQL …

When Monty Widenius published his criticisms of MySQL 5.1 recently a lot of the coverage that followed focused on his belief that the product had been made generally available too early and has too many serious bugs.

A solution to this problem would have been told hold 5.1 back even longer for more testing or, better still, not to have announced it as a release candidate so early. However, reading Monty’s post in full indicates that this would be a matter of treating the symptoms rather than finding a cure.

He also wrote: “the MySQL current development model doesn’t in practice allow the MySQL community to participate in the development of the MySQL server” and “I think it’s time to seriously review how the MySQL server is being developed and change the development model to be more like Drizzle and …

Sometimes when importing data into MySQL using the following method it can take a very long time, especially if the file is very large in size:

shell> mysql < importfile.sql

I have therefore developed a tiny patch to the mysql client which uses stderr to show the progress of the import in number of lines every 1000 lines of import.  This isn't quite a progress bar but should give you an indication of how long the import will take.

The patch for MySQL 5.1.30 is available here.

Being completely distributed team, meetings are very important for us and this time we went to the Turkey in the end of October (yes, yes I could be faster with sharing photos)

This went we went to Turkey, Antalya region, which is a destination which is very easy to reach from Europe as well as offering great all inclusive deals in the end of the season.

Same as last year we had all spouses/girlfriends and spouses and kids invited to join. I think this was a great tradition of early days MySQL, which Monty and David came up with. Among other things they would finally believe there is a real job real company and real team mates you work with

This year we also missed few guys from the team meeting which had to stay home due to various reason but this is surely majority of the team.

It is fun to compare this picture to one from …

Some recent news of interest:

Sun Microsystems, Inc. today announced the general availability of MySQL™ 5.1, a major new release of the world's most popular open source database. Designed to improve performance and simplify management of large-scale database applications, the production-ready MySQL 5.1 software is available for download now at dev.mysql.com/downloads.

O’Reilly tells me that translation rights for our book, High Performance MySQL Second Edition have been purchased in the following languages: Korean Russian Portuguese Polish Spanish Czech Some of them were sold quite a while ago, and some are more recent. Portuguese was the first. I’m looking forward to learning all these languages (except for Spanish, which I already sort of know) so I can read the book in them… in my copious spare time!

and probably my last one ..

I mentioned a couple of weeks ago that I was looking into a way of converting my static page with published papers, articles and presentations in a more dynamic page where I could create RSS feeds from the updates and feed them into another site for everybody to use.

Some people suggested that I'd have a look at CCK & Views for this. While up till now when creating an app I had usually written my own Drupal module with my own database schema and manually written SQL Queries. This indeed looked like the perfect opportunity to dig into the CCK and Views thingie.

Now I must admit that I`m not really fond of "generated queries"

I've had nightmares before when having to …

I've been working on some new options for ndb_restore which allows to include and exclude databases and/or tables while restoring. The current solution doesn't really work as documented, or isn't flexible enough.

Not really my job, but lots of us in MySQL Support are developers. Doing some coding from time to time keeps one sharp!

How it works? Let me show it with some (simplified) examples:

# only restore db1
ndb_restore --include-database="db1" /dir/.../
 
# only restore db2.t2 (1 table)
ndb_restore --include-tables="db2.t2" /dir/.../
 
# restore the rest of db2
ndb_restore --include-databases="db2" --exclude-tables="db2.t2" /dir/.../
 
# restore db3 excluding db1 and db2
ndb_restore --exclude-databases="db1,db2" /dir/.../

This isn't pushed yet, but if anyone has …

It looks like we're going to meet on Monday, 22nd of December. I'll give a talk on subqueries in 4.1 and 6.0.
I'll post additional information here when I know more :)