8 ms·
>Right, how often do you actually need to do this? In my experience query building to this degree is usually a sign of over optimising for code reuse where it i
by flukus 8y ago
>Right, how often do you actually need to do this? In my experience query building to this degree is usually a sign of over optimising for code reuse where it isn't really needed.
I need to very often and it's rarely about code reuse. You requirements like "on the client list screen we want to be able to search by client id or client name and we want to be able to sort by last login time or name"? What about writing an API, that's 90% handling things like this.
And then there's the other cases ORM's solve, like representing data as something more than a 2D table.
- lugg 8y agoThat problem is a query building problem you probably want to look into graphql. ORMs sometimes come with query builders that help things but in my experience it's not worth having to clusterbomb my codebase for it.
- platz 8y agoImplementing graphql, which you can only apply in a limited number of client-server scenarios, to solve a relatively trivial problem, sounds like the clusterbomb or a good 2,000 lb mk-84 general purpose bomb to me e.g. graphql is not a panacea