Open jessehallam opened 6 years ago
Same issue
For some reason it conflicts with the mssql extension. If you have that one, remove it. Then you should be able to select MySQL.
Instead of removing it I just disabled that extension for the current workspace, and then this extension worked just fine
Same here, MsSQL is having conflicts with this and MySQL does not show.
As I said on #15, the language ID for this extension's provided language support should be "mysql" to avoid this conflict. Having to fiddle with extension status should not be necessary.
I've just encountered the same issue. I agree it should be possible to have the MSSQL and MYSQL extensions installed and active side-by-side, and be able to choose the language syntax.
In the absence of a proper fix for this can I suggest that the issue be highlighted in the extensions description? Users shouldn't have to visit GitHub issues in order to figure out why MySQL syntax isn't working.
Also, having to change the file extension to .mysql is not optimal. For example, MySQL Workbench defaults to .sql and changing file extensions won't fly in a complex project. Just my 2 cents.
Hey folks, this issue will be fixed on the next release, and you will get your mssql
associations back. Thanks everyone for your comments ❤️
I have this extension installed in the latest version of vs code. However when I open a
.sql
file, I'm greeted withMSSQL
syntax highlighting:If I click on
MSSQL
in the toolbar, no other options are available:If I click on
SQL
in the toolbar, nothing helpful appears: