New SQL syntax highlighting breaks with SQL Server quoted names

[c0shea]

Description of the bug

Sublime in the latest version now highlights the closing square bracket of any quoted names in red to mark them as invalid. This previously didn't happen in older versions.

Steps to reproduce

1. Start ST in safe mode
2. Open a new tab/file
3. Set the syntax mode to SQL
4. Paste in the following content

CREATE TABLE [Sales].[DailyMovement]
(
[StoreNumber] [smallint] NOT NULL,
[SaleDate] [datetime] NOT NULL
)

Expected behavior

The right square bracket shouldn't be highlighted in red

Actual behavior

The right square bracket is highlighted in red

Sublime Text build number

4200

Operating system & version

Windows 10

(Linux) Desktop environment and/or window manager

No response

Additional information

No response

OpenGL context information

[keith-hall]

The "SQL" syntax is unfortunately still an alias to MySQL in build 4200. If you set the syntax to T-SQL instead (under the SQL "folder" if using the menu) then you will see much better highlighting.

[c0shea]

@keith-hall Thanks! Do you know if there's a way to have files with the *.sql extension always load with the T-SQL syntax instead of MySQL/SQL syntax?

[deathaxe]

You can clone https://github.com/deathaxe/DefaultSyntaxChooser.

A simplified special purpose solution for SQL is proposed via sublimehq/Packages#4279.

Those commands assign selected dialect (e.g. TSQL) to source.sql scope, so it is also used in all embedded code blocks of languages like Python, Markdown, ...

If only the *.sql extension is to be assigned to T-SQL, you can also ise "Always Open With Syntax" functionality as for any other syntax, to assign the extension to TSQL.sublime-syntax.

[c0shea]

@deathaxe I couldn't get your method of modifying the default SQL.sublime-syntax file to work. Using the always open with syntax functionality works for now.