This screenshot represents an error I've received numerous times where I've edited a Stored Procedure only to have the IDE tell me there's an error (when there is not) and prohibiting me from saving the changes. Note in this example, I added "in_password", which triggered this error stating out_result doesn't exist, when it does.
Note copying the contents of the window, closing, re-opening the Stored Procedure, Pasting and Applying changes works fine. There are no errors or syntax issues.
dbForge MySQL 2020 Bug - IDE Syntax Error Issue
Re: dbForge MySQL 2020 Bug - IDE Syntax Error Issue
Could you please provide us the server's version?
Does it reproduce constantly on the procedure you provided?
Does it reproduce constantly on the procedure you provided?
Re: dbForge MySQL 2020 Bug - IDE Syntax Error Issue
Server Version: 8.0.18
So much code has changed since I reported the problem that I'm not sure. I've learned how to work around these issues automatically and can't remember the exact cause; but it happened regularly with multiple stored procedures.
So much code has changed since I reported the problem that I'm not sure. I've learned how to work around these issues automatically and can't remember the exact cause; but it happened regularly with multiple stored procedures.
Re: dbForge MySQL 2020 Bug - IDE Syntax Error Issue
This bug still exists in the new 9.0.285 version.
Re: dbForge MySQL 2020 Bug - IDE Syntax Error Issue
Thank you for the reply.
We will investigate this issue and will answer you as soon as possible.
We will investigate this issue and will answer you as soon as possible.
Re: dbForge MySQL 2020 Bug - IDE Syntax Error Issue
Could you please tell us if the issue reproduces on the official release of version 9.0 and, if so, describe the steps to reproduce and provide a video?
Re: dbForge MySQL 2020 Bug - IDE Syntax Error Issue
Of course; I THINK the issue is gone, but I got into the habit of constantly re-compiling the procedures due to the bug (that's what fixed it) so I'll try to compile less and see if it pops back up - and if so, let you know. Thanks!