Hacker News Reader

I use a data mapping ORM and I've literally not have any of these concerns. They are all non-issues.

The first item about querying is relevant but all ORMs allow you to drop into SQL to execute a complex reporting-style query. It's not really necessary if you are just querying in objects to manipulate (which is what ORMs are good for).

View on HN

A data mapper is not an ORM, it's a data mapper. It's a different access pattern.

But I do agree that data mappers tend to be better.

This is the 'data mapper' vs 'active record' debate and I would argue both are sub-categories of 'Object-relational mapper.' I've seen multiple people in this thread even include query builders in their definition of ORM. I'm starting to wonder if much of the disagreement in this thread is caused by everyone having their own definition of ORM.

My comment wasn't meant to be a refutation of anything, merely an observation.

https://medium.com/oceanize-geeks/the-active-record-and-data...

Reply on news.ycombinator.com