If a string in an SQL file ends in a backslash, the backslash acts as an escape character. ST3 thinks the string has not ended, which adversely affects the syntax highlighting for the rest of the file. This issue is described further here:
SQL syntax highlighting for /’ in string
Disable backslash as escape
Since the SQL I write is not intended for MySQL, I had previously fixed the issue (as suggested in the above posts) by modifying the “SQL.tmLanguage” file (located within the compressed “SQL.sublime-package” file). However, as of ST3 Build 3103, that file appears to have been replaced with a “SQL.sublime-syntax” file, and so far I am unable to determine how to modify it in order to fix this issue.
To avoid affecting the rest of the file, I have been adding a commented single-quote after each “offending” line, but this is a poor workaround. Can anyone suggest a fix that does not require a change to the SQL file?