MCP servers and skills: search, filter by where they run, and compare.
Starting at the 0.11 release, the .insert() method on the SQL builder accepts only an array of row objects. The single object overload that previously allowed .insert({ field: value }) is removed.
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Skills under test: prisma next supabase , prisma next contract , prisma next queries .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
<! Release bump to 0.15.0 (PR 988): the version bump itself. Every packages/3 extensions/ /package.json advances to 0.15.0 (version field + workspace: specifier lockstep; one stray workspace: in targe
OfficialInstructionsApache-2.0★ 415 in collectionNo key
<! Release bump to 0.15.0 (PR 988): the version bump itself. Every workspace package.json advances to 0.15.0 (version field + workspace: specifier lockstep), and the examples/supabase contract artifac
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.10 release, the SQL family's contract serializer ( familyInstance.validateContract , the seam every on disk contract read now crosses) is strict about the storage.types polymorphic s
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.10 release, the SQL family's contract serializer ( familyInstance.validateContract , the seam every on disk contract read now crosses) is strict about the storage.types polymorphic s
OfficialInstructionsApache-2.0★ 415 in collectionNo key
<! TML 2843: @prisma next/sqlite gained a facade level transaction API ( SqliteClient.transaction() + SqliteTransactionContext ), mirroring the existing Postgres facade. Purely additive public surface
OfficialInstructionsApache-2.0★ 415 in collectionNo key
<! TML 2500(M3b): advances the examples/supabase walking skeleton to wire a cross space FK from public.Profile.userId to supabase:auth.AuthUser.id with a cascading delete. The diff is new sample code
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Load this guide when db.ts imports from @prisma next/postgres/runtime .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.12 release, the SQL runtime's marker verification API is simplified. The previous verify: { mode; requireMarker } option carried two concerns — when to verify and whether to throw on
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.12 release, the framework ExprVisitor<R interface in @prisma next/sql relational core/ast gained a required method:
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Who stands behind it
