Re:Sqlfluff the SQL Linter for Humans
by dugmartin on Wednesday October 06, 2021 @10:53AM
(#28773871)
Or the ultimate pedant (pedultimate?) order which matches the SQL order of operations (which for some queries can be illuminating):
[ Parent
| on HN ]
Re:Sqlfluff the SQL Linter for Humans
by wodenokoto on Wednesday October 06, 2021 @04:41PM
(#28778144)
Is that legal SQL? I'd love to write in that order.
When working in Big Query, it would be so nice to first declare the table, so the online IDE can autocomplete columns.
Re:Sqlfluff the SQL Linter for Humans
by throwaway021212 on Wednesday October 06, 2021 @07:32PM
(#28779832)
You might like QUEL, precursor to SQL (and the original language of Ingres and Postgres) where range variables came first.
Re:Sqlfluff the SQL Linter for Humans
by forgetfulness on Wednesday October 06, 2021 @11:10AM
(#28774080)
Standard SQL and most dialects enforce that in the syntax anyway no?
Edit: misread and select was in the middle in that comment
Re:Sqlfluff the SQL Linter for Humans
by CamouflagedKiwi on Wednesday October 06, 2021 @11:20AM
(#28774218)
No, all databases support the common order of SELECT ... FROM ... WHERE ....
Re:Sqlfluff the SQL Linter for Humans
by forgetfulness on Wednesday October 06, 2021 @11:26AM
(#28774286)
You're right, I somehow missed that select was in a different order.