4.3 KiB
client-api-mapping
Create the Prisma 8 client, then map each Prisma ORM 6 or 7 call to it; five differences break most rewrites.
Priority
CRITICAL
Why It Matters
The Prisma 8 client chains calls instead of taking one options object, and a schema read
through prisma7Schema(...) changes a few lookups and types. Some of these compile and then
fail at runtime or write wrong data.
The client
One client for the app and the seed script, reading the same DATABASE_URL as before:
// src/db.ts
import postgres from "@prisma/orm-postgres/runtime";
import { contractFromJson } from "@prisma/orm-postgres/static";
import type { Contract } from "./prisma/contract.js";
import contractJson from "./prisma/contract.json";
export const db = postgres({ contract: contractFromJson<Contract>(contractJson), url: process.env["DATABASE_URL"]! });
In a CommonJS .ts file, import the JSON without the with { type: "json" } attribute the
prisma-8 skill shows: the attribute fails there with TS2856 and is only valid in .mts files.
On Compute, prisma-compute replaces this client with service.load().db.client.
Old call to new call
Queries start at db.orm.public.<Model>. For anything not listed here, follow the synced
prisma-8 skill (references/queries.md, references/runtime.md).
| Prisma ORM 6 / 7 | Prisma 8 |
|---|---|
findMany({ where, orderBy }) |
.where({...}).orderBy((m) => m.field.asc()).all() |
include: { _count: { select: { posts: true } } } |
.include("posts", (p) => p.count()); the number is row.posts, not row._count.posts |
orderBy: { votes: { _count: "desc" } } |
.orderBy((p) => p.votes.count().desc()) |
findUnique({ where: { id } }) |
.first({ id }) |
findUnique on an @unique or @@unique field |
.where({...}).first() |
create({ data: { ..., votes: { create: {...} } } }) |
.create({ ..., votes: (v) => v.create([{...}]) }) |
deleteMany({ where }) then .count |
.where({...}).deleteAndCount() |
deleteMany() with no filter (seeds, tests) |
.where((m) => m.id.isNotNull()).deleteAll(): writes need a filter |
createMany({ data: [...] }) |
.createAll([...]) |
count({ where }) |
.where({...}).aggregate((a) => ({ total: a.count() })) |
Object.values(PostStatus) from @prisma/client |
db.nativeEnums.public.PostStatus.values |
$queryRaw`SELECT 1` (health checks) |
db.execute(db.raw.sql`SELECT 1`.affectedCount().build()) |
What has no Prisma 8 form yet, such as increment in an update, is listed in
Coming from Prisma ORM 7.
The five differences
- Unique lookups use
.first(...)or.where(...).first(). A 6/7@uniqueor@@uniquebecomes a unique index, whichwhereUniquedoes not accept, so do not reach for it. - Enums are under
db.nativeEnums, notdb.enums. The values are the same strings. DateTimemay read as a string ("2026-11-06 09:10:48.497", UTC, no offset) at@prisma/orm-postgres@8.0.0-rc.20.row.createdAt.toISOString()then throws at runtime, often in a templatetscnever checks. Check the installed version's behavior in theprisma-8skill before converting.@default(now())is filled by the database at rc.20, so atimestampcolumn gets the database's local time where 6/7 sent UTC. IfSHOW timezoneis notUTC, tell the user rather than changing data: new rows will store a different time than before, which is a behavior change the user has to decide on.- Templates and other code
tscdoes not check still read the old shapes. Search views (.ejs,.hbs,.pug) and plain.jsfiles for_count.,.toISOString()on dates, and enum imports, and change them with the queries.
Bad
const board = await db.orm.public.Board.whereUnique({ slug }).first(); // does not compile
<%= post._count.votes %> <!-- an .ejs view tsc never checks: undefined after the rewrite -->
Good
const board = await db.orm.public.Board.where({ slug }).first();
const post = await db.orm.public.Post.include("votes", (v) => v.count()).first({ id }); // post.votes
References
- Guide, step 5
- The synced
prisma-8skill, authoritative for the installed client