Well, I'm MySQL 5 Developer certified!

But on the official site at the certification pages there's not yet the "Certfied candidates" list of the 5.0 version.

Am I the first one ?

Today I faced with a problem that could arise when dealing with replication.
I had on the master host a table with 534,587 rows and the replicated one on one of the slave hosts with 534,603 rows (16 rows more).
This happened because of some old script that made INSERTs connecting directly to that slave. Unfortunately the replication didn't stop because new INSERTs made by the master host never duplicated entries. I discovered this situation just few days ago.

I wanted to find out how this happened.
I was faced to the problem to determine the IDs of the sixteen phantom-rows on the slave table.

Instead of writing a Perl script (as I would have done a year ago) to read all IDs from master and then find mismatching IDs reading the same values from the slave, I created a Federated table on a non-replicating database (binlog-ignore-db=test in the my.cnf file):

CREATE …

Using stored procedures is a good thing to reduce complexity of PERL scripts.
Since my company switched to MySQL 5 (last month) I started to write some SPs.
But a problem arised.

DBD::MySQL for Perl has a problem dealing with multiple rows statements like simple SELECTs in SP.
So, I was not able to grab results from routines.

As you can see here the problem is well known and a patch was proposed , but at the moment there's no solution. My DBD::MySQL version is 3.0003

So, the only way you can grab the SP's results in a perl script is to store them into OUT parameters and read them through user variables.

Let's see a simple example.

Suppose you have the SP below to count the number of published news articles …