Skip to content

Commit 9f15cd1

Browse files
committed
re-word to be less sarcastic lol
1 parent c1504c8 commit 9f15cd1

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

_posts/2024-07-30-everythings-a-case-statement.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,13 @@ image: img/postbanners/2024-07-30-everythings-a-case-statement.png
99

1010
Just a quick public service announcement:
1111

12-
I've now received quite a few responses to this post saying nearly the same thing..."_Not to be pedantic, but it's a case expression, not a case statement_". It's like when people say "No offense, but" and then say something offensive.
12+
Yes...I know it's a "CASE expression" and not a "CASE statement".
1313

14-
Yes...Thank you, you are correct, it is an "expression" not a "statement", here's your cookie 🍪.
14+
I've now received quite a few responses to this post saying nearly the same thing..."_Not to be pedantic, but it's a case expression, not a case statement_".
1515

16-
And no, I'm not fixing it. Why? Because it changes nothing about the information in this post, there is no confusion as to what I'm referring to. The vast majority of people refer to them as a "CASE _statement_" despite being inaccurate. When writing blog posts and tuning SEO, I'm going to go with the most common phrasing.
16+
Yes...Thank you, you are correct, it is an "expression" not a "statement".
17+
18+
When I originally posted it, I considered fixing it. But in the end, it really doesn't matter, it doesn't change the information in the post. And as far as SEO goes...it appears most people don't search for "sql case expression" anyway. So, this PSA is my compromise.
1719

1820
Exhibit A:
1921

0 commit comments

Comments
 (0)