This prerelease adds MySQL ORM writes, named MongoDB index handling, and convenience database types, while improving extension-pack discovery for PostgreSQL extensions. It also changes runtime validation and extension requirements in ways that may require application and extension updates; the release notes provide upgrade recipes and specific migration steps.
affected
Prisma 8 application and extension authors—especially MongoDB users and projects composing PostgreSQL extension packs—may need contract, API, and input-validation updates.
action
Use the matching app or extension upgrade recipe for this prerelease and perform the documented contract-emission and migration steps.
release_signals
-MongoDB indexes must carry names in contracts and migrations; duplicate inferred names are refused. Extension APIs for MongoDB indexes and index operations now require names.
-`prisma6Schema()` preserves Prisma 6 index-reading behavior, including refusing certain duplicate indexes and retaining some indexes that produce a new storage hash.
-PostgreSQL extension packs declare extensions in the unbound namespace; applications may not separately declare an extension already declared by a composed pack.
-`mongo()` and `mongoStatic()` require the extension packs used by the contract, and MongoDB `contract.json` must include `target`.
-`supabase()` and `postgres()` validate database inputs immediately; invalid, conflicting, or null inputs now fail, and Supabase no longer accepts `pg.Client`.
!The extension APIs `mongoStandardCodecs` and `buildStandardCodecRegistry` are removed.
+
migration_steps5 steps
01Follow the release's app or extension upgrade recipe for the applicable changes.
02After upgrading, run `prisma contract emit` once to restamp extension-generated contracts with the installed package version.
03For MongoDB indexes, emit the contract, run the script supplied by the app recipe to name indexes in migration snapshots, then run `prisma db sign` or plan a migration; name any indexes that would otherwise collide.
04For pgvector, PostGIS, ParadeDB, or citext packs, remove the application's duplicate extension declaration, run `prisma contract emit`, then run `prisma db migrate` to apply the pack migration without changing the database.
05For MongoDB projects composing extension packs, pass each pack's runtime descriptor to `mongo({ extensions })` and `mongoStatic({ extensions })`; ensure MongoDB contract JSON includes `target`.
This prerelease introduces PostgreSQL convenience date/time types and `Duration`, moves value objects into the storage plane, and adds PostgreSQL checks for value-object and discriminator columns. It also changes MongoDB APIs to use execution contexts and stack-created drivers, adds contract-declared PostgreSQL extensions, and broadens Prisma 7 and MySQL read support.
affected
Applications and extensions upgrading from v8.0.0-rc.21 are affected, especially those using PostgreSQL date/time types or value objects and MongoDB query, runtime, or driver APIs.
action
Because this is a prerelease with multiple breaking changes, follow the linked app or extension upgrade recipe before upgrading, and restamp contracts with `prisma contract emit`.
This release introduces significant changes including Postgres full-text search, prepared ORM reads, and schema file splitting. It also includes several breaking changes requiring careful migration.
affected
Projects using Prisma ORM, especially those with custom configurations or relying on `dbgenerated` defaults, are affected by these changes.
action
Follow the provided upgrade recipes for detailed migration steps.
release_signals
-Engine peer moves to `@prisma/cli-engine@0.6.1`, requiring `definePrismaConfig` instead of `defineConfig`.
This release completes the rename from Prisma Next to Prisma 8, introduces named model and result types, and adds attribute completion to the language server. It includes breaking changes for environment variables and contract types.
affected
Users relying on `PRISMA_NEXT_*` environment variables or needing to update contract types for to-one relations are affected.
action
Update environment variables and run `prisma contract emit` to ensure compatibility with the new contract format.
release_signals
-CLI environment variables lose the `NEXT_` infix. Rename `PRISMA_NEXT_*` to `PRISMA_*` in shell profiles, `.env` files, and CI.
MySQL now supports ORM writes.
+PostgreSQL scalar types gain convenience types; SQLite and MySQL gain convenience date and time types.
+`mongo()` accepts extension packs, and `supabase()` accepts the options supported by `postgres()`.
+PostgreSQL extension packs locate extensions through the connection search path, supporting setups such as Supabase.
+Prisma ORM no longer refuses to start when loaded from more than one copy.
-
PostgreSQL `DateTime`, `Date`, and `Time` now use convenience defaults and read JavaScript `Date` or strings instead of `Temporal` values; use `TimestamptzTemporal`, `DateTemporal`, or `TimeTemporal` to retain the prior behavior. `temporal.CreatedAt` and `temporal.UpdatedAt` now use the new `DateTime`, and their `String` and `JsDate` variants are removed.
-Value objects move from the domain plane to `storage.namespaces.<ns>.entries.valueObject`; changing one is a migration, and contracts that retain the old `valueObjects` location are rejected. PostgreSQL migrations add checks and fail if existing rows violate them.
-MongoDB query, raw, ORM, and runtime APIs now take an execution context; several old enum helpers and runtime options are removed, and driver creation uses a runtime descriptor on the execution stack.
-`createMongoDriver` and `MongoDriverImpl` are no longer exported; extension-facing driver and SQL execution-stack types also change.
-PostgreSQL `contract infer`/`contract print` now emit convenience types; re-inferred `timestamptz` fields default to JavaScript `Date` and lose microseconds unless configured to preserve a string and precision.
!Removed `temporal.CreatedAt.String`, `temporal.CreatedAt.JsDate`, `temporal.UpdatedAt.String`, and `temporal.UpdatedAt.JsDate` variants.
!Removed MongoDB exports `createMongoDriver` and `MongoDriverImpl`, as well as `buildMongoEnums`, `MongoEnumAccessors`, `MongoOrmEnums`, and `ORM.MUTATION_DEFAULTS_MISSING`.
+PostgreSQL contracts can declare required extensions, including pgvector, PostGIS, ParadeDB, and the new citext pack.
+Adds PostgreSQL `Duration` and convenience `DateTime`, `Date`, and `Time` types with configurable storage, precision, and read representation.
+MongoDB clients create their driver from the execution stack; `connect()` can safely be called again.
+Prisma 7 reader now supports every PostgreSQL `@db.*` type Prisma 7 accepts; MySQL gains ORM and SQL builder reads.
+PostgreSQL derives checks for value-object and discriminator columns on managed tables.
migration_steps6 steps
01Follow the linked app or extension upgrade recipe for the 8.0.0-rc.21-to-8.0.0-rc.22 upgrade; the app recipe specifies step order.
02After upgrading, run `prisma contract emit` once to restamp contracts with the installed package version.
03To preserve prior PostgreSQL Temporal behavior, rename fields to `TimestamptzTemporal`, `DateTemporal`, or `TimeTemporal` (and use the corresponding TypeScript helpers).
04For value objects, run the app recipe's script to rewrite contracts, snapshots, and migrations, then sign each database before re-emitting.
05After re-emitting a contract read by `prisma7Schema(...)`, run `prisma db sign`; for inferred `timestamptz` fields that must retain string values and microseconds, use `DateTime(as: string, precision: 6)`.
06For MongoDB, replace `{ contract }` query/raw setup with a context from `mongoStatic({ contract })` or `mongo({ contract })`, and use the runtime driver descriptor on the execution stack.
PSL models without `@@map` now name their tables exactly as written, requiring explicit `@@map` for previous behavior.
-Every PSL schema file must start with `// use prisma-8` to be included in the contract.
-`dbgenerated(...)` is removed; raw SQL defaults must use `sql` tagged literals.
-Column defaults must now be values that the column's data type accepts.
!`.defaultSql('...')` in TypeScript contract builder is deprecated in favor of `.default(now())`, `.default(autoincrement())`, or ``.default(sql`...`)``.
+Postgres full-text search support.
+Prepared ORM reads and aggregates.
+Schemas can now be split across several files.
+Prisma 7 projects can use their existing `schema.prisma` as the Prisma 8 contract source.
migration_steps5 steps
01Update `@prisma/cli-engine` to version 0.6.1 and replace `defineConfig` with `definePrismaConfig`.
02Run the `add-model-map` script to add `@@map` to models without it.
03Add `// use prisma-8` to the first line of every PSL schema file.
04Replace `dbgenerated(...)` with `sql` tagged literals or appropriate functions like `now()`.
05Ensure column defaults match the column's data type.
To-one relations record their nullability in the contract. Run `prisma contract emit` once after upgrading to update `contract.d.ts` with the new `Models` namespace.
!The schema header `// use prisma-next` is deprecated in favor of `// use prisma-8`. The old header still works but will be rewritten to the new form when formatting the file.
+Named model and result types in `contract.d.ts` with `Models` namespace and `models` constant.
+Attribute completion in the language server for field, model, and block attributes.
+`db sign` can choose or skip the ref it advances with `--advance-ref` and `--no-advance-ref` options.
migration_steps2 steps
01Rename `PRISMA_NEXT_*` environment variables to `PRISMA_*`.
02Run `prisma contract emit` to update `contract.d.ts` with the new `Models` namespace.