Learn Prisma Next from its expanded docs and use native PostgreSQL enums

Prisma Next docs now cover Fundamentals, data modeling, migrations, middleware and extensions, contract authoring, and an API reference. The schema also reads native PostgreSQL enums, including types created outside Prisma, as typed value unions.

Prisma ORM removes the destructive migrate-reset tool from its MCP server and makes the typedSql preview feature visible to language tools.

Highlights

DocsPrisma Next documentation now covers the full surface

Learning Prisma Next meant working from the setup guides and scattered posts. The docs now cover Fundamentals, data modeling, migrations, middleware and extensions, contract authoring, and an API reference, with guides behind a version dropdown.

Note: Prisma Next is in Early Access. Scope and behavior may still change.

Start with the Prisma Next docs; the setup guides from last week remain the fastest entry point.

NewUse native PostgreSQL enums in Prisma Next

Enum types created outside Prisma, for example by Supabase, used to read as plain strings. Prisma Next now maps native PostgreSQL enum types to typed value unions, so reads and writes are checked against the enum's values.

// account_status is a native PostgreSQL enum type
const account = await db.account.findFirst();

// account.status: "active" | "paused" | "closed"

Shipped in prisma/prisma-next#906.

Prisma Next

Prisma Next reads external enum types as typed unions and tightens contract inference on stack extensions.

Improved

Prisma Next contract infer now writes a contract covering only your app's own tables when running on a stack extension such as the Supabase pack, instead of repeating what the extension already declares. (prisma/prisma-next#919)

Prisma ORM

Prisma ORM removes a destructive agent-facing tool and surfaces the typedSql preview feature.

Improved

The Prisma MCP server no longer exposes a migrate-reset tool. An agent that needs a reset must run prisma migrate reset through the CLI, where the safety checkpoint requires explicit confirmation before the database is dropped. (prisma/prisma#29691)
The typedSql preview feature now appears in language-tool autocomplete and in schema validation error suggestions. It was already fully functional when enabled explicitly. (prisma/prisma-engines#5836)

Need help applying these changes in production? Prisma Enterprise Support can help with schema design, performance, security, and compliance.