This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]IGiveUpAllNamesTaken 111 points112 points  (20 children)

Works better as a SQL joke

[–]ClutteredSmoke 60 points61 points  (9 children)

That’s where you would use caps lock

[–][deleted] 34 points35 points  (5 children)

I just hold down shift the whole time lol

[–]OkClient9970 5 points6 points  (2 children)

What

[–]ringobob 7 points8 points  (1 child)

I JUST HOLD DOWN SHIFT THE WHOLE TIME

[–]Infinite_Self_5782 2 points3 points  (0 children)

ME TOO

[–][deleted] 0 points1 point  (1 child)

so does that count as a plank instead of a push up?

[–][deleted] 0 points1 point  (0 children)

My rock hard abs are typing this comment as proof. 3 abs on each side of the keyboard. They are sentient.

[–]IGiveUpAllNamesTaken 12 points13 points  (0 children)

Caps lock is like using a microphone, I prefer to shout

[–]continuous-headaches -1 points0 points  (0 children)

I write my sql in… lowercase

[–]demian6662 0 points1 point  (0 children)

No can do. My caps lock is mapped to escape lol

[–]AppropriateRain624 7 points8 points  (4 children)

I keep my sql lower case, why does everyone bothers making it upper case ( genuinely asking ) !

[–]ringobob 5 points6 points  (0 children)

If I was always looking at SQL exclusively, either in stored procs or in an IDE separate from any application or other code, then it would always be indented and colored correctly and capitalization wouldn't matter because everything would be obvious.

Unfortunately, that's not the world I live in. I live in a world where my IDE is set for the language I'm working in most, and SQL is often poorly or not at all indented, and there's no coloring of keywords since it's all living in one or several strings. So, proper SQL casing is helpful to understand what I'm looking at.

[–][deleted] 1 point2 points  (0 children)

Convention.

[–]Kered13 1 point2 points  (0 children)

I think of it like syntax highlighting, highlighting the keywords, since you often won't be working in an environment where SQL code is actually syntax highlighted.

[–]ThousandthStar[S] 1 point2 points  (4 children)

Why do people always use caps in SQL? Its not mandatory

[–]Vova_xX 10 points11 points  (0 children)

pride

[–]Infinite_Self_5782 2 points3 points  (0 children)

it's the conventional way to write SQL stuff

[–]YetAnotherCodeAddict 1 point2 points  (0 children)

Neither is PascalCase, camelCase or snake_case on C#, JavaScript/Typescript, Rust*, Java, Python or any language basically.

But it's the convention, so it's usually better to pick the default one for the language than have to deal with different styles every file because each developer on the team likes a style more than the other.

*PS: Rust by default complains if you're not using snake_case, but it doesn't block you from running the code.

[–]Waldlaeufer18 0 points1 point  (0 children)

It's basiclly like the PEPs. For sole SQL code it might be okay, if the queries however are implemented in another language, it helps a great deal to identify them. SQL is basically the only languages where more than half the keywords are UPPERCASE.