Replies: 1 comment
-
If that's not just a configuration problem (i.e., we would have to explicitly state that, for example, the syntax accepted by MariaDB is considered valid) then I'm for it. I have never understood these "mistakes". |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
At the moment, Codacy checks the syntax of SQL files using SQLint. SQLint only supports "ANSI SQL" syntax:
(see https://github.com/purcell/sqlint , "About").
This leads to SQL statements that are perfectly fine in our environment to be marked as syntax errors by Codacy:

Since this imposes unnecessary constraints on our development I would propose to deactive the SQL checks in Codacy until SQLint supports checking the syntax of the SQL extensions we use.
@Kathrin-Huber , @henning-gerhardt , @matthias-ronge : what do you think?
Beta Was this translation helpful? Give feedback.
All reactions