[SA 9.2.346 Pro] - MySQL stored procedure arguments

[SA 9.2.346 Pro] - MySQL stored procedure arguments

There's something fishy about stored procedure arguments shown in popup for CALL in MySQL. It seems as if the argument list gets corrupted (see screenshot below).

The actual stored procedure definition starts as:

	Code:
	CREATE PROCEDURE traccar.usp_add_geofence ( a_name VARCHAR(128) ,a_description VARCHAR(128) ,a_area VARCHAR(4096) ,a_attributes VARCHAR(4000) ,a_calendarid INT ,a_groupid INT ) . . .

UPDATE: Still an issue in [9.2.349 Pro].

UPDATE: Still an issue in [9.2.349 Pro].

Thank you for reporting this issue.
Do you use ODBC or native connection? What's your MySQL client version?

I experience it on both ODBC and native, using MySQL version 5.1.40 with libmysql.dll version 6.1.11.0.

This issue has been confirmed as a bug that requires fixing SQL Assistant's internal MySQL client handler.

I guess that'll take some time. Any estimates on it?

The task has been assigned and shouldn't be difficult to fix. Unfortunately I cannot offer an ETA for the fix and whether it will be available in 9.2 code branch, or as part of the next maintenance release. Next version is tentatively labeled as 9.5 and no formal date is set for the release yet. If this is a critical issue for you, please let us know. I will check if the fix can be back-ported to 9.2

Not really critical, yet it'd be nice to see it fixed. Selecting a stored procedure will result in incorrect number of arguments pasted into the code, as well as the popup when hovering over stored procedures will contain misleading info.