I have a sob-story and a cautionary tale to relate ...
 

The problem: Leave a maintenance problem for long enuff and BOOM!

350-odd emails arrive in my inbox with SQL errors (after a convenient 72 hours of intermittent net access due to my ISP having their collective heads up their collective orifices)

One or more of the tables in the database needed repairing - due to a bug in the version of MySQL that we have on the server ... [a good reminder for me to run maintenance on the database more often]

I research the SQL error, get advised by some site out there that I needed to run REPAIR on my SQL tables, but to be prepared to restore from a backup (good thing I had the cron-backup script ! thanks brad.loo!

The report on the REPAIR told me my user table had been reduced in total number of rows by one (1).

I return to the forum and find my cookied access had been lost ... (some of you are seeing the punchline...) so I tried to login, incorrect login or password (WTF?? checks caps-lock) .. then I decided to bite the butllet and check the database ... my user ID was the only missing record in the user table!

One look at our most recent forum backup gave me the Query to re-insert my account via the backend and I was back in again ...

Who woulda thought when it said that "The number of rows has reduced from 669 to 668" that the missing user would be ME !

EOF

Ouch! What version of MySQL are you running?

MySQL 4.0.18 - seems there's some sort of bug relating to large numbers of DELETE queries being run in close sequence ... or something like that ...

Oh-Oh. That's what they're running on my server. They just upgraded to v4.0.18-standard. I hadn't heard of this bug. And patch or fix for it yet?

Mate - I'm not sure ... I am actually assuming that the bug is in my version (as I had the problem) but I will take a browse thru my logs and see if I can find the place I got the info from ... see if I am giving u the right info ... before you go and bug your host about another upgrade ... :D

You see there I go ... it was 4.0.14 that had the bug ...

4.0.18 is fine (afaik) ...

http://support.discusware.com/forum/...tml?1058121551 <- solution

and

http://lists.mysql.com/mysql/164250 <- this whole thread was useful

Thank for the heads up, Mr. working on WAR with Bob. ;)

;) {ten chars}