MySQL Bugs: #25174: Long stored procedure name (64*Ä) ignored and database no longer accessible

Bug #25174	Long stored procedure name (64*Ä) ignored and database no longer accessible
Submitted:	19 Dec 2006 12:10	Modified:	25 Jan 2007 10:07
Reporter:	Heinz Schweitzer (Gold Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.2.8	OS:	Windows (XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Long stored procedure name (64*Ä) ignored and database no longer accessible

With phpMyAdmin you can still work with and access the database
but something prevents access via MySQL Administrator.

MySQL-Server-Information
--------------------------------------------------------------------------------
Mit MySQL-Serverinstanz verbunden
  Benutzername:            root
  Hostname:                localhost
  Port:                    3306
--------------------------------------------------------------------------------
Serverinformation
  MySQL-Version:           MySQL 5.0.24a-community-nt via TCP/IP
  Netzwerkname:            localhost
  IP:                      127.0.0.1
--------------------------------------------------------------------------------
Clientinformation
  Version:                 MySQL Client Version 5.1.11
  Netzwerkname:            XXXXXXXXXXX
  IP:                      XXXXXXXXXXX
  Betriebssystem:          Windows XP
  Hardware:                Intel(R) Pentium(R) M processor 1600MHz, 512 MB RAM

How to repeat:

1.Prerequisite
============
Create a new database schema with one table with one field.
Do not use an existing one you need.
Create a backup  project referring to this database
--------------------

Open  MySQL Administrator 1.2.8 German version
From Kataloge select a schema you can fool around with
In the schema activate the 'stored procedure' tab.

Create a  stored procedure with a name  exactly 64 times the character Ä,
(German A Umlaut).

Say 'execute sql' in order to save the stored procedure.

1) Nothing happens !
2) From now on you can no longer view tables or indices views of this database.
   Closed and restarted MA, even booted but nothing helped.
   You have to drop and recreate the database in order to access it again with MA

3) If there is a backup project defined referring to this database you will get 
an access violation trying to open this project like in screen shot p1

p1

Attachment: p1.jpg (image/jpeg, text), 95.28 KiB.

Could reproduce this with english version also on a different system.

Thank you for the bug report.

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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Additional note: This is actually a problem in the server (see bug #25832). However, MA should be more stable against such problems and hence some adjustments have been made so that it can recover smoothly. However such problematic SPs will prevent the display of any SP in the particular schema (until the server is fixed).