Bug #17220 | table created with merge eng and non MyISAM table has bad error message | ||
---|---|---|---|
Submitted: | 8 Feb 2006 2:25 | Modified: | 18 May 2006 11:00 |
Reporter: | Jonathan Miller | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.1.7 | OS: | Linux (Linux 32 Bit OS) |
Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
[8 Feb 2006 2:25]
Jonathan Miller
[8 Feb 2006 9:17]
Tomas Ulin
reading the manual states that merge engine is for myisam tables only so either leave as is and/or document more and/or print error message if you try to do a merge table based on other engines than myisam
[24 Apr 2006 6:56]
Tomas Ulin
same happens for innodb: master> create table t1 (a int) engine=innodb; Query OK, 0 rows affected (0.01 sec) master> create table t3 (a int) engine=merge union(t1); Query OK, 0 rows affected (0.00 sec) master> SHOW CREATE TABLE t3; ERROR 1017 (HY000): Can't find file: 't3' (errno: 2)
[18 May 2006 11:00]
Ramil Kalimullin
From the documentation (http://dev.mysql.com/doc/refman/5.1/en/merge-table-problems.html): If you encounter an error message similar to ERROR 1017 (HY000): Can't find file: 'mm.MRG' (errno: 2) it generally indicates that some of the base tables are not using the MyISAM storage engine. Confirm that all tables are MyISAM.