MySQL Bugs: #14485: Server Crashes when Editing Stored Procedure

Bug #14485	Server Crashes when Editing Stored Procedure
Submitted:	30 Oct 2005 3:42	Modified:	11 Jan 2006 11:03
Reporter:	Raj Borborah	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.1.4	OS:	Windows (Windows XP Professional)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
When editing a stored procedure the edit window displays the stored procedure
without the database name before it.

If you save the procedure it crashes the mysql server process.
Both are running on same machine Windows XP.
If you add the `dbname`. prefix it does not crash

How to repeat:
Create a Store Procedure and save it
Now Hit Edit in Administrator to bring up the stored procedure
Hit Save to save the stored procedure(no need to make any change)

Suggested fix:
Clicking on Edit should put the dbname prefix
Server should not crash for any reason like this

Thanks for the bug report. I was able to reproduce it on 1.1.4.

If restarted having one storeproc with no db in the mysql.proc table will make the administrator and the query browser to stop displaying all storeproc.

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