Bug #12679 myisam-recovery doesn't affect MyISAM tables if they are opened via MERGE table
Submitted: 19 Aug 2005 15:41 Modified: 19 Aug 2005 15:43
Reporter: Victoria Reznichenko Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Merge storage engine Severity:S4 (Feature request)
Version:any OS:Any (any)
Assigned to: CPU Architecture:Any

[19 Aug 2005 15:41] Victoria Reznichenko
If a sub-table of MERGE table is corrupted and table is opened via MERGE table (i.e. query involves only MERGE table and not corrupted MyISAM table) then myisam-recovery does nothing.

If I do any query that uses MyISAM table directly, MySQL automatically repairs it.

How to repeat:
1. start mysql server and open new connection.
2. restore tables (change path to the index files in total_flat.MRG file). Table 'flat' is corrupted.
3. from opened connection execute any query that uses MERGE table, f.e.
select * from total_flat limit 1
4. check error log
5. from the same connection execute any query that uses 'flat' table, f.e
select * from flat limit 1
5. check error log
[19 Aug 2005 15:43] MySQL Verification Team
tables were uploaded to bug12679.zip">ftp: bug12679.zip