MySQL Bugs: #13682: Edit Stored Procedures & Views

Bug #13682	Edit Stored Procedures & Views
Submitted:	1 Oct 2005 10:59	Modified:	1 Aug 2006 13:20
Reporter:	Robert Locklear	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.1.3	OS:	Windows (Windows XP)
Assigned to:	Vladimir Kolesnikov	CPU Architecture:	Any
Tags:	Object Editors

Description:
If you edit a stored procedure/function and then try to add a new one it overwrites the one you edited.

How to repeat:
1. In the Stored Procedures Tab edit one of you procedures.
2. Click the "create new proc" button and enter the new procedure.
3. Click execute sql.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

I tried to recreate the first procedure that was deletet, and my mysqld server (5.0.15) failed and stopped. I am running both the server and client on the same computer.

I could recreate the procedure from mysql command-line.

This is some additional information that can probably be connected to the  bug "13682". Else, move this to a new bug.

I have a database 'mysql' and a database 'test'.

I create a stored procedure/function 'X' attached to the 'test' database and this seems to work and the procedure is listed for this database.

Then if I "edit stored procedure" and make any changes and press "execute sql" the procedure dissapears from the 'test' database but appears in the 'mysql' database.

I can also make a SQL query for the 'X' against the 'mysql' database (even if some other error will occure) so it seems like the procedure actually has been moved to the 'mysql' database.

Then if I create a new procedure 'Y' for 'test' database this seems to work.

But when I "edit stored procedure" for 'Y' and press 'execute sql' the 'Y' will dissapear in 'test' database AND overwrite the 'X' in 'mysql' database.

So now I only have the 'Y' left and attaced to wrong database.

I read the buggy version is 1.1.3. I'm using 1.1.7 MySQL Administrator and it still has the same bug with a a little bit harder reproducing case. 
You may be implying 'next version' being 2.x I guess?

sorry for the repost.
problem doesn't seem to exist in MySQL Query Browser 1.1.19

I've updated to 1.1.9 and still get this problem. It's not that the edit puts the stored procedure ion a different schema, but more that the stored procedure just disappears. If I use Toad, for example, this all works fine.

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

This bug is still there after being reported in October. Thanks a million for losing this afternonn's work. Any chance that someone can either mend it or publish a workaround.

This may be non-critical to you, but it's a ***** nuisance to new users. A real turn-off from the MySQL setup. You're not Microsoft, so we'd like some action :-)

I'm using mysql administrator 1.1.9 and just getting started with stored procedures. It *really* sucks. It keeps dropping my procedures. When I finally got my main procedure working and attempt to edit another one it dropped the main one.

So, editing procedure B drops procedure A. In order to use this you'd have to keep saving the stored procedures in another editor. I'd rate is as totally unfit for purpose at the moment.

Rob

The bug fix is not a part of the current 5.0-r1a GUI-Tools release. It will be a part of the next (r2) release. At the moment you can use sources from our svn repository.

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

I see how this could be a bug, but what if you WANTED to update the stored proc?