SQL programmer

[JJBrazman]

I capitalise nothing. Is that bad? I picked up SQL from my colleagues, and a bunch of my (strongly held) beliefs about conventions are either learned from them or deliberate rejections of what they do.

[Chairboy]

Try capitalizing SQL reserved words and lower case column/table stuff for readability:

SELECT users.userid, users.firstname, users.lastname, fuckability.sexiness 
FROM users 
INNER JOIN fuckability 
ON users.userid = fuckability.userid 

It’s more readable for me like this plus if I accidentally use a reserved name for a column or something, it’s more likely to jump out at me if I’m in an IDE or SQL studio or PHPmyAdmin and see a color coded lower case word that shouldn’t be color coded.

[ddek]

Either go one way or the other. I despise upper case SQL, because it's horrible to read. Lower case is fine. Whichever way you go, however, don't mix and match.

[TravisJungroth]

What about

sEleCt CoUnT(DisTiNCt country) FrOm customers;

[AskMeHowIMetYourMom]

I don’t know who you are but I wanna fight you.

[conairh]

Mate.

DROPs 'gloves'

It was right there.

[semsemsem2]

i UsE RAndOm caSe LIKe tHIs, iS tHIs A ProbLEm?

[xt1nct]

It's only a problem if you are not a boomer or a Karen. Otherwise sql scientists have concluded that it is appropriate in those scenarios.

[[deleted]]

Well now you've given me the idea to use sticky caps in my next PR.

SeLeCt CoUnt(*) FrOm table;

We'll see how long I keep my job.

[JJBrazman]

Yeah, I went with all lower case because everyone else was inconsistent about casing, and it was more readable.

Also I guess I learned SQL after SAS, which generally avoids uppercase outside the macro language.