Problem with stored procs/funcs and with debugging

[abarlev]

Using dbForge Studio for MySQL Professional Edition - Trial v3.0.183
I just started the trial. The tool seems to be good, just that I have two issues:
1. After creating a stored procedure with an IN parameter, when opening the procedure again, the parameter is gone. Same goes for stored functions, just that with stored functions not just does the parameter disappear, the return type also changes from TEXT (if defined as such) to

This is very problematic as it appears this way also when exporting the schema.

2. When attempting to compile for debugging I get the following message: "SELECT command denied to user... for table 'debuggings'". What is this table and how is it supposed to be created?

Thanks,

Asaf.

[Elias]

Hello, Asaf.

1. After creating a stored procedure with an IN parameter, when opening the procedure again, the parameter is gone. Same goes for stored functions, just that with stored functions not just does the parameter disappear, the return type also changes from TEXT (if defined as such) to

Make sure that you have saved the procedure before reopening. Please execute some CREATE FUNCTION statement in the sql document, e.g.

CREATE FUNCTION foo() RETURNS TEXT
BEGIN
RETURN 'hello';
END;

and then open the created function in the editor or generate DDL. Is the text of the function correct?

2. When attempting to compile for debugging I get the following message: "SELECT command denied to user... for table 'debuggings'". What is this table and how is it supposed to be created?

The "debuggings" table is the part of the debug engine that is presented as cr_debug database with utility debugging tables and routines.
It seems that you have the debug engine installed on your server but your
user account doesn't have privileges to access cr_debug objects.
Please try to redeploy the debug engine, using the Debug/Deploy Debug Engine menu command, or manage your account privileges using the Security Manager or contact your DBA to give you privileges to use cr_debug schema. Your account need SELECT, UPDATE, DELETE privileges on debugging tables and EXECUTE privilege on debugging routines.