Some syntax not supported
See original GitHub issuePossibly fixed by https://github.com/Borvik/vscode-postgres/projects/2.
begin;
select 1;
commit;
shows syntax errors for begin
and commit
.
PS: Your extension is awesome! I like the autocompletion, parameter and return type suggestions, and also being able to see multiple result sets at once.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Abstract Syntax not supported · Issue #591 - GitHub
Issue. Abstract Syntax not supported. I am trying to send a dicom from Horos to a StoreSCP implementation and I am encountering this...
Read more >“The syntax is not supported by this runspace” error after ...
The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode. Message 2. Exception occured System.Management.Automation....
Read more >What are the SQL Server query syntax not supported by ...
I am not using any stored procedures, views, triggers, user defined functions, etc. But I think even then some queries written for SQL...
Read more >Transfer Syntax missing during Query/Retrieve - Google Groups
We configured Orthanc to work as DICOM Server. The Store part working fine, but when performing Query/Retrieve we are facing problems. The Study ......
Read more >Javascript syntax highlighting it not working
Go to Tools > Extensions and Updates > Installed. And look for "Visual Studio Extension for TextMate Grammars" and make sure it is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The following valid sql statements show syntax errors:
Currently the error validation is powered by postgres itself by prepending each statement with an
EXPLAIN
and running that. Postgres itself is returning these errors.EXPLAIN
was not meant forCREATE
/ALTER
statements - but works good forSELECT
statements.However creating a whole parser that can do this analysis is tricky at best, but to also create one that can be kept up-to-date with the version of postgres anyone might be connected to… yeah… really not my forte (also this is a side-project I don’t really have a lot of time to work on)