Devart Forums

It appears dbForge Studio MySQL does NOT like JSON fields.

If I set a stored procedure field to type of JSON, whenever I try to debug the stored procedure, I get the error:

Cannot create a JSON value from a string with CHARACTER SET 'binary'.

Note this ONLY happens when trying to debug a Stored Procedure with the Studio debug interface, as seen below. Note the JSON data type is selected:



To fix it? I just change in_JSON to a TEXT type. It's also important to note the EDIT PARAMETERS dialogue doesn't have a JSON data type selectable, only TEXT.

Another issue is the JSON processed with the debugger is tossing a ton of \ in the values, as seen below:



Note entries 13 and above are created by my system; 14, 15 and 16 are from the debugger.

This is to be supported in one of the next product versions.

Thank you for the clarification. Are we talking about the next few weeks, or are we looking at months until the fix is released?

Unfortunately, we don't have the estimated date for this at the moment.

Can I please get a status update on this issue? This problem is how hindering the debugging of a commercial application since it will not allow complex JSON content (simple, yes, but not long/complex), which renders the debugger useless.

The new product build with the fix should be released at the end of April.

Thank you - that makes me VERY happy!