>>>>> "Jonathan" == Jonathan A Zdziarski <jonz@stripped> writes:
Jonathan> it is...but i don't experience this problem with 3.22 only the new
>> > > > jonz@stripped writes:
>> > > > > >Description:
>> > > > > After updating rows in a table, on an AUTO_INCREMENTing key
>> > > > > I receive 'ERROR 1034: Incorrect key file for table. Try
> and repair it'.
>> > > > > mysql> select * from EVENTS;
First; When one reports like the above, the fastest way to get this
fixed is to upload the problem file (checked to ensure that it doesn't
contain any errors), to:
together with a script that corrupts its. By doing this you can be
sure to get this fixed VERY rappidly.
I did just fix for MySQL 3.23.5 a bug that corrupted indexes when the
first column was a CHAR that could have NULL values. If your table
has such a column. I strongly suggest you to try MySQL 3.23.5 and
report if this helps!
Anyway; You can probably get MySQL 3.23 to work by switching the
problem table to ISAM:
ALTER TABLE EVENTS TYPE=isam;
(I would however like to get a copy of your table if it doesn't work
in MySQL 3.23.5 to nail the bug!)