undefined | Better HN

0 pointsjrumbut3y ago0 comments

An ORM allows you to encode a relationship once then use it for many different queries, I think that's the idea.

0 comments

But a view also does that? Like, if you want to assemble information about a user from several different tables, you can have a view that does the join for you.

jrumbutOP3y ago

Sure, but people never use those. Also it gets back to the discoverability issue. The ORM documents relationships with the rest of the model code, if you have a poorly named view in a large, complex schema it may be hard to find. You could reinvent the wheel easily.

Like everything with SQL, you can solve the problem but sometimes the solution isn't elegant. People want elegance.

Justsignedup3y ago

This is an accurate description of how I think of this problem. And it would be tough to describe all this:

- table a joins b yay a view

- table b joins c yay a view

- table c join d yay a view

- table a joins to d. well technically it can, but are you really gonna write all the permutations of views for every possible join?

ORMs encode that nicely so I can easily walk the relationships and get to the query I need.

1 more reply

bambax3y ago

> Sure, but people never use those

Why not? I use views all the time, and they seem pretty elegant and simple to me.

j / k navigate · click thread line to collapse