Bug #91795 SQL statement generated from modification on the editor is wrong
Submitted: 26 Jul 2018 5:22 Modified: 27 Jul 2018 2:09
Reporter: Shelley Shelley Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S5 (Performance)
Version:6.3.10 OS:Windows (Microsoft Windows 7 Enterprise Service Pack 1)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[26 Jul 2018 5:22] Shelley Shelley
Description:
When fields of SQL statement generated from modification on the editor contains update,set,where these keys, SQL statement tanslate to UPPER case.
Modify the field on the editor, and apply it.Generated sql statement on Review Sql Script is wrong.
for example:
INSERT INTO `db`.`codec` (`id`, `field`, `field_type`) VALUES ('1820', 'cluSETer_type', 'string');

the value of the field should be cluseter_type, but the generated sql statement is cluSETer_type.

It's wrong. And users are difficult to find the error.

How to repeat:
field contains any key on database.
[26 Jul 2018 9:41] Chiranjeevi Battula
Hello Shelley,

Thank you for the bug report.
I could not repeat the issue at our end using with MySQL Workbench 8.0.11 version on Windows 7/10.
Could you please provide repeatable steps (exact steps, WB logs, screenshots etc. - please make it as private if you prefer) to confirm this issue at our end?

Thanks,
Chiranjeevi.
[26 Jul 2018 9:42] Chiranjeevi Battula
Screenshot

Attachment: Bug_91795.PNG (image/png, text), 54.23 KiB.

[27 Jul 2018 1:35] Shelley Shelley
I found the reason. Sorry to propose a wrong bug.
[27 Jul 2018 2:09] MySQL Verification Team
Thank you for the feedback.