I woke up this morning to a nice surprise. Peter Zaitsev from MySQL Performance Blog mentioned my fix for a crash in MySQL. Thanks Peter! That reminded me that I need to write this post about another fix.

A storage engine is called a “handler” in MySQL internals. Handler events are per row at the storage engine layer. For example an insert query that inserts 3 rows will cause one Com_insert increment and 3 handler_write increments. The way these statistics are implemented the storage engine is responsible for incrementing statistics itself. Innodb is missing function calls to increment the handler_delete and handler_update status variables. I’ve filed …

On March 4th I wrote about an observation we made concerning InnoDB locking behavior in combination with foreign key constraints. Since then we have been in contact with MySQL support and they in turn with the InnoDB developers. One of the conclusion I can already draw from the whole thing is that another level of indirection (InnoDB being a part of Oracle, i. e. an external resource to MySQL,

To be really successful at working with databases, there are many different disciplines to become proficient in - things like disaster recovery, security management, data integration, and more. But there are less than a handful of things you want to be really good at; becoming super-skilled in them will help you enormously in your database career. And believe it or not, one of these key areas is data modeling and its kissing cousin, physical database design.

In reviewing some of my notes I thought it was relevant to ensure this small MySQL gem is documented for my history purposes.

Historically I’ve seen people do a complex SELECT statement twice, first to get a COUNT(*) and then to retrieve the data, perhaps in a paginated format. In MySQL you can combined both SELECT statements into 1 SQL. You still need a second SQL statement, but it is less impactful to your system.

Here is how?

mysql> select sql_calc_found_rows * from mysql.user limit 2;
...
2 rows in set (0.01 sec)

mysql> select found_rows();
+--------------+
| found_rows() |
+--------------+
|            5 |
+--------------+
1 row in set (0.00 sec)

Shortly after getting RC1 out we have now released RC2. We fixed a few issues that were reported after RC1 was out, thanks for that! In addition to that we included a first version of the GRT Scripting IDE that will play a key role for the MySQL Workbench community in the future.

The GRT Scripting IDE allows to easily create scripts, libraries and modules that extend the core Workbench functionality. We will add detailed documentation and tutorials that will get people started. Vlad is hosting a tutorial on this topic at the upcoming MySQL Users Conference as well.

We also plan to create an online repository where people can share their Workbench extensions - think Firefox Extensions - but also including things like diagram-snippets, sample models and much more.

Please give RC2 a try and report your findings on the forums or via the bug system.

…

As half of the world population already knows, the MySQL conference is coming in less than 3 weeks. Since this event only happens once a year, lasts only 4 days, and costs more than a Russian mail-order bride, I'd really like to get the most out of it. Considering that the schedule is completely packed, with 8 (!!) events going on in parallel, I imagine things can get a little frantic. Additionally, I've never been to a conference of such size before and I'm not sure what to expect.

…

LugRadio is possibly the best Linux/Free Software related podcast out there - and it has been for a very long time. LugRadio Live is a live event where lots of people gather together to love freedom.

This year, there’s a LugRadio Live USA - and it’s in San Francisco. So, are you going to be (or are able to be) around SF the weekend before the MySQL UC? If, there is no excuse not to drop in on LugRadio Live USA - it should be awesome! (oh, and it doesn’t cost much… like $10 or something)

I attended the MySQL-Sun cocktail party yesterday (March 25, 2008) at the Jillian's @ The Metreon (101 Fourth Street, San Francisco, CA).

As you may have seen from his blog, Baron Schwartz is joining our consulting company - Percona in less than a week. This is exciting news for us as Baron is renowned MySQL community member, blogger, co-author of High Performance MySQL second edition book, author of Maatkit and Innotop and just a great guy.

Welcome Baron - We're proud to have you onboard.

So if you always wanted to hire Baron to take a look at your system and help you with high availability scaling optimization or other needs you can do it now by filling out our consulting request form

Entry posted by …

While recently migrating Tschitschereengreen.com from Symfony to Django plus changing the database backend from MySQL to PostgreSQL, there were mainly two tasks more time-consuming than I’ve had thought beforehand:

SQL dump

The old database used a latin1 encoding for the database fields and utf-8 as the server and client connection encoding. With these settings, even trying to get a correctly encoded database dump from phpMyAdmin is a bad idea.

Using mysqldump with an explicitly specified character-set is much better:

mysqldump ? ?default-character-set=latin1 …