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
Hello,
I noticed that lately DBCode began complaining about non-existing errors in perfectly valid queries, example:
I figured it does not like lower-case keywords, but since when upper case keywords became compulsory in SQL? I prefer not to enable sql-formatter.uppercase as I use ClickHouse SQL flavour, and certain CH functions are badly named for historical reasons, and whenever any linter all-caps them, it actually breaks the query.
Furthermore, today it began complaining about a non-existent file:
Screen.Recording.2025-10-30.at.14.18.45.mov
Please note in the video above, I have no open file 'Untitled-2' and whenever I click the error, DBCode seems to create an empty file for me..
In addition, ClickHouse SQL has notoriously complex syntax, and even properly formatted queries can trigger linting error, and on contrary -- most linting errors (see the first example) are not errors per se...
All in all, it'd be nice to have "disable linter" option.
p.s. I have "dbcode.useLanguageServer": false, still having all these problems pop up in every SQL file.
Thanks for continued support!
Debug:
2025-10-30 14:08:37.847 [info] line 4:4 token recognition error at: '`'
2025-10-30 14:08:37.847 [info] line 4:14 token recognition error at: '`'
2025-10-30 14:08:37.847 [info] line 5:4 token recognition error at: '`'
2025-10-30 14:08:37.847 [info] line 5:16 token recognition error at: '`'
2025-10-30 14:08:37.848 [info] line 6:4 token recognition error at: '`'
2025-10-30 14:08:37.848 [info] line 6:14 token recognition error at: '`'
2025-10-30 14:08:37.848 [info] line 7:4 token recognition error at: '`'
2025-10-30 14:08:37.849 [info] line 7:16 token recognition error at: '`'
2025-10-30 14:08:37.850 [info] line 8:4 token recognition error at: '`'
2025-10-30 14:08:37.850 [info] line 8:12 token recognition error at: '`'
2025-10-30 14:08:37.850 [info] line 9:4 token recognition error at: '`'
2025-10-30 14:08:37.850 [info] line 9:13 token recognition error at: '`'
2025-10-30 14:08:37.850 [info] line 10:4 token recognition error at: '`'
2025-10-30 14:08:37.851 [info] line 10:26 token recognition error at: '`'
line 11:4 token recognition error at: '`'
2025-10-30 14:08:37.852 [info] line 11:14 token recognition error at: '`'
Hello,
I noticed that lately DBCode began complaining about non-existing errors in perfectly valid queries, example:
I figured it does not like lower-case keywords, but since when upper case keywords became compulsory in SQL? I prefer not to enable
sql-formatter.uppercaseas I use ClickHouse SQL flavour, and certain CH functions are badly named for historical reasons, and whenever any linter all-caps them, it actually breaks the query.Furthermore, today it began complaining about a non-existent file:
Screen.Recording.2025-10-30.at.14.18.45.mov
Please note in the video above, I have no open file 'Untitled-2' and whenever I click the error, DBCode seems to create an empty file for me..
In addition, ClickHouse SQL has notoriously complex syntax, and even properly formatted queries can trigger linting error, and on contrary -- most linting errors (see the first example) are not errors per se...
All in all, it'd be nice to have "disable linter" option.
p.s. I have
"dbcode.useLanguageServer": false, still having all these problems pop up in every SQL file.Thanks for continued support!
Debug: