MySQL Bugs: #12355: Schemata treeview: display of procedure parameter lacks icon and parameter name

Bug #12355	Schemata treeview: display of procedure parameter lacks icon and parameter name
Submitted:	3 Aug 2005 19:25	Modified:	11 Mar 2009 11:20
Reporter:	Roland Bouman	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S4 (Feature request)
Version:	1.2.12	OS:	Windows (Win XP Professional SP2)
Assigned to:		CPU Architecture:	Any

Description:
In the schemata treeview of the Query Browser, the parameters of procedures are displayed only by the parameter datatype. 
It was expected to see an icon and the name of the parameter rather than just the datatype. (Also, the direction (IN/OUT/INOUT) of the parameter is not displayed but this is already reported as bug 8958)

How to repeat:
In the schemata browser, expand the schema node of a schema containing procedures with parameters. Expand such a procedure node. Observe that the parameters are displayed as text indicating the datatype of the procedure. 

Suggested fix:
Use an icon to indicate parameter direction, and display the name of the parameter instead of the datatype.

Funny, I do see parameter names  in some cases. A function with this signature:

CREATE FUNCTION `tree`.`f_insert_node`(
    p_parent_id INT unsigned
,   p_position  INT unsigned
,   p_label     varchar(32)
) RETURNS INT unsigned

is shown as 

f_insert_node: int(10) unsigned
..INT unsigned
..INT unsigned
..p_label varchar

(the .. aren't really there, they just represent indentation). 
The funny thing is:

1) I really entered 'INT unsigned' for the return type too, but the Query browser likes the change that whereas the parameters retain case 
2) I'd expected to see the length for the varchar parameter.

Many thanks for writing a feature request.

Verified as described by using MySQL Query Browser 1.2.12.

Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Query Browser into MySQL Workbench. We won't add this feature request anymore.

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/