News for hackers. Stuff that matters.
Re:Learning Go as a Node.js Developer by imtringued on Friday February 09, 2018 @08:45AM (#16340087)
Mapping objects to tables and back is a solved problem.

Let me tell you one thing that isn't solved yet: Serialization of arbitrary objects to json and back.

How do you deal with two refererences pointing to the same object? Duplicate the data?

What about circular references? Give each object an id and save a symbolic reference?

What about polymorphism? Should a json array be turned into an array or an list or a json map turned into an object or a hashmap?

You need a type discriminator attribute.

ORMs have already solved those problems well.

The actual problem is that databases are distributed systems and you still have to write queries with the still 10 times better querybuilder of your ORM. Just try writing raw JDBC queries. It's so painful I'd still use the ORM even if my project only uses native SQL queries via the ORM api.

You will probably now ask what's the point of ORMs if you still have to write queries? Well, it's in the damn name. Object relational mapper. It maps stuff. It's not advertised as WYQFY. "Writes your queries for you"

There are no comments on this comment yet.