> If you use an ORM-like coding style Not the op but for me the defining word here is "coding style". Would be interesting to see if their is any serious ORM

> If you use an ORM-like coding style Not the op but for me the defining word here is "coding style". Would be interesting to see if their is any serious ORM frameworks that recommends ops steps. That kind of steps you normally see in novice code, that does not understand sql or the orm framework. So for a novice a fetchall into memory, loop over each row in memory, and after each modification commit, not a issue, ignorance is bliss. And it will most probably stay a non issue until performance hits are taken, then optimization can take place. This time maybe with a senior that will look at the sql logs and show the junior the error in his ways. At least with the junior code you could move the product forward... but maybe it a case of one step forward, two step back.