Bug #50294 | ER_UNKNOWN_STORAGE_ENGINE produces diff error message in 5.X and 6.0 versions | ||
---|---|---|---|
Submitted: | 13 Jan 2010 0:13 | Modified: | 24 Feb 2010 20:36 |
Reporter: | Hema Sridharan | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Errors | Severity: | S3 (Non-critical) |
Version: | 5.6.0-beta, 5.5.99 | OS: | Any |
Assigned to: | Jon Olav Hauglid | CPU Architecture: | Any |
[13 Jan 2010 0:13]
Hema Sridharan
[13 Jan 2010 8:03]
Sveta Smirnova
Thank you for the report. Verified as described. I assume problem is not related to different messages between 5.1 and 6.0 servers.
[25 Jan 2010 8:22]
Jon Olav Hauglid
Backported from 6.0 to 5.5 (mysql-next-mr-bugfixing): revno: 2630.22.42 committer: Konstantin Osipov <kostja@sun.com> branch nick: mysql-6.0-runtime timestamp: Fri 2008-10-17 14:36:55 +0400 message: Update old wording (table engine -> storage engine). Note that 5.5 documentation must be updated to reflect that ER_UNKNOWN_STORAGE_ENGINE is "Unknown storage engine '%s'"
[24 Feb 2010 9:38]
Jon Olav Hauglid
errmsg.txt has now been removed from 5.5 (mysql-next-mr) and 6.0, making the backport above irrelevant. Setting the bug to Documenting.
[24 Feb 2010 20:35]
Paul DuBois
re: "Note that 5.5 documentation must be updated to reflect that ER_UNKNOWN_STORAGE_ENGINE is "Unknown storage engine '%s'"" The error messages in the manual are created from the errmsg.txt and errmsg-utf8.txt files in the source trees. An incorrect message in the manual reflects and incorrect message in the source tree. Currently, the 5.5 manual is taken from mysql-trunk (which doesn't have Celosia information). When Celosia is pushed to mysql-trunk, the error message will be updated to whatever Celosia has.
[24 Feb 2010 20:36]
Paul DuBois
No changelog entry needed.