L013 seems to expect an alias for the `*` when subsequent columns are present
See original GitHub issuetest.sql
select
*,
'string' as extra_column
from
my_table
$ sqlfluff lint test.sql
== [test.sql] FAIL
L: 2 | P: 5 | L013 | Column expression without alias. Use explicit `AS`
| clause.
The linting passes if I don’t include extra_column
in the select
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Sampling and Aliasing - NJIT
Problem 1: How many samples are enough to have to represent a continuous time signal?
Read more >Aliasing - Wikipedia
In signal processing and related disciplines, aliasing is an effect that causes different signals to become indistinguishable when sampled.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is definitely a bug, but I’m curious as to how it happens. I think it must be that there’s something fundamental about how the parse tree is structured in the two cases. This one needs more investigation.
Next step here is to run
sqlfluff parse
on each of the two queries and understand whyselect * from blah
means that the*
is not parsed as an expression, butselect *, foo from blah
means that*
is parsed as an expression. 🤔Y’all are too quick on the draw! Would love to contribute in a future issue, thanks for addressing this so quickly 🏋️♂️