this post was submitted on 01 Apr 2025
2 points (100.0% liked)
programming
258 readers
3 users here now
-
Post about programming, interesting repos, learning to program, etc. Let's try to keep free software posts in the c/libre comm unless the post is about the programming/is to the repo.
-
Do not doxx yourself by posting a repo that is yours and in any way leads to your personally identifying information. Use reports if necessary to alert mods to a potential doxxing.
-
Be kind, keep struggle sessions focused on the topic of programming.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Amen! SQL is by far the most powerful and easiest to use query language and I will fight anyone who tells me different. Raw SQL is easier to work with, easier to optimize and easier to analyze - why would anyone want to give this up?
Thankfully I've been seeing some positive movement in the industry away from ORMs, query builders and other such crap
I still like a good query builder in the right context, like in the software I have to use a ton (ArcPro) you can quickly slap a
SELECT * FROM <table> WHERE table.shape INTERSECTS input.shapeusing some drop downs and immediately discard the query once the selection is made.For anything else where the selection is used repeatedly, it should be written in SQL so it can be profiles and debugged.
yeah that's fair enough. I was just thinking about backend developement since that's what I mostly do. Query builders are still somewhat popular in that space unfortunately. Even this website uses a query builder, which has caused the devs a lot of problems because queries become impossible to optimise
Wait what... Why? Is it at least plaintext? Or like an orm? Query builders should be a way to generate a SQL starting point...
I've used Metabase to do BI on databases before, and that has a pretty decent query builder, but it also lets you see the exact SQL it generates and convert the query to raw SQL at any point. Why would you ever lock a builder into your workflow...
It's a framework called "Diesel" and I have absolutely no clue why anyone would use something like this. I guess it has some nice stuff like migrations built in, but I don't know why they need any of the other stuff
Oh shit, is that the "ilovejesus" crate?