Comments on: Introducing MySQL Duplicate Key Checker

By: Xaprb

Xaprb — Sat, 03 Mar 2007 14:29:18 +0000

Thanks! Yes, it would be great to package for distributions, too. Any volunteers?

By: tom quas

tom quas — Sat, 03 Mar 2007 07:07:47 +0000

Great job! Have you considered providing a package for the Fink distribution? Erm, Debian would be cool, too. Sorry, I don’t wanna make the impression that I’m too lazy to check for new versions and recompile stuff all the time–but in fact I am ;-)

By: Xaprb

Xaprb — Fri, 02 Mar 2007 18:54:46 +0000

Hi Mark! Re the password: yes, I found that too when I tried to use it without a password. It’s already fixed in Subversion.

The second error is more troublesome. Another user reported problems with it trying to scan the ‘lost+found’ database, which appears because of the ext3 filesystem but is not a database. I have also addressed that, and added quoting so strange names shouldn’t cause troubles. This is also in Subversion, but it may not be the same trouble you’re having.

I will follow up with you over email to see what the issue is. Thanks!

By: Mark Papadakis

Mark Papadakis — Fri, 02 Mar 2007 18:45:19 +0000

Greetings,

I just downloaded both the duplicate keys checker and the queries profiler.
There are 2 issues:

First, it won’t allow you to simply not specify a value for, say, the password to access the database. That is, if you provide -p “” or not a password at all, it will ask you for it. I commented out your checks in the perl code, but I think it needs to be fixed.

As for the duplicate keys checker:
DBD::mysql::db selectcol_arrayref failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘database’ at line 1 at ./mysql-duplicate-key-checker line 185.

Nevertheless, they seem interesting and useful. Thank you for making them available for download. Good luck.

By: Xaprb

Xaprb — Fri, 02 Mar 2007 13:42:17 +0000

Someone has pointed out a regression bug from the old version… oops. I’ll release a fix soon. In the meantime, please feel free to put the tool through its paces and give me feedback if you have any! Then I can fix more things at once.