Hacker News new | ask | show | jobs
by zadikian 88 days ago
Well before LLMs, I already ditched ORMs. What sometimes holds back SQL is not having a convenient way to call it. Statically-typed languages require you to manually set result types unless you use a compile-time query builder, but that's a whole can of worms. Besides that, many client libs aren't so convenient out of the box, so you still need a few of your own helpers.

Also, before jsonb existed, you'd often run into big blobs of properties you don't care to split up into tables. Now it takes some discipline to avoid shoving things into jsonb that shouldn't be.
1 comments
raw_anon_1111 88 days ago
Let me introduce you to LINQ…

https://learn.microsoft.com/en-us/dotnet/csharp/linq/

It solves all of your issues with “ORMs” (it’s really more than just an ORM)

link
zadikian 85 days ago
That's part of the query builder "can of worms" I mentioned. Might be one of the better examples. But idk what limitations it has vs regular SQL, like it mentioned not having native support for count/max.
link