Bug #82293 MySQL editor ignores ANSI_QUOTES when highlighting errors
Submitted: 20 Jul 2016 17:35 Modified: 28 Mar 2018 1:46
Reporter: Jonathan Lidbeck Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.3.7 OS:Windows (Microsoft Windows 8.1 Enterprise)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[20 Jul 2016 17:35] Jonathan Lidbeck
Description:
In SQL editing tabs, incorrect syntax highlighting (red underscore) appears under double-quoted string literals, regardless of the validity of the statement with ANSI_QUOTES not set.

How to repeat:
Open a schema with ANSI_QUOTES not selected.

Open a SQL editing tab. Enter a valid query using double-quotes as a string literal, such as:

SELECT GROUP_CONCAT(title SEPARATOR ",") AS titles FROM mybooks GROUP BY rating;

Note that an error is incorrectly highlighted. Hover text reads:

Syntax Error: Unexpected "," (double quoted text)

Suggested fix:
Have syntax validation use the same settings as the active schema.
[21 Jul 2016 5:16] MySQL Verification Team
Hello Jonathan Lidbeck,

Thank you for the report.

Thanks,
Umesh
[21 Jul 2016 5:17] MySQL Verification Team
Screenshot..

Attachment: 82293.png (image/png, text), 51.03 KiB.

[28 Mar 2018 1:46] Christine Cole
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.11 release, and here's the changelog entry:

When SQL_MODE=ANSI_QUOTES was not set, the SQL editor indicated that each
double-quoted string literal was syntax error.

Thank you for the bug report.