Post funny things about programming here! (Or just rant about your favourite programming language.)
Speaking as a Senior Dev specialized in database access and design... you don't have to use all caps - SQL is actually case agnostic.
But... but my fucking eyes man. I'm old, if your branch doesn't have control keywords in all caps I'm going to take it out back and ol' yeller it.
There are few hills I'll die on but all caps SQL and singular table names are two of them.
I'm a sql developer, and I am completely the opposite to you. I will find it incredibly difficult to read when everything is in caps
You should do a project together
You monster.
The commit wars will be long and bloody.
Same, I prefer lower case. Every other language has keywords in lower case, why do you need to shout when writing sql?
I understand it as an attempt to get very basic, manual syntax highlighting. If all you have is white text on black background, then I do see the value of making keywords easy to spot by putting them in all caps. And this probably made sense back when SQL was first developed, but it's 2023, any dev / data scientist not using a tool that gives you syntax highlighting seriously needs to get with the times
Please tell me what IDE you're using that's capable of highlighting SQL syntax that's embedded inside another language source file
Also please fucking stop with the "it's current year stop x." The year is not an argument.
As the other commenter said, the Jetbrains IDEs do this perfectly fine. Although I'd also argue that if you're working with SQL from within another language already, a DSL wrapper is probably gonna be the better way to go about this.
Unfortunately RustRover is still garbage for actual usage. And I refuse to use an ORM when I can just write the SQL in a more common syntax that everyone understands across every language instead of whatever inefficient library-of-the-week there is. Raw SQL is fine and can be significantly more performant. Don't be scared.
I'm not talking full blown ORM here, not a fan of those either. I'm talking about some light weight wrapper that basically just assembles SQL statements for you, while giving you just a little more type safety and automatic protection against SQL injection, and not sacrificing any performance. I'm coming from the JVM world, where Jooq and Exposed are examples of that kind of thing.
I'm currently using SQLx which you write raw queries in and it validates them against a currently-running db, using the description of the tables to build the typing for the return type instead of relying on the user. It makes it pretty hard to write anything that supports injection
Oh, that sounds really cool! At what time does this validation happen? While you code, or later at build time?
Also some people are color blind.
Also you might need to ssh in somewhere and vi some code or tail a log file where you don’t have color support.
My ide isn't limited to color when it comes to highlighting, so being color blind generally shouldn't be a problem. Set keywords to underlined, bold, italic, whatever works for you.
Your other examples I can see, but at least at my work those are rare edge cases, and I'd rather optimize for the brunt of the work than for those. Of course at other places those might be much more of a concern.
What about Intercal?
MAKING SQL QUERIES IN CAPITAL LETTERS MAKES DATABASE TO SENSE URGENCY AND RUN FASTER.
THANKS, NOW I DON'T HAVE TO HOLD DOWN THE SHIFT KEY WHEN I TYPE ANYMORE!
If you guys think that's cool you should see what I can do with a double negative.
What you can't not do with a double negative?
In english a double negative only reinforces the no if i rember correctly
As a senior query writer, I use caps for begin and end and some other commands, but all caps makes my head hurt. It's like the sql is screaming at me. I think it's more important to have good looking queries with proper indentation.
This.
Highlight important aspects of the worry with caps
Nobody knows (/s) but you don't have to write keywords in upper case (for most DB's default settings anyway).
You can even write them sarcastically like this:
sElEcT * fRoM dUaL
The phrase "SQL programmers" is so fucking weird. SQL isn't a programming language. It's a query language. You don't "program" things with SQL. You utilize SQL as a component of programs for data insertion and lookup, but the actual logic of execution is done in a programming language. Unless you're doing Oracle PL/SQL, in which case why are you giving money to Oracle?
Edit: Damn, this comment made people mad.
SQL is turing complete
So is Tex. And, yet, I still don't put it under the "programming languages I know" section on my resume. Probably because it's not a programming language.
Where you put it is not my problem.
The general census is that latex actually is an example of programming languages sharing semantics with non programming languages and not being intend as a programming language.
since you linked to wikipedia:
The domain of the language is also worth consideration. Markup languages like XML, HTML, or troff, which define structured data, are not usually considered programming languages.[12][13][14] Programming languages may, however, share the syntax with markup languages if a computational semantics is defined. XSLT, for example, is a Turing complete language entirely using XML syntax.[15][16][17] Moreover, LaTeX, which is mostly used for structuring documents, also contains a Turing complete subset.[18][19]
Sometimes even non Turing complete languages are considered a programming language but Turing completeness usually is the criteria agreed upon:
The majority of practical programming languages are Turing complete,[5] and all Turing complete languages can implement the same set of algorithms. ANSI/ISO SQL-92 and Charity are examples of languages that are not Turing complete, yet are often called programming languages.[6][7] However, some authors restrict the term "programming language" to Turing complete languages.[1][8]