We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When working with tables inside a CTE (aka WITH) no column completions are generated.
WITH
e.g. when the cursor is here (at the |)
|
SELECT x.| -- completions generated correctly FROM some_table x
however this doesn't work for me:
WITH v as ( SELECT x.| -- no completions generated FROM some_table x ) SELECT v.* FROM v
Possibly relevant log messages when the completions are not generated:
[2024-02-09T17:55:47.774] [DEBUG] default - WITH [2024-02-09T17:55:47.774] [DEBUG] default - complete: WITH [2024-02-09T17:55:47.774] [DEBUG] default - target: WITH
which may mean the completions aren't targeted to the SELECT.
SELECT
Additionally, an exception is often being thrown here (even when the completions work and the SELECT is the target):
if (_e.name !== 'SyntaxError') { throw _e }
since the exception that is coming from the PEG parser is named peg$SyntaxError, I think.
peg$SyntaxError
I am using:
nvim-lspconfig
[email protected]
v20.11.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When working with tables inside a CTE (aka
WITH
) no column completions are generated.e.g. when the cursor is here (at the
|
)however this doesn't work for me:
Possibly relevant log messages when the completions are not generated:
which may mean the completions aren't targeted to the
SELECT
.Additionally, an exception is often being thrown here (even when the completions work and the
SELECT
is the target):since the exception that is coming from the PEG parser is named
peg$SyntaxError
, I think.I am using:
nvim-lspconfig
[email protected]
v20.11.0
The text was updated successfully, but these errors were encountered: