Re:What ORMs have taught me: just learn SQL (2014)
by spdionis on Monday December 18, 2017 @06:31AM
(#15950927)
5 years down the road, good luck refactoring your application to not query the same object from the database 3-4 times, and load it only once instead.
[ Parent
| on HN ]
Re:What ORMs have taught me: just learn SQL (2014)
by oceanswave on Monday December 18, 2017 @07:45AM
(#15951233)
You’ve probably refactored the ORM Data layer 3 times in that time period as ORM producers have a hard time figuring out the interface which they wish to provide you
Re:What ORMs have taught me: just learn SQL (2014)
by spdionis on Monday December 18, 2017 @08:00AM
(#15951294)
Agreed. I'd say my point still stands because duplicated database calls affect performance and scalability and this can grind the project to a halt at a certain point. Also this refactor is much more dangerous/probably buggy.
On the other hand refactoring your data logic is just business as usual, and you will probably do it in both cases anyway.
Re:What ORMs have taught me: just learn SQL (2014)
by guru4consulting on Monday December 18, 2017 @12:23PM
(#15953318)
caching is a very tricky area with tons of pitfalls. In my opinion, the ORM should not be caching. Let the clients (or any other layer) cache/clear based on their needs.