True, v2->v3 was hard due to escaping-by-default, but that was a long time ago. v3 to v4 was trivial and v4 to v5 looks to be similarly easy. Also, I find bus

True, v2->v3 was hard due to escaping-by-default, but that was a long time ago. v3 to v4 was trivial and v4 to v5 looks to be similarly easy. Also, I find business logic sql libs written by typical devs tend to be unreadable and much buggier than AR code. They start clean, but once some other devs make some edits, they end up a jumble of sql concatenation nightmares (even if you use prepared statements, and especially if you've ever switched sql dialects). Given the choice, I think I'd rather see them written as stored procedures. At least that enforces decoupling. I agree with your other points -- less code is more better.