In MySQL, not all keywords are reserved words, and because of the way function parentheses are handled by default, function names aren't reserved words either.
Reserved words are nasty, as they can't simply be used for identifiers: database, table, and column names.
I say "can't simply" because you can of course backtick anything and use it as identifier, even stuff with spaces; but that doesn't mean you should ;-)

While working with the OurDelta (and earlier, Percona) builds, I found that the Google patch with the magic SHOW USER|CLIENT|TABLE|INDEX_STATISTICS commands actually produced all those *_STATISTICS keywords as reserved words (see this bug). It shows up easily in v2 of the patch that also makes this info available through INFORMATION_SCHEMA tables. You quickly find there that unless …

I just pushed up a new Drizzle branch at lp:~fallenpegasus/drizzle/newplugins

It contains two new plugin types, one for configuration interface, and one for query cache. Those two are not "plumbed in", and are in fact just templates, containing two dummy entry points with two dummy parameters. But they follow the evolving pattern for plugin types.

It also contains fixes and improvements for the logging and errmsg plugins. The logging engine implementation has parameters for filtering for slow queries and for "big queries", both ones that return a lot of rows, and ones that just examine a lot of rows.

It's all also been internationalized.

There is still lots of work to be done, but it's fun to get this foundation stuff going.

I just read that Toru has a branch he's been working on a query cache plugin interface as well, so we need to work together to stitch all our work …

Download Maatkit

The newest release of Maatkit contains mk-audit bug fixes, lots of new features for mk-table-checksum so you can check replication more frequently (see my earlier post about this), and more bug fixes for other tools.

Here’s the changelog:

Changelog for mk-audit:

2008-10-17: version 0.9.3

* mk-audit died if no /etc/*release file existed (issue 62). [...]

(Note: This post is relevant only if you want to have 'DTr ace' support in the MySQL server. Packages for Solaris are available at http://dev.mysql.com/downloads/.  You can install the MySQL packages for Solaris 10 on Open Solaris)

We shall use the Sun Studio C/C++ compilers and linkers to build MySQL 6.0 alpha on Open Solaris b98 on a x86 system.

1. Grab the MySQL 6.0 alpha tarball from here
2. Extract it

3. Go to the source root, and do the following: (The text following a '#' should be treated as comments)

       $ ./configure --enable-dtrace CC=cc CXX= CC --without-falcon --prefix=/export/home/amit/mysql60-install # MySQL 6.0 alpha contains DTrace probes. To enable it use the flag --enable-dtrace, 'cc' and 'CC' are Sun C …

(Note: This post is relevant only if you want to have 'DTr ace' support in the MySQL server. Packages for Solaris are available at http://dev.mysql.com/downloads/.  You can install the MySQL packages for Solaris 10 on Open Solaris)

We shall use the Sun Studio C/C++ compilers and linkers to build MySQL 6.0 alpha on Open Solaris b98 on a x86 system.

1. Grab the MySQL 6.0 alpha tarball from here
2. Extract it

3. Go to the source root, and do the following: (The text following a '#' should be treated as comments)

       $ ./configure --enable-dtrace CC=cc CXX= CC --without-falcon --prefix=/export/home/amit/mysql60-install # MySQL 6.0 alpha contains DTrace probes. To enable it use the flag --enable-dtrace, 'cc' and 'CC' are Sun C …

(Please note that you will have to build MySQL from sources only if you want to try out the DTrace facilities. Otherwise, binary packages are available for installation) 

We shall use the Sun Studio C/C++ compilers and linkers to build MySQL 6.0 alpha on Open Solaris b98 on a x86 system.

1. Grab the MySQL 6.0 alpha tarball from here
2. Extract it
3. Go to the source root, and
   1. ./configure --enable-dtrace --prefix=/export/home/amit/mysql60-install CC=cc CXX=CC --without-falcon
      
   2. make
   3. make install

Note:

Please make sure that the location of the Sun tools are ahead in your PATH. GNU tools should be located later in the PATH. For eg.

…

I’m speaking at the MySQL European Customer Conference this week (Thursday, 23rd), on the topic of the best deployment practices for using MySQL on Solaris.

I’ll be covering a number of topics, including:

• Overview of MySQL availability on Solaris
• General tips for MySQL on Solaris
• MySQL on ZFS
• DTrace and the new DTrace Probes
• Using MySQL with containers and zones
• Using Sun Cluster and MySQL Cluster for HA

Some of the material I’ve already covered before (see my presentation at the London Solaris User’s Group, but most of the content will be new and more focused than the top level …

The newest release of Maatkit contains mk-audit bug fixes, lots of new features for mk-table-checksum so you can check replication more frequently (see my earlier post about this), and more bug fixes for other tools.

If we get enough good submissions by them, we won't extend. Meaning that if you were counting on an extension to send your proposal, it may be too late.

Of …

This poll was posted last week on Arjen’s blog and is still open for a few more days to receive your vote. The comments on the original post contain some interesting considerations either way, and many in fact non-technical. Anyway, please add your vote, and optionally your thoughts to the comment thread!