The latest from the MySQL community

Supplementary Characters
MySQL 6.0 New Features Document#1
2008-04-20

MySQL 6.0.5 is about to appear on the “MySQL 6.0 Downloads” page http://dev.mysql.com/downloads/mysql/6.0.html

This is MySQL’s alpha version, not to be confused with MySQL 5.1, which has been ‘release candidate’ for a while. The big 6.0 features are “online backup”, “Falcon”, and “supplementary characters”. This document is about the new supplementary characters feature.

What

Since MySQL 4.1, MySQL has supported two Unicode character sets, ucs2 and utf8. Luckily we don’t have to explain all about “Unicode” because there’s good definition and explanation. So if you need help with Unicode in general, read here:
http://www.unicode.org (Unicode reference)
or here:
…

At the moment, there are two big features in the works in MySQL optimizer - Subquery optimizations and Batched Key Access. While the former is a part of MySQL 6.0, I wrote about it here in my blog, and so forth, the latter was in nearly stealth mode until a couple of weeks ago.

That's no longer the case:

• Batched Key Access source code is now published as mysql-6.0-bka-preview tree.
• Igor Babaev, the author of the feature, gave a talk about Batched Key Access at MySQL User Conference, and the slides are available here.
• There is now …

I do not know if anyone noticed this; but there was an incompatible change from MySQL 5.1.22 to 5.1.23 in mysql_com.h file for NET structure by renaming the members last_errno and last_error to client_last_errno and client_last_error. This is really annoying as it not just breaks the compilation of lot of depending applications; and functionality will be annoy if one uses the wrong client library as there is no protocol version change. The change should have been done in …

For you, Fabrizio. All this talk about MySQL walking a tightrope got me hungry. So, on a pleasant stroll around Brussels I came across this little shop.

Not sure how well he walks the tightrope, but les gaufres...? Magnifiques!

I would be a very fat man if I lived in ...

Since Oracle announced the InnoDB plugin which provides compressed row formats, I thought I'd do this comparison again.

Here are some more data that I've cobbled together.

I've created a 2M row table with a schema that we use for audit data. It has 47 columns and 17 indexes.

I copied the table into new empty tables using INSERT ... SELECT with each of these engines:

• InnoDB row_format=compressed (from the InnoDB plugin)
• InnoDB row_format=Compact
• InnoDB row_format=Redundant
• MyISAM pack_keys=1
  
• MyISAM packed with myisampack (NOTE: these tables are readonly)
• PBXT
• Falcon

Here are …

Thanks to Jay Pipes and the conference team for putting together a great event and especially the top-notch keynotes. I think this is one reason we had such large attendence this year with more than 2,000 attendees. Also thanks to all the bloggers, speakers, session buddies, community members, users, boffers, drinkers, runners, sales people for bringing customers, alliance guys for getting sponsors, to engineering for shipping great products, marketing for promoting the conference, consultants for having great solutions, SEs for keeping us honest, support guys for meeting with customers and more...

There are some great conference photos from Duncan Davidson available on Flickr, including the one above of our community awards.

For a couple of months there have been no updates to our msl patch, however recently I managed some time to change this. The functionality was extended a little bit and what?s even more important the patch is available for all the recent MySQL releases.

To remind anyone who has not yet come across this piece of code. msl (microslow) patch was developed a few years ago to allow more precise logging of query execution times into the slow log. Originally MySQL database offered a second time resolution and also a 2 second minimum for the query to get written, that is when you set long_query_time=1. After applying the patch you could see whether the time was 0.005s or 0.9s, which can make a substantial difference for the database and application performance. Over time msl patch grew with new features to let people learn more details of query execution, normally hidden from everyone's eyes. Currently it?s used by many DBAs and developers to help …

It occurred to me today that open-source infrastructure providers (e.g., commercial providers of open-source operating systems, databases, application servers, etc.) may have much in common with telecommunications infrastructure providers (like cable, wireless, etc. providers).

Everyone uses their stuff, and generally at a rate that doesn't quite match the value of the benefits derived from it.

Early on we pay a premium for broadband Internet or support for still-buggy but cheaper open-source software. Over time it becomes commodified and our willingness to pay decreases.

What's a company to do?

...

As I'm occasionally reminded, MySQL didn't start out as open source. In fact, MySQL's original license was very similar to what it is trying to achieve today: Free for noncommercial use, but not-so-free for commercial use. It didn't decide to go open source (GPL) until 1999.

So for those of us that get caught up in MySQL's decision to keep some extensions closed to paid subscribers, perhaps a refresher course in MySQL history will make it seem a bit less shocking. (Also be sure to check out the early 2001 brouhaha over trademark violations surrounding MySQL.org. Fascinating stuff.)

With that said, there's an ongoing tension between commercialization and adoption that MySQL (and …