Closed sidewinder94 closed 5 years ago
please support syntax first, thanks
Also would like to see the syntax updated to support SQLCMD
This isnt a full replacement for ssms until sqlcmd mode is supported unfortunately. But great work so far.
1up
1up :)
1up
1up :)
1up
1up
1up
The new version now supports SQLCMD!
Which version supports this? I'm using 1.40.10, October 2019 build but it still says ":setvar" is incorrect syntax.
@puruzio There is an "SQLCMD: Off" button that was added in the latest version, if you click on it it will enable the SQLCMD syntax & ability to run. Otherwise, it won't recognize the SQLCMD syntax.
Sorry, where can I find that button? I looked all over but couldn't find it.
@puruzio You can either access it via the command palette (Ctrl
/Cmd
+ Shift
+ P
) then look for SQLCMD
or it's in the lower most bar when a query editor is opened.
Sorry. Nothing under Ctrl/Cmd+SHift+P shows SQLCMD in its description. I checked in on both Mac OS and Windows versions of VS Code v1.40.0. What am I missing?
@puruzio What version of the extension are you using? We introduced SQLCMD in version 1.7.0
1.7.0 :(
Never mind. I found it in the lower right corner of the task bar. Thanks!
Just one more question. VS code still highlights ":setvar" as a syntax error even with SQLCMD:On
. Is there a solution for that?
It seems to execute and format the code just fine. But the error message is annoying.
SQLCMD On/Off is only available while VS Code is connected to a database. Otherwise, it is hidden.
@Zarepheth thanks for pointing that out, I have found the SQLCMD option after years of being annoyed by this issue.
Devs Is it possible to enable the SQLCMD mode regardless of the database connection as most of the time I use VSCode to open my repository of files and not to run them in VSCode directly. The syntax highlighting / problems being accurate despite a connection would be wonderful
Would it be possible to implement a SQLCMD mode for executing SQL scripts ?
As of now, the syntax is not recognized by VSCode and the execution fails if using SQLCMD features.