daniel

I went from "wow ORMs are cool you don't have to deal with sql" to "ORMs bad" a while ago. But now I think that query builders are also bad. Your code shouldn't build chunks of SQL. Your queries should be fixed, and your code should build up parameters for them. The reason being - this approach makes it much easier to optimize on query-by-query basis while keeping code logic mostly intact. Also makes it trivial to see all entry points that actually hit the database. The upmost reuse on this level would be a set of fields that you send to a query, akin to GraphQL fragments. This is one of few things that GraphQL did right, probably because its queries don't have logic so it's easier to see the right path. As a bonus, I bet a setup like this makes it much easier for LLMs to reason about where the code ends and database interaction starts, and also LLMs are much better at reading raw SQL than they are at reading 101 flavors of different query builders.

sbb zugwlan so scheisse die schweiz sollte sich schämen