Re:Sqlfluff the SQL Linter for Humans
by fnord123 on Wednesday October 06, 2021 @10:32AM
(#28773636)
alt styling
[ Parent
| on HN ]
Re:Sqlfluff the SQL Linter for Humans
by EamonnMR on Wednesday October 06, 2021 @12:21PM
(#28774946)
That's the one I'm familiar with. The capitalized keywords help give you that Relational Database feel.
Capitalized keywords and section declarations on their own lines helps with quick comprehension for me at least
I've seen this one in the wild and have objections to it.
- why capitalize KEYWORDS. We're no longer in 1970s. We use colors
- why waste so much space. Why not just put table on the same line with from. With joins this just bloats up
- for complicated conditions they have to be put on their own lines. Do I give each AND a separate line and waste ever more space?
Re:Sqlfluff the SQL Linter for Humans
by wodenokoto on Wednesday October 06, 2021 @04:46PM
(#28778204)
- Half my SQL queries are written inside some other script, like Python or bash, so capitalization is nice.
- Space is not wasted when it it makes code more readable.
- Yes, and also give the columns in select their own lines. So nice to read. Space well spend!
Good points. Maybe there is a difference between a SQL script embedded occasionally somewhere in python, for which this style probably makes sense.
For heavy SQL codebases found in data analytics, there are better styles.
Re:Sqlfluff the SQL Linter for Humans
by bntyhntr on Wednesday October 06, 2021 @04:08PM
(#28777771)
My editors and code review tools do not format or highlight sql for me when it's embedded in other files - eg java. I find capitalized keywords to be very convenient. Of course at that point, I can't run sqfluff on it either but this thread has already devolved fairly quickly.