Bug #38583 | Parser error messages are meaningless. | ||
---|---|---|---|
Submitted: | 5 Aug 2008 19:41 | Modified: | 16 Oct 2008 3:50 |
Reporter: | Chris Rossi | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Parser | Severity: | S3 (Non-critical) |
Version: | 5.0.51b-community-nt MySQL Community Edi | OS: | Windows |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | error messages |
[5 Aug 2008 19:41]
Chris Rossi
[6 Aug 2008 0:08]
MySQL Verification Team
Thank you for the bug report.
[8 Oct 2008 19:54]
Konstantin Osipov
The suggestion is to make parser error messages more context dependent (print what is expected, etc.).
[23 Mar 2013 8:25]
David Nechodom
Today, I encountered "Error 1607: Cannot create stored routine `spc_reset_bucket_firsts`. Check warnings ..." when attempting to submit a modified version of an existing routine. Where are the warnings? Does anyone have a clue why I couldn't create the routine? After three hours of fruitless butchery on the code, I happened to remove the comment. Imagine my shock when what remained of my code produced a new procedure! Over the next two hours, I added, then removed, various chucks of code until I finally determined that the culprit all along was a half-dozen too many characters in the comment! Can anyone tell me how a person would know that from the error message?