An ORM is not a "query builder"
An ORM turns your result into a collection of objects. THAT is what an ORM is for and about.
The fact that they are built on top of query builders and lighten the load when developing is just a handy side effect.
An ORM turns your result into a collection of objects. THAT is what an ORM is for and about.
The fact that they are built on top of query builders and lighten the load when developing is just a handy side effect.
Sounds nice, but in reality, latencies, networks, massive data sets, atomicity of operations, and a whole host of other annoyances get in the way.
... so it ends up being simpler and easier in the long run to be very explicit about your interactions with data stores. Took me a long time to get to this point.