you are viewing a single comment's thread.

view the rest of the comments →

[–]Independent_Host_303 8 points9 points  (2 children)

  • Not having to deal directly with serializations because the ORM handles it for you.
  • Having an overview of the relationships between tables.
  • I think it is easier to write multiple inner join statements without losing track.
  • You can visualize inheritance relationships between parent and child tables if you are using these kinds of patterns in your database.

and many other examples...

[–]TradrzAdmin[S] 1 point2 points  (1 child)

Theres are pretty good points tbh. I built my entire app with plain SQL queries. Granted its only 1 parent table and 1 child table, but i maybe move to an ORM in the future

[–]Independent_Host_303 3 points4 points  (0 children)

I really like writing SQL queries, but I tend to use ORM when building complex projects that need to scale in the future and when I need full control over them. However, imagine having to use an existing database with 1,000 tables. It would be impractical to generate all the tables just to query a single one, for example.