Bug #78956 Workbench ignores changes to procedure code
Submitted: 25 Oct 2015 16:52 Modified: 26 Oct 2015 5:04
Reporter: Fernando Davidovsky Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S1 (Critical)
Version:6.3 OS:Windows (OS version: 10)
Assigned to: CPU Architecture:Any
Tags: coding issue, workbench

[25 Oct 2015 16:52] Fernando Davidovsky 
Description:
I marked this with severity "Critical" because I can't proceed with my development (I'm really stuck!).

I am writing a stored procedure through the Workbench application. Under certain conditions, changes to code are not recognized, meaning that clicking on the "Apply" button yields a message "No changes detected.".
The only way to cause a detection is to change the procedure declaration, like adding a parameter.

Also, attempted to DROP the procedure and create it again. In certain cases, after doing this (i.e. Create Procedure -> paste the code I kept aside -> "Apply"), after closing the tab and re-opening the same procedure, I get an old version of it.

How to repeat:
Can't tell, but it would appear (though not sure) that it has some relation with the size of the procedure (in my case, 233 lines including lots of comments).
[25 Oct 2015 18:25] Fernando Davidovsky 
It would appear that I found something in relation to getting OLD results... 
I'm manipulating strings and was using 'aaa' + 'bbb' to concatenate instead of the CONCAT function.

Compilation didn't sign any error, and when running the procedure I kept receiving an OLD result. When switching to CONCAT, I got the new result.

It would look that, when an error occurs during execution, a cached value is being returned (no warning of any kind is being shown.

Must confess, didn't include as yet any error handling.
[26 Oct 2015 5:04] MySQL Verification Team 
Hello Fernando Davidovsky,

Thank you for the report.
This is duplicate of Bug #78924.

Thanks,
Umesh