Querying & Raw SQL

Score the codebase on rename safety, control of emitted SQL, portability, readability at three joins, runtime assembly, discoverability and build cost; then set one default, one named escape hatch, and an enforcement point. Mixed styles collapse to the weakest.

They lose behaviour the mapped model carried - derived values, rounding rules, visibility and soft-delete predicates - and must re-express it in the statement. The rule then exists twice, and only a shared test keeps the copies honest.

Interfaces preserve method names and result shapes, not semantics. Write-back of tracked objects, multi-call atomicity, conflict behaviour, ordering stability and latency do not travel. Keep the boundary for naming, fetch-plan ownership and testability, not portability.

It fits set-shaped and read-heavy work, bulk and streaming paths, latency-sensitive endpoints and shapes close to the tables. It costs hand-assembled graphs, hand-ordered writes, hand-written concurrency checks, and discipline enforced by review rather than by the layer.

A layer calls a routine through a callable form declaring each parameter's direction, not through a plain query. Results arrive as result sets, as output parameter values, or as a returned value, consumed in that order.

The lifecycle semantics the signature cannot express: whether mutating a result persists it, when writes land, whether associations are live, whether repeated reads share an instance, and whether conflicts are checked. Same types, different caller rules.