MySQL Bugs: #30458: Error message ER_WRONG_MRG_TABLE does not tell the table name

Bug #30458	Error message ER_WRONG_MRG_TABLE does not tell the table name
Submitted:	16 Aug 2007 14:56	Modified:	16 Aug 2007 15:00
Reporter:	Kristian Koehntopp	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Merge storage engine	Severity:	S3 (Non-critical)
Version:	5.0.42-enterprise-log	OS:	Any
Assigned to:		CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
ER_WRONG_MRG_TABLE reports

"Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't exist"

It does not tell which underlying table is problematic. In a merge with more than 100 tables this can be hard to detect.

How to repeat:
Provoke the above problem.
Try to find out which underlying table is broken.

Suggested fix:
Make the error message contain the name of the offending underlying table.

Duplicate of http://bugs.mysql.com/bug.php?id=26976

Fixed in 5.0.44