From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Description of problem:
Running a query of "DELETE FROM table" will fail if the table is an ISAM table, with the error "ERROR 1: Can't create/write to file './foo/table.ISM' (Errcode: 17)".
Running "DELETE FROM table WHERE 0=0" works fine. Converting the table to MyISAM also fixes the problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. CREATE TABLE test (col1 int(10)) TYPE = ISAM;
2. INSERT INTO test SET col1=15;
3. DELETE FROM test;
Actual Results: ERROR 1: Can't create/write to file './test/test.ISM' (Errcode: 17)
Expected Results: Query OK, 0 rows affected (0.00 sec)
Sorry, this isn't a security item, not a Legacy issue. If this problem still
occurs in supported versions of Fedora Core (3/4) then please refile for those
It's an issue that started after a Legacy update, and was not present before.
Therefore, the bug is likely to be only in the Legacy code.
Previous version of MySQL was mysql-server_3.23.58-1.90.5.legacy_i386.rpm.
So, is this going to be fixed?
(In reply to comment #4)
> So, is this going to be fixed?
Haven't heard any action. A workaround (which we used) is to convert the tables
This doesn't seem to be important enough to fix just on its own, so mark it DEFER.
(In reply to comment #6)
> This doesn't seem to be important enough to fix just on its own, so mark it DEFER.
In that case, I will attach the workaround we used; a script to convert all ISAM
tables to MyISAM.
Created attachment 121151 [details]
Ad-hoc perl script to convert ISAM tables to MyISAM
A small perl script to convert all ISAM tables to MyISAM, which works around
the problem this bug causes.
Use at your own risk.
-----BEGIN PGP SIGNED MESSAGE-----
Could you please try the following rh9 packages and report back here. They
should fix the problem. If they work for you, I'll release them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
-----END PGP SIGNATURE-----
They do not fix the problem; the repeatable steps I listed still produce the
(In reply to comment #10)
> They do not fix the problem; the repeatable steps I listed still produce the
> same error.
Correction: they work just fine, if I install them right.
Problem appears to be solved.
Packages to fix this issue have been submitted for QA in bug 167803.