Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
regexman1
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
regexman1
22d ago
Brilliant
2.
▲
Show HN: A TUI for Inspecting Snowflake Tasks
(github.com)
3 points
by
regexman1
22d ago
|
0 comments
3.
▲
by
regexman1
2y ago
I'm an analyst so I literally only query for analytical purposes. I don't have any SQL code embedded in an application so the 1=1 is purely for tweaking/testing a query more quickly. I certainly didn't use AI, all these
4.
▲
by
regexman1
2y ago
I've amended the README.md to explain what I meant. My error was in using the word dynamic!
5.
▲
by
regexman1
2y ago
Just to be clear I'm using it for the same reason as trailing commas. If I'm inspecting a dataset I use WHERE 1=1 so I can add and remove conditions more easily. I realise the confusion is in my wording of dynamic - I might amend
6.
▲
Show HN: A command-line tool for bulk deleting your GitHub gists
(github.com)
1 points
by
regexman1
2y ago
|
0 comments
7.
▲
by
regexman1
2y ago
That's right - it's just a quicker way of being able to comment/uncomment conditions when doing EDA or debugging.
8.
▲
by
regexman1
2y ago
Not at all actually, I just hadn't really planned to add this as a tip. Additionally I thought an in-line view was fine for the examples included. But maybe I will!
9.
▲
by
regexman1
2y ago
Fair point!
10.
▲
by
regexman1
2y ago
I appreciate the feedback, no offence taken. I'm an analyst so I often find the leading comma useful when I'm testing something and want to quickly comment a column out but I take your point. And I agree, I should have used CTEs f
11.
▲
by
regexman1
2y ago
That's a totally valid point haha.
12.
▲
by
regexman1
2y ago
I didn't realise that, great to know. Thanks!
13.
▲
by
regexman1
2y ago
I'll add this as a caveat. I'm an analyst so my SQL isn't really exposed to anyone other than myself and so I wasn't aware of this, thanks for flagging.
14.
▲
SQL Tips and Tricks
(github.com)
332 points
by
regexman1
2y ago
|
161 comments