[RED FLAG BUG] dbForge Studio 2020 MySQL Enterprise - Manipulating/Misrepresenting TEXT Values!

[Requnix]

Version 9.0.304.

This has cost me well over a day of work, and it's a VERY serious issue because I've been trying to resolve a string parsing problem, and couldn't figure out why nothing was working the way it should. It appears that dbForge is either manipulating strings or misrepresenting them in the data fields, or both.

Take the below stored procedure for example. Note the ONLY differences between the two sets of string is a single CRLF for formatting (readability).

Code: Select all

PROCEDURE test_json()
BEGIN
    DECLARE var_text text;

    SET var_text = '{"jobTitle":"Systems Manager \\ DevOps"}';

    SELECT var_text;

    SET var_text = '{"jobTitle":
    "Systems Manager \\ DevOps"}';

    SELECT var_text;

    SET var_text = 'This is a "string" for fun';

    SELECT var_text;

    SET var_text = 'This is 
    a "string" for fun';

    SELECT var_text;
END

So here's the results - the first set is from dbForge and the 2nd set is from MySQL workbench.

Code: Select all

DBFORGE:
"This is 
    a ""string"" for fun"

"{""jobTitle"":
    ""Systems Manager \ DevOps""}"

This is a "string" for fun

"This is 
    a ""string"" for fun"

MySQL WORKBENCH:

'{\"jobTitle\":\"Systems Manager \\ DevOps\"}'

'{\"jobTitle\":\r\n    \"Systems Manager \\ DevOps\"}'

'This is a \"string\" for fun'

'This is \r\n    a \"string\" for fun'

As you can see, dbForge is wrapping quotes around the TEXT value and doubling the quotes.

Because of this issue, I cannot resolve this parsing problem in dbForge; I must switch back to MySQL Workbench.

This is a serious problem.

[alexa]

Unfortunately, we were not able to reproduce this issue.

Could you please tell us what server version you are using?

Please also perform the following:
1. Select 'Tools -> Options...' from the main menu. The 'Options' window opens.
2. Navigate to the 'Environment -> Output' branch.
3. Select the 'Write queries sent by the program to the SQL Log' and 'Log application errors' options.
4. Unselect the 'Delete application log after closing' option. Click 'OK'.
5. Execute the procedure and send us the *.log file with the latest date from the folder:

Code: Select all

%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for MySQL\

You can send the reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .

[Requnix]

Morning Alexa, so I did exactly as you instructed. This is the only MySQL content that was written out after I ran the Stored Procedure can be seen below:

Code: Select all

dbforgemysql.exe Information: 0 : 7:51 AM: dbForge Studio 2020 for MySQL: Start: 6/19/2020 7:51:42 AM
You cannot recursively loading the same module {c45f8674-34de-456f-af53-790acc602c68}.
You cannot recursively loading the same module {c45f8674-34de-456f-af53-790acc602c68}.
You cannot recursively loading the same module {c45f8674-34de-456f-af53-790acc602c68}.
You cannot recursively loading the same module {c45f8674-34de-456f-af53-790acc602c68}.
You cannot recursively loading the same module {c45f8674-34de-456f-af53-790acc602c68}.
You cannot recursively loading the same module {c45f8674-34de-456f-af53-790acc602c68}.

Definitely strange the logs show no indication of running the below Stored Procedure:

Code: Select all

CREATE DEFINER = 'root'@'localhost'
PROCEDURE empowercrm_main.test_json()
BEGIN
    DECLARE var_text text;

    SET var_text = '{"jobTitle":"Systems Manager \\ DevOps"}';

    SELECT var_text;

    SET var_text = '{"jobTitle":
    "Systems Manager \\ DevOps"}';

    SELECT var_text;

    SET var_text = 'This is a "string" for fun';

    SELECT var_text;

    SET var_text = 'This is 
    a "string" for fun';

    SELECT var_text;
END

[Requnix]

Note for clarification, I'm right-clicking and selecting COPY from the Query window output. What's strange is the bottom data viewer shows the hex values of the content. So it looks like it could be an issue of right-clicking and copying from the query result table rather than the core text having issues.

The way I have been checking the data is by right-clicking and copying the var_text value from the Query table window and pasting it into Notepad (multi-monitor system).

So it looks like the problem is right-clicking and COPYing the data and pasting it into Notepad. Apparently the COPY is being corrupted.

[alexa]

We were able to reproduce this issue and will fix it in one of the next product builds.