michaelab
10-05-2003, 06:04 PM
My board is unfortunately suffering rather frequently from phantom thread deletions which are always accompanied by a MySQL error 1030 "got code 127 from table handler". It's infuriating and I guess I have to put it down to the MySQL v4.0.12 corruption bug. My host refuses to upgrade to MySQL v4.0.15 so there's pretty much nothing I can do.
The specifics of what happens is that the "thread" record for the thread goes missing but all the "post" records are still there. The error message I get always contains the threadid. So, what I've been doing is re-inserting the correct thread record based on data from the post table.
Clearly this must be automatable with a script that just takes the threadid as an argument and inserts a thread record based on data from the post table. Before I go and write such a script, has anyone done something like that already?
Thanks,
Michael.
The specifics of what happens is that the "thread" record for the thread goes missing but all the "post" records are still there. The error message I get always contains the threadid. So, what I've been doing is re-inserting the correct thread record based on data from the post table.
Clearly this must be automatable with a script that just takes the threadid as an argument and inserts a thread record based on data from the post table. Before I go and write such a script, has anyone done something like that already?
Thanks,
Michael.