1719
I love it when I have to scream at a computer
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Oct 2023
1719 points (98.8% liked)
Programmer Humor
31700 readers
763 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
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
Partially, yes. I personally use an IDE with excellent syntax highlighting and those have been around for at least two decades. You are, however, often transplanting your SQL between a variety of environments and in some of those syntax highlighting is unavailable (for me at least) - the all caps does help in those rare situations.
More importantly though it helps clearly differentiate between those control keywords (which are universal) and data labels (which are specific to your business domain). If I'm consulting on a complex system that I only partially understand it's extremely helpful to be able to quickly identify data labels that I'm unfamiliar with to research.
You say that as if AS400 systems with only console access don't exist anymore.
Well then use all-caps keywords whenever working on those systems, I don't care. But an edge case like that shouldn't dictate the default for everyone else who doesn't have to work on that, that's all I'm saying.
There are several cases where you'll be limited to console only, or log files, or many many other situations. Good coding practices just makes life easier all around.
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.
JetBrains IDEs - IntelliJ, WebStorm, PyCharm, GoLand, etc., all support highlighting SQL embedded in another source file or even inside markup files like YAML. Does your IDE not support this?
RustRover isn't ready for actual usage, I've tried it
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?
Happens at compile time! It's relatively quick. You can also run a command to write the query results to file for offline type checking which is mostly useful for CI
Sublime is actually great at that especially when I keep my SQL in heredocs.
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.
Just some key words in uppercase (FROM, JOIN,WHERE,etc) so they pop out
Yea - you want the structure in a recognizable form so that you can quickly confirm code patterns for comprehension.
THE DATABASE CAN'T HEAR ME IF I DON'T SCREAM
What about Intercal?