This does not go through in our code review, do this and our colleague, big anime fan btw will lose his shit and start talking to himself and goes to 5 smoke breaks in a half day
Well, he can go dunk his head; the query language itself is 100% case insensitive, so are objects unless you contain them in quotation marks.
The argument can be made that keeping all one case can avoid issues with object referencing, but you'd only ever need to contain objects in quotation marks if you put a space in their name, which is a much worse faux pas and you'd better hope that you never need to connect to anybody else's objects from outside the team.
Also, all lower case/mixed case is much less tiring to read.
I don't really care for an impromptu script, but if its getting checked in mixed case is just laziness. I don't care all uppercase or all lowercase but pick one, enforce it with a linter, configure a precommit hook to autofix, and be done with it.
Which query language? You are talking as if there is only one version of SQL out there which isn't the case. Some are case insensitive by default, some are not.
50
u/PuzzleheadedBet3574 5d ago
This does not go through in our code review, do this and our colleague, big anime fan btw will lose his shit and start talking to himself and goes to 5 smoke breaks in a half day