MySQL Bugs: #15836: MA causes MySQL to crash after a Schemata is selected under Catalogs

Bug #15836	MA causes MySQL to crash after a Schemata is selected under Catalogs
Submitted:	18 Dec 2005 16:56	Modified:	19 Dec 2005 17:07
Reporter:	[ name withheld ]	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.16-nt	OS:	Windows (Windows XP Pro)
Assigned to:		CPU Architecture:	Any

Description:
Problem started the first time I started experimenting with stored procedures.  I was attempting to edit the first stored procedure I created and MA hung, so I shut it down.  Since then, everytime I start MA and attempt to select a Schemata, no matter if it's test, mysql, information_schema or another schema I created, the mysql server shutdowns (I get a windows error saying that the mysql-nt.exe service encountered an unexpected error and will be shutdown).

I am able to restart the mysql service and use command line sql queries to access data within the various databases, so I am not sure if the tables are corrupted or not.  I attempted to drop the stored procedure via a SQL command line query after the issue with MA started.  However, MySQL could not find the specified stored procedure.  When I select from the mysql_proc table though, I am able to see a single entry for that stored procedure.  So, there must be some inconsistency there, however, is that the reason MA keeps crashing the mysql service?

How to repeat:
Create a stored procedure in any schemata.
Edit the stored procedure.  While editing procedure, close MA down.
Restart MA, select any schemata.
MA will crash the mysql service.

Thank you for a problem report. What exact version of MySQL Administrator do you use? 

I also need more exact description of steps to perform to repeat the bug. Text of the procedure you created, exact change you performed, buttons clicked etc. What do you mean by "While editing procedure, close MA down" - should I discard the changes to the procedure?

Looks like a duplicate of bug #15367.

The version of MA is 1.1.5 for windows.  MySQL version is 5.0.16-nt.

The stored procedure created initially under a root account, and then an administrative account was created for the specific database I was using.  After creating the admin account for the database 'x' I logged out of MA and then logged back in to edit the stored procedure I had created in database 'x'.  While editing the procedure, MA hung, I closed its window, and then restarted MA.  Since then, MA causes MySQL service to shutdown when a Schemata is selected.

Being used to MS SQL server syntax, I was using the stored procedure to learn the MySQL syntax, so the stored procedure code was very simplistic.  I had several IN parameters, a declared variable, a set statement, and that was it.

The in parameters were periodstartdate datetime, status smallint, state nvarchar(2), city nvarchar(66), zip nvarchar(16), rating smallint, evalutorID int

with two lines of code not including 'Begin' and 'End':

DECLARE currentdate datetime;
SET currentdate = CUR_DATE();

Additionally, in reference to Bug 15367, doing a SHOW PROCEDURE STATUS; execution from the command line causes the MySQL server to crash.