Bug #74237 | unable to save stored procedure | ||
---|---|---|---|
Submitted: | 6 Oct 2014 13:50 | Modified: | 5 Nov 2014 1:47 |
Reporter: | austin woz | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 6.2.2, 6.2.3 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | stored procedure |
[6 Oct 2014 13:50]
austin woz
[6 Oct 2014 14:21]
MySQL Verification Team
Hello Austin, Thank you for the report. Verified as described. Thanks, Umesh
[6 Oct 2014 14:32]
MySQL Verification Team
How to repeat: try to add a new SP: CREATE PROCEDURE `new_procedure` () BEGIN SELECT CAST(1 AS UNSIGNED INTEGER) ; END It, complains about syntax error but SP is created with new_procedure_SYNTAX_ERROR.. Upon refreshing SP is renamed to new_procedure. Later, try to alter the SP - changes are not detected even after adding extra line of code.
[6 Oct 2014 14:33]
MySQL Verification Team
Screenshot..
Attachment: 74237.png (image/png, text), 53.97 KiB.
[5 Nov 2014 1:47]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Workbench 6.2.4 release, and here's the changelog entry: Stored procedures that were identified as having syntax errors could not be saved. Thank you for the bug report.