this post was submitted on 19 Oct 2023
1697 points (98.8% liked)

Programmer Humor

32495 readers
259 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] hikaru755@feddit.de 20 points 1 year ago* (last edited 1 year ago) (16 children)

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

[–] Stumblinbear@pawb.social 7 points 1 year ago* (last edited 1 year ago) (9 children)

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.

[–] hikaru755@feddit.de 2 points 1 year ago (5 children)

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.

[–] Stumblinbear@pawb.social 2 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] hikaru755@feddit.de 2 points 1 year ago (1 children)

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.

[–] Stumblinbear@pawb.social 1 points 1 year ago* (last edited 1 year ago) (1 children)

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

[–] hikaru755@feddit.de 2 points 1 year ago (1 children)

Oh, that sounds really cool! At what time does this validation happen? While you code, or later at build time?

[–] Stumblinbear@pawb.social 3 points 1 year ago

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

load more comments (3 replies)
load more comments (6 replies)
load more comments (12 replies)