Bug #46128 Stored Procedures not shown in Stored Procedures tab of MySQL Administrator
Submitted: 11 Jul 2009 10:49 Modified: 11 Aug 2009 15:00
Reporter: joost stallaert Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Administrator Severity:S2 (Serious)
Version:1.2.17 OS:Windows (XP SP3)
Assigned to: CPU Architecture:Any
Tags: administrator, stored procedures, Treelist

[11 Jul 2009 10:49] joost stallaert
When I want to create a new stored procedure or fucntion I enter the syntax for the new function/procedure I want to create and then press 'Execute SQL' to create the stored procedure. The dialog (to create the stored procedure) closes and no error messages are given. However, the newly create procedure/function does not appear in the treelist.

I only have this problem in a custom schema I created, in the test schema it works without a problem.
My user is granted all rights on *.* from all clients. I explicitly added all rights on the schema itself via 'User Administration' to make sure it's not a security issue.
The stored procedure/function I created via the function is created in the database itself (when I call it, it works) it's only not appearing in the treelist of the Stored Procedures tab of my custom schema. 

How to repeat:
Create a custom schema, eg FOO. 
Open MySQL Administrator
Select Catalogs
Select the FOO schema
Select the Stored Procedures tab
Click Create Stored Proc
Enter a stored procedure name
In the syntax screen, add any syntax, eg "SELECT 1;"
Press Execute SQL
Observe that the stored procedure is not shown in the treelist. When pressing refresh it's still not visible
[11 Jul 2009 15:00] Valeriy Kravchuk
Thank you for the problem report. What exact version of MySQL server are you working with? Please, send the results of:

show grants\G

statement from mysql command line client when connected as a user that created these stored procedures.
[11 Aug 2009 23:00] Bugs System
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".