Bug #95925 No intellisense, autocomplete or syntax error indicators in MySQL editor
Submitted: 21 Jun 2019 21:28 Modified: 22 Jun 2019 14:42
Reporter: Kevin Hollingshead Email Updates:
Status: Verified Impact on me:
Category:MySQL Visual Studio Integration Severity:S3 (Non-critical)
Version:1.2.8 OS:Windows (10 (Runing under Parallels on Mac Mojave)
Assigned to: CPU Architecture:Any
Tags: sql editor, syntax errors, Visual Studio

[21 Jun 2019 21:28] Kevin Hollingshead
When creating a new or opening an existing MySQL script file the MySQL editor opens but does not provide anything but the most rudimentary syntax highlighting (keywords are blue, everything else is black, including comments). I'm raising this as a bug because I'm assuming you would have created a more fully featured sql editor similar to the one in MySQL Workbench.

How to repeat:
Install MySql for Visual Studio in VS2017.

Use File -> New -> File..., then select MySQL on the left.

Double click the "MySQL Script" (only) option. 

The MySQL editor will open with a blank file named MySQL Script.mysql. 

Type "select * from thingy+;" (note the plus sign is a syntax error)

Observe that no indication is made to show that a syntax error exists.

On a new line type "-- this is a comment".

Observe that the comment text is highlighted like other non-keyword text, i.e. black on white.

Suggested fix:
I would expect (and hope you would too) that syntax errors and highlighting would be at a level equivalent to the sql editor in MySQL Workbench, no?
[22 Jun 2019 14:42] MySQL Verification Team
Thank you for the bug report.