Is ORM still an anti-pattern?

Re:Is ORM still an anti-pattern? by erik_seaberg on Tuesday June 27, 2023 @04:58PM (#36498556)

This. Use a good one unless you want to own half of a poor one.

[ Parent | on HN ]

Re:Is ORM still an anti-pattern? by wredue on Tuesday June 27, 2023 @07:37PM (#36500230)

This is just a claim that everyone who advocates for ORMs makes, but it’s not reality.

[ Parent | on HN ]

Re:Is ORM still an anti-pattern? by erik_seaberg on Wednesday June 28, 2023 @12:13AM (#36502193)

The third time I have to figure out whether to write obj.setCreatedAt(rs.getTimestamp("created_at", calendar)) or obj.setCreatedAt(rs.getLong("created_at")) I'm going to write code to look at the schema and the setter and figure it out automatically. And that’s where new ORMs come from.

[ Parent | on HN ]

Re:Is ORM still an anti-pattern? by isbvhodnvemrwvn on Wednesday June 28, 2023 @03:15AM (#36503366)

Query builders solve those problems without the complexity of ORMs.

[ Parent | on HN ]

Re:Is ORM still an anti-pattern? by mschuster91 on Wednesday June 28, 2023 @07:02AM (#36504788)

Query builders tend to get tediously verbose compared to a plain old `$entityManager->persist($object)`

[ Parent | on HN ]