News for hackers. Stuff that matters.

A comment on Sqlfluff the SQL Linter for Humans. Parent comment

Re:Sqlfluff the SQL Linter for Humans by justusw on Wednesday October 06, 2021 @08:38AM (#28772403)
I guess it depends on what you want out of a linter e.g. if you want it to check just syntax or semantics as well. Is “= NULL” syntactically correct?
[ Parent | on HN ]
Re:Sqlfluff the SQL Linter for Humans by ThePadawan on Wednesday October 06, 2021 @08:43AM (#28772443)
A linter is supposed to tell you "you are probably making a mistake."

"= NULL" is as syntactically correct in SQL as "if (x = null)" in C.

If it wasn't, code highlighting or compiling would break, both of which are much much more obvious.

[ Parent | on HN ]
Re:Sqlfluff the SQL Linter for Humans by danachow on Wednesday October 06, 2021 @10:16AM (#28773465)
The compiler checks syntax - if that’s all a linter did it wouldn’t be very useful.
[ Parent | on HN ]
Re:Sqlfluff the SQL Linter for Humans by munk-a on Wednesday October 06, 2021 @01:05PM (#28775507)
`= NULL` is perfectly legal syntax - but it isn't doing what you think it is.
[ Parent | on HN ]
Re:Sqlfluff the SQL Linter for Humans by ThePadawan on Wednesday October 06, 2021 @01:22PM (#28775730)
That's what parent is saying. He is contrasting a compiler (which this isn't) to a linter (which this arguably also isn't).
[ Parent | on HN ]