MySQL Bugs: #78924: unable to save stored procedures, incorrectly detected as no changes detected

Bug #78924	unable to save stored procedures, incorrectly detected as no changes detected
Submitted:	22 Oct 2015 12:12	Modified:	7 Dec 2015 20:34
Reporter:	austin woz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	6.3.5	OS:	MacOS
Assigned to:		CPU Architecture:	Any
Tags:	No Changes detected, regression, stored procedures

Description:
Changes to stored procedures cant be saved. Workbench informs me "no changes detected" which is not correct

How to repeat:
Open a stored procedure, make a change and try to save.

(in my case I just changed a number 21 to 19)

Workbench informs me there is no changes detected, and refuses to save the stored procedure. 

I did not have this issue with 6.3.4, I have only had this issue since 6.3.5.

BTW: thank you for the update, the bugs in 6.3.4 were driving me mad. But this bug completely stops me working now. 
Hopefully there is a workaround as i don't want to go back to 6.3.4 and cant wait another month or two for 6.3.6.

I give up, going back to 6.3.4.

back to 6.3.4 and it work fine. 

Sorry to be a critic, but this is such a critical feature of workbench, why release a new version without testing basic tasks such as saving a stored procedure?

I would suggest pulling 6.3.5, to stop further downloads of this vesion, until fixed.

Hello Austin Woz,

Thank you for the report.
Verified as described on Win7 with WB 6.3.5/MySQL Version 5.7.9.

Thanks,
Umesh

6.3.5 - Screenshot..

Attachment: 78924_6.3.5.png (image/png, text), 42.22 KiB.

6.3.4 - Screenshot..

Attachment: 78924_6.3.4.png (image/png, text), 39.06 KiB.

// How to repeat
- create below schema in CLI etc or using WB

CREATE DATABASE IF NOT EXISTS test;
use test;

delimiter //
CREATE PROCEDURE simpleproc()
 BEGIN
   SELECT 12 FROM dual;
 END//
delimiter ;

- Try to alter it from WB i.e change 12 with 15 and apply

Workbench is unusable with this critical fault. 
I recommend you pull version 6.3.5 from the download store until it can be fixed

That's a bad bug indeed and we are working to get this fixed asap. In the meantime you could just use the SQL editor. Decorate the CREATE PROCEDURE code with delimiter and maybe USE. It's inconvenient, but at least you can continue with 6.3.5.

I also recommend pulling the download.

I could decorate code, but don't have confidence in workbench for production if simple tasks like this have not been tested. What else has not been tested before release?

The 6.3.x has been a very buggy version.  6.2.x was far more stable.

Bug #78956 marked as duplicate of this

This is for Mike Lischke.

Can you estimate when a fix to this critical issue will be made available?

I hate when I need to return to previous versions, but will have no choice if the fix will not become available really soon.

I'm only adding this comment because the bug claims to be for Mac OS X.

This issue happens on my Windows 8.1 64bit machine as well.  It's annoying but, as stated above, using the editor with the proper delimiter ($$) is a valid workaround.

Bug #79087 marked as duplicate of this

Same issue affected on triggers. I can't make any changes to triggers.

http://bugs.mysql.com/bug.php?id=79041 marked as duplicate of this one.

Same problem when I try to change triggers.

I have been monitoring this bug daily in the hope of seeing a resolution. But one does not appear to be forth coming. Which leads me to think, and I could be wrong, that MySQL workbench is not being actively developed. Shame as I really like the product between bugs. 
If this is the case, then I must assume there is a rival product that the masses of MySQL users must use, only I dont know what it is. Can anyone tell me what the best alternative is?

best for OSX mac i should add

Hi All, a Can confirm the same in Ubuntu 14.04 LTS
best regards

I found a new workaround. It's annoying, but working well.

Add some white space on deceleration section of the stored procedure.

can you give example of the declaration section? not sure what you mean.

does not look like this is going to be fixed anytime soon. What alternative editor does everyone use?

The option of changing the Procedure's signature was mentioned in a bug report that was marked as duplicate (my report), and this workaround was not added to the main report. Pity.

The idea is quite simple in fact. Suppose you have this declaration:

CREATE DEFINER=`root`@`localhost` PROCEDURE `Register_New_Poll`
                                      (in  Param_1 INT ,
                                       out Param_2 VARCHAR(512)   )
...

You simple need to add blanks, say, before "out Param_2 VARCHAR(512)   )" and click Apply. Next time you do some changes, you remove the added blanks.

The alternative (and this is what I did) is to fallback to version 6.3.4.0 of Workbench, which works PERFECTLY(!).

http://www.heidisql.com/download.php

This is another best alternative for Workbench, It's free.  Please let us know if anyone found another solution.

+1

Facing the same problem. Hope this issue is fixed.

http://bugs.mysql.com/bug.php?id=79435 marked as duplicate of this one.

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.6 release, and here's the changelog entry:

"ALTER PROCEDURE" changes were not detected by Workbench 6.3.5.

As a workaround, the SQL Editor could be used to decorate the "CREATE PROCEDURE" code with delimiters.

Thank you for the bug report.

Bug #79914 marked as duplicate of this

I found this bug in 6.3.5 build 201 CE (64 bits).
My workaround was that I dropped the stored procedure and recreated it.