You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using MySQL without a DB connection.
In MySQL, while not recommended, you can use double quotes for strings. Example: VALUES("Hello World").
Currently, if you have such a code, it will cause the language server to return a Not found statement error on a completion request.
To Reproduce
Start the sqls language server without configuration and DB connection
Check the LSP communication below, and imitate the same steps either programmatically or by running an LSP client.
It will provide the competition sometimes, depending on the cursor position. I'd recommend strictly following actions from the LSP communication to reproduce the issue.
See that you won't get any suggestions on competition requests.
See that you will get the Not found statement error
Versions (please complete the following information):
OS Version: Docker container. Based on frolvlad/alpine-glibc
Describe the solution you'd like
Add the possibility to configure the language server to identify double-quoted string values as valid. We could use the configuration file to specify the default behavior.
The text was updated successfully, but these errors were encountered:
Allless
changed the title
MySQL: Double-quoted strings break suggestions
MySQL: Double-quoted string values break suggestions
Sep 11, 2024
Using MySQL without a DB connection.
In MySQL, while not recommended, you can use double quotes for strings. Example:
VALUES("Hello World")
.Currently, if you have such a code, it will cause the language server to return a
Not found statement
error on a completion request.To Reproduce
Not found statement
errorVersions (please complete the following information):
Additional context
LSP communication
Describe the solution you'd like
Add the possibility to configure the language server to identify double-quoted string values as valid. We could use the configuration file to specify the default behavior.
The text was updated successfully, but these errors were encountered: