mysqlreport v3.0a has been released which fixes a bug on line 93:

chomperc($mycnf{’pass’} = <STDIN>);

should be just

chomp($mycnf{’pass’} = <STDIN>);

Thanks to jeroen for pointing this out to me. This bug caused mysqlreport to die when using –pass to prompt for a password:

Undefined subroutine &main::chomperc called at mysqlreport line 93

In other news: thanks also to Aurimas for some technical clarifications in the mysqlreport Guide about temp tables.

mysqlreport v3.0 has been released (v2.8 & v2.9 were skipped) which finally has InnoDB reports for MySQL servers v5.0.2 and up. The documentation has been updated accordingly. The new options that invoke the InnoDB reports are –innodb (or -id), –innodb-only (or -ido), and –dpr (for the extra Data, Pages, Rows report).

Since this is the first release with InnoDB reports, feedback on the InnoDB reports is appreciated. Eventually, I’ll update the mysqlreport guide to explain the InnoDB reports. For now, I think the InnoDB reports are self-evident to those who know a little about how the …

mysqlreport v2.7a has been released. It only fixes one bug: –host was completely ignored if a socket was available. Thanks to Sam for pointing this out to me.

mysqlreport v2.7 has been released. This version sports the following changes:

• Option “password” in ~/.my.cnf now recognized (used to be that only “pass” was recognized)
• Options host, port, and socket now recognized in ~/.my.cnf
• Given those two changes, the order of option precendece is such that ~/.my.cnf is read first, then command line options override ~/.my.cnf options, and if nothing else default values are assigned
• –all actually shows all reports now (i.e. no more need to –all –tab)
• Like mytop, mysqlreport tries to connect via a socket first, otherwise it tries via a network connection

Thank you to those who provided patches for these changes, although I wound up writing the mods myself for various reasons. To …