MySQL 5.6.2 is available for your evaluation at Labs.MySQL.Com –

MySQL 5.6.2 ready to go

in three flavors — InnoDB-Memcached, New Performance Schema, or multi-threaded slave. Remember, these servers are for evaluation purposes and not for production. I downloaded the InnoDB-Memecached version on a Fedora system and the New Performance Schema on a Ubuntu system. Both downloads were the pre-built generic binaries.

Installation will be familiar to anyone who has installed the binary sever before and is covered in detail at Installing MySQL from Generic Binaries on Unix/Linux

shell> groupadd mysql
shell> useradd -r -g mysql mysql …

The MySQL Sandbox tool is a fantastic way to evaluate and install different versions of MySQL. Often when new versions of software come out people tend to be very nervous to upgrade and test with their current stable server environments. You just might not be able to take a risk and upgrade a development or slave servers to test evaluate a new version.   Giuseppe Maxia “The Data Charmer” has built the MySQL Sandbox (http://mysqlsandbox.net/) to help you avoid these risks. This is just one of the many things Giuseppe does for the MySQL community.

Code is available via Launchpad or …

Dear Perl and MySQL enthusiasts,

I’m pleased to announce the release of DBD::mysql 4.019. I’m especially pleased because there are some new enhancements and features that have been provided by contributions from the community:

* Asynchronous support, added by Rob Hoelz. This is a new feature to DBD::mysql that takes advantage of libmysql’s asynchronous functions (see Jan’s article from 2008 http://jan.kneschke.de/2008/9/9/async-mysql-queries-with-c-api/) . From the DBD::mysql documentation:

You can make a single asynchronous query per MySQL connection; this allows
you to submit a long-running query to the server and have an event loop
inform you when it’s ready. An asynchronous query is started by either
setting the ‘async’ attribute to a true value in the DBI do() method,
or in the DBI prepare() method. Statements created with async set …

Version 1.3 of Slave read-Ahead is available for download. If you don't know what this tool is about, it is a tool that runs in the background, reads the incoming replication log on a slave and converts INSERT, UPDATE and INSERT ... SELECT statements into SELECT statements and executes these before the statement in question is executed on the server, the idea being that this will "prewarm" the MySQL caches for this date, for example the rows that an UPDATE is affecting will already be in the cache when the UPDATE arrives on the slave. Because of the way replication data is read, this tool only works with MySQL5.5 and up.

Version 1.3 introduces the auto-reconnect feature. This will reconnect to the MySQL server if the connection fails. To be sure that we restart, all existing connectings are released before a reconnect attempt is made. This version also has …

Permalink: http://bit.ly/TBKQL3



Skip to part 2 for the code snippet or to part 3 for a working example and how to debug the stored procedure.

Also another workaround on a missing MySQL functionality, enabling/disabling triggers, can be found here.

As of version 5.5, MySQL still does not have the native ability to execute a dynamic cursor. This can be worked around but the resulting stored procedure will have a few limitations.

This stored procedure is a general purpose …

A couple of years ago Domas Mituzas created a tool which could basically be thought of as basically a lightweight multi-threaded mysqldump.  By this I mean it can retrieve data from multiple tables simultaneously and can even break a table down into parts for simultaneous retrieval.  Sometime around 2010 I started hacking on mydumper too but stopped whilst working at Rackspace (Drizzle was way more than full-time for me).

Back when Domas first blogged about it he was managing to dump his sample data over 10x faster than mysqldump!

Since the 0.1 series Domas has fixed a lot of problems and since starting at SkySQL I have finished a lot of work that I …

Photo by Pockafwye under a CC by NC SA 2.0 license

A couple of years ago Domas Mituzas created a tool which could basically be thought of as basically a lightweight multi-threaded mysqldump.  By this I mean it can retrieve data from multiple tables simultaneously and can even break a table down into parts for simultaneous retrieval.  Sometime around 2010 I started hacking on mydumper too but stopped whilst working at Rackspace (Drizzle was way more than full-time for me).

Back when Domas first blogged about it he was managing to dump his sample data over 10x faster than mysqldump!

Since the 0.1 series Domas has fixed a lot of problems and since starting at …

A customer had an interesting (and rather urgent) request recently. I thought I'd share as it might be of interest to someone else.
The issue was something a lot of us have run into, a query that was never supposed to be run. This time, it was a rather devestating "DELETE FROM table_a;".
The only backup available was made several hours AFTER the erronous statement, so what we had left to work from was the table_a.idb file. Based on file size alone, it should contain most of the data, so we set to work.
This was a job suited for the Percona InnoDB Data Recovery Tool.
Getting the table definition from my customer, I created an identical table on a local mysql server then used the create_defs.pl script to create a table_defs.h file.
$ ./create_defs.pl --host=localhost --user=root --db=test --table=table_a > table_defs.h …

I've got interviewed on authentication API :)

Read all about it here

I've got interviewed on authentication API :)

Read all about it here