Today, we are issuing a 6.11.1 patch release.

Bug fixes

• In Prisma ORM version 6.11.0, we shipped a bug fix for Prisma that allows using Prisma Postgres with direct TCP connections with Prisma Driver Adapters. This fix required refactoring the Prisma Client initialization logic, and while several test cases were added, an edge case was missing, causing https://github.com/prisma/prisma/issues/27569. Namely, using @prisma/client with @prisma/extension-accelerate on a prisma+postgres://... connection string, while generating the Prisma Client definitions via prisma generate, resulted in a PrismaClientInitializationError.

  This is now fixed, so we highly recommend upgrading to version 6.11.1.

  Reminder: when using Prisma Accelerate, we highly encourage you to generate your Prisma Client definitions via prisma generate --no-engine.

• We've fixed an issue that would occur when using arrays as aggregation fields with the query compiler. These queries would fail with a confusing data mapping error. They should now work as expected.

Today, we are excited to share the 6.11.0 stable release 🎉

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

Prisma ORM without Rust engines for MySQL/MariaDB, Neon & CockroachDB (Preview)

We are in the process of removing the Rust engines from Prisma ORM. This week, we're adding Preview support for the Rust-free Prisma ORM version for MySQL via a new @prisma/adapter-mariadb driver adapter, as well as for Neon and CockroachDB via the already existing @prisma/adapter-neon and @prisma/adapter-pg adapters.

Note: The mariadb driver is compatible with all MySQL databases. It's the recommended option to use MySQL with Prisma ORM when using driver adapters.

To use it, enable the queryCompiler and driverAdapters feature flags on your generator block, install the driver adapter for your database and start querying!

generator client {
  provider        = "prisma-client-js" // or `prisma-client`
  output          = "../generated/prisma"
  previewFeatures = ["queryCompiler", "driverAdapters"]
}

📚Learn more in the docs.

Stop and remove local Prisma Postgres instances via CLI

You can start a local Prisma Postgres instance using the prisma dev --name mydb command or via the Prisma VS Code extension UI.

If you start a local instance via the Prisma CLI, you can simply kill the process to stop the instance. However, when you start instances via the VS Code extension UI, you could also only stop them via the UI—not via the CLI.

This changes in this release: You can now also stop local Prisma Postgres instances and remove them from your file system via the Prisma CLI:

• prisma dev stop <globs>: Stops one or more local Prisma Postgres instances
• prisma dev rm <globs>: Removes one or more local Prisma Postgres instances from your file system

📚Learn more in the docs.

Ready-to-run examples for new prisma-client generator

Our new prisma-client generator is more flexible, provides more control about the generated code, works with various JS runtimes and comes with ESM support out-of-the-box.

To make it easier for you to try it out, we created a few ready-to-run example projects so you can see the new generator in action:

• nextjs-starter-webpack
• nextjs-starter-turbopack
• neextjs-starter-webpack-monorepo
• nextjs-starter-webpack-with-middleware

Bug fixes in VS Code embedded Prisma Studio

Have you already seen the new look of Prisma Studio when it's embedded directly in VS Code via the Prisma VS Code extension? In this release, we fixed a few bugs that you all have reported:

• Fixed an issue with writing and deleting from tables with UUIDs
• Fixed an issue with saving data in fullscreen mode
• Fixed an issue with updating the schema when the refresh button is clicked

Let us know in case you hit any snags with Prisma ORM by opening a new issue.

Other news

Embed Prisma Studio in your own tools and projects

If you're using Prisma Postgres (yourself or by offering it to your own users), you can now embed Prisma Studio to offer an amazing data editing experience to your users via the @prisma/studio-core npm package.

Try out the demo that shows how to integrate Prisma Studio in your own apps!

Predict your Prisma Postgres bill with our new Pricing Calculator

Prisma Postgres comes with a pricing model that seems too simple to be true: You're charged based on storage and operations—not CPU, compute hours or any other resource-based metrics.

While it's simple, it may feel unfamiliar because it's so different from existing pricing models. To understand how much you'd pay for Prisma Postgres running your app, you can now use our Pricing Calculator. Put in the predicted storage and number of operations to see how much you're going to be charged on each plan.

Prisma Postgres now available for all Postgres templates in Vercel Marketplace

On vercel.com/templates, you can find lots of one-click-deploy application templates! We recently worked with the Vercel team to get Prisma Postgres working with all templates requiring a PostgreSQL database, for example:

• Next.js SaaS Starter with Drizzle ORM
• Postgres SvelteKit Starter with Postgres.js
• Next.js + PostgreSQL Auth Starter with Drizzle ORM
• … and a lot more

Connecting to Prisma Postgres with any tool is now faster

We recently enabled the option to connect to Prisma Postgres with any tool via direct TCP connections. In this release, we have reduced the connection latency so your first request is now faster.

New region for Prisma Postgres: Frankfurt (eu-central-1)

We keep expanding Prisma Postgres availability across the globe! After having added San Francisco just a few weeks ago, we're now adding Frankfurt based on another poll we ran on X. Here are all the regions where you can spin up Prisma Postgres instances today:

• eu-central-1: Frankfurt (new!)
• eu-west-3: Paris
• us-west-1: San Francisco
• us-east-1: North Virginia
• ap-northeast-1: Tokyo
• ap-southeast-1: Singapore

Keep an eye on our X account to take part in the poll and vote for the next availability zone of Prisma Postgres!