ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #prisma
Prisma's include and select options collapse N+1 query loops into a single database round trip. This post shows how to fetch posts with authors and limited comments in one query, when to choose select over include to avoid over-fetching, and how to verify the generated SQL with query logging.
Treat Prisma model instances as internal data. Wrap user-facing reads with an explicit select allowlist and return plain DTOs to avoid leaking password hashes and tokens.
Wrap related Prisma Client writes so they commit together or roll back together, with worked examples and limits.
Learn how Prisma’s Fluent API compares to declarative include/select for fetching relational data, with a concrete User‑Post‑Comment example, performance trade‑offs, and guidance on when to use each approach.
A decision guide for choosing between Prisma interactive transactions and batch operations (createMany, updateMany, deleteMany) based on atomicity scope, isolation needs, throughput, and middleware requirements. Includes a concrete seeding example and validation checklist.
Learn how Prisma Client's `include` option gives you type‑safe eager loading of relations, with a concrete schema, query example, and the practical limits you need to watch.
Prisma $transaction enables atomic multi-table writes, but requires short callbacks, connection pool awareness, and exclusion of side effects. This guide covers requirements, failure modes, operational checks, and design alternatives.
Learn how to use Prisma's $transaction API to ensure atomic database writes, preventing partial data updates with sequential and interactive transaction patterns.
When pulling related data with Prisma Client, ‘include’ pulls full objects while ‘select’ fetches only specified fields. This article explains the semantics, trade‑offs, and illustrates a concrete User‑Post example to help you decide the right approach.
typescript
nodejs