@prisma/pg-worker

Persists your databases across prisma dev invocations.

Enables you to have multiple local Prisma Postgres instances running at the same time.

Running prisma init now uses local Prisma Postgres by default.

us-west-1: San Francisco (new!)

Checking the status of your migrations (e.g. telling you if migrations haven't been applied)

Creating and running schema migrations for you

Authenticating you with the Prisma Console

Provisioning new Prisma Postgres instances so you can start coding right away

⚠️ Note that there have been breaking changes to the prismaSchemaFolder Preview feature in the last 6.6.0 release.

Note: The prisma-client generator is currently in Early Access and will likely have some breaking changes in the next releases.

If you are using the prismaSchemaFolder Preview feature to split your Prisma schema into multiple files, you may encounter some breaking changes in this version.

Pass the the --schema option to your Prisma CLI command (e.g. prisma migrate dev --schema ./prisma/schema)

Set the prisma.schema field in package.json:

Using the defineConfig helper exported by prisma/config.

Using the PrismaConfig utility type exported by Prisma.

Allow for binaries to be loaded from local network. Thank you @RaHehl!

Enhance type safety of the AtLeast utility type. Thank you @de-novo!

Resolve a race condition in the NextJS monorepo plugin. Thank you @toniopelo!

allow for filtering out spans with PrismaInstrumentation. Thank you @overbit!

Add take or limit to updateMany() & deleteMany()

Prisma interactive transaction ignores DB exception on commit (with triggers)

prisma db pull non-deterministically sorts generator fields

no entry found for key error on views<->model relations

Adding onUpdate data to the DMMF in @prisma/generator-helper