Bug #14773 INFORMATION_SCHEMA.routines data not showing
Submitted: 8 Nov 2005 22:12 Modified: 10 Nov 2005 15:35
Reporter: [ name withheld ] Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version: 5.0.15 OS:Lynix
Assigned to: MySQL Verification Team CPU Architecture:Any

[8 Nov 2005 22:12] [ name withheld ]
Description:
select * from INFORMATION_SCHEMA.columns; - Is showing the colums properly
 
The following is not showing the error message

select * from INFORMATION_SCHEMA.routines;

ERROR 2013 (HY000): Lost connection to MySQL server during query

How to repeat:
select * from INFORMATION_SCHEMA.routines;
[8 Nov 2005 22:23] MySQL Verification Team
I was unable to repeat the behavior reported with current source server:

miguel@hegel:~/dbs/5.0> bin/mysql -uroot test
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2 to server version: 5.0.16-debug

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

mysql> delimiter //
mysql> create procedure sp1()
    -> begin
    -> select 1+1;
    -> end //
Query OK, 0 rows affected (0.00 sec)

mysql> delimiter ;
mysql> select * from INFORMATION_SCHEMA.routines\G
*************************** 1. row ***************************
     SPECIFIC_NAME: sp1
   ROUTINE_CATALOG: NULL
    ROUTINE_SCHEMA: test
      ROUTINE_NAME: sp1
      ROUTINE_TYPE: PROCEDURE
    DTD_IDENTIFIER: NULL
      ROUTINE_BODY: SQL
ROUTINE_DEFINITION: begin
select 1+1;
end
     EXTERNAL_NAME: NULL
 EXTERNAL_LANGUAGE: NULL
   PARAMETER_STYLE: SQL
  IS_DETERMINISTIC: NO
   SQL_DATA_ACCESS: CONTAINS SQL
          SQL_PATH: NULL
     SECURITY_TYPE: DEFINER
           CREATED: 2005-11-08 20:24:03
      LAST_ALTERED: 2005-11-08 20:24:03
          SQL_MODE: 
   ROUTINE_COMMENT: 
           DEFINER: root@localhost
1 row in set (0.00 sec)

mysql>
[10 Nov 2005 15:35] [ name withheld ]
This problem started after I tried to stop/kill a running procedure.How can I get rid of the 1044 error