MySQL Bugs: #14939: crash in procedure or funtion

Bug #14939	crash in procedure or funtion
Submitted:	15 Nov 2005 8:01	Modified:	16 Dec 2005 19:15
Reporter:	sanjeev kumar	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	mysql 5.0.15	OS:	Windows (windows 2000)
Assigned to:		CPU Architecture:	Any

Description:
hello
i am using mysql  5.0.15   running on windows 2000

when i am creating procedure name given as blank space it's crashing

same when i am creating funtion to give name as blank space it's crashing

Please solve this problem

How to repeat:
for procedure

execute this query it will crash
delimiter // ;

create procedure ` `()
begin
select 1;
end//

Thank you for a problem report. Have you selected any database before creation (looks like no - if this is the case, than your crash is a known problem)? If I do use some, your procedure can be created and used without any crashes:

C:\Documents and Settings\openxs>mysql -uroot -p -P3307
Enter password: ****
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2 to server version: 5.0.15-nt

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> use test;
Database changed
mysql> delimiter //
mysql> create procedure ` `()
    -> begin
    -> select 1;
    -> end//
Query OK, 0 rows affected (0.15 sec)

mysql> delimiter ;
mysql> call ` `();
+---+
| 1 |
+---+
| 1 |
+---+
1 row in set (0.00 sec)

Query OK, 0 rows affected (0.04 sec)

screenshot of crash during create procedure to give name as blank space

Attachment: mysql crash.jpg (image/pjpeg, text), 49.41 KiB.

yes i am selecting database first before creating the procedure

I see that you have a crash while trying to create this procedure. But I do not see the 'use database' or database in the mysql command line. Please, just copy and paste all the commands you executed since the MySQL server startup and before the crash, just as I did.

I need additional information on how to repeat this crash, because I was not able to.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".