Blog

I sent the same query down a transaction-mode pooler and a session-mode one into the same Postgres instance, and wrote down every place the answers diverged.

A sensitive column passes through five hops on its way from Postgres to a browser, and a Prisma select only closes the first one — this traces all five with measured runs, including the RSC payload that a TypeScript props interface does not narrow.

Prisma will happily turn one findMany into 133 statements, and the include that replaces them is not one query either, so this walks through the real logged SQL for four versions of the same read against a 132-post table.

Prisma 7 eliminated the Rust binary and closed the performance gap. So why are teams still choosing Drizzle? The real answer is about SQL transparency, bundle size, and who owns complexity.