Releases: prisma/prisma
5.4.1
Today, we are issuing the 5.4.1
patch release.
Fix in Prisma Client
Fix in @prisma/adapter-planetscale
5.4.0
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Preview support for PlanetScale and Neon serverless database drivers
We’re excited to announce Preview support for the Neon and PlanetScale serverless database drivers. The PlanetScale and Neon serverless database drivers allow Prisma to connect to your database using protocols besides TCP — HTTP (PlanetScale) or WebSockets (Neon).
To get started with the serverless database drivers, first enable the driverAdapters
Preview feature flag in your Prisma schema:
// schema.prisma
generator client {
provider = "prisma-client-js"
previewFeatures = ["driverAdapters"]
}
Next, to set up Prisma Client to use the serverless database drivers:
PlanetScale
Install the Prisma adapter for PlanetScale and PlanetScale serverless database driver, and undici:
npm install @prisma/adapter-planetscale @planetscale/database undici
Prisma ORM supports Node 16 and up. In Node 18 and up,
undici
is not needed.
Ensure you update the host value in your connection string to aws.connect.psdb.cloud
. You can learn more about this here.
DATABASE_URL='mysql://johndoe:strongpassword@aws.connect.psdb.cloud/clear_nightsky?sslaccept=strict'
Update your Prisma Client instance to use the PlanetScale database driver:
// Import required dependencies
import { connect } from '@planetscale/database';
import { PrismaPlanetScale } from '@prisma/adapter-planetscale';
import { PrismaClient } from '@prisma/client';
import { fetch as undiciFetch } from 'undici';
// Initialize Prisma Client with the PlanetScale serverless database driver
const connection = connect({ url: connectionString, fetch: undiciFetch });
const adapter = new PrismaPlanetScale(connection);
const prisma = new PrismaClient({ adapter });
PlanetScale Driver in 5.7.0 and later
In Prisma 5.7.0, usage of the PlanetScale driver adapter changed to the following:
// For Prisma 5.7.0 and later
// Import required dependencies
import { Client } from '@planetscale/database';
import { PrismaPlanetScale } from '@prisma/adapter-planetscale';
import { PrismaClient } from '@prisma/client';
// Initialize Prisma Client with the PlanetScale serverless database driver
const client = new Client({ url: process.env.DATABASE_URL });
const adapter = new PrismaPlanetScale(client);
const prisma = new PrismaClient({ adapter });
Neon
Install the Prisma adapter for Neon, Neon serverless database driver and undici (WebSockets):
npm install @prisma/adapter-neon @neondatabase/serverless undici
Update your Prisma Client instance to use the Neon serverless database driver:
// Import required dependencies
import { Pool, neonConfig } from '@neondatabase/serverless';
import { PrismaNeon } from '@prisma/adapter-neon';
import { PrismaClient } from '@prisma/client';
import { WebSocket } from 'undici'
neonConfig.webSocketConstructor = WebSocket;
// Initialize Prisma Client with the Neon serverless database driver
const pool = new Pool({ connectionString: process.env.DATABASE_URL });
const adapter = new PrismaNeon(pool);
const prisma = new PrismaClient({ adapter });
Let us know your feedback about the Neon or Planetscale serverless database drivers in the linked GitHub discussions. Create a bug report if you run into any issues.
Early Access support for Turso
Turso is an edge-hosted, distributed database that's based on libSQL, an open-source and open-contribution fork of SQLite, enabling you to bring data closer to your application and minimize query latency.
Since support for Turso is in Early Access, there may be some rough edges which we’re still working on it to improve the API and overall support. Additionally, it is behind the driverAdapters
Preview feature flag. Enable it to get started using Turso in your project:
// schema.prisma
generator client {
provider = "prisma-client-js"
previewFeatures = ["driverAdapters"]
}
Next, install the Prisma Client adapter for Turso and the libSQL
database client
npm install @prisma/adapter-libsql @libsql/client
Update your Prisma Client instance:
// Import required dependencies
import { PrismaClient } from '@prisma/client'
import { PrismaLibSQL } from '@prisma/adapter-libsql'
import { createClient } from '@libsql/client'
// Create a new instance of the libSQL database client
const libsql = createClient({
// @ts-expect-error
url: process.env.TURSO_DATABASE_URL,
authToken: process.env.TURSO_AUTH_TOKEN
})
// Create a Prisma "adapter" for libSQL
const adapter = new PrismaLibSQL(libsql)
// Pass the adapter option to the Prisma Client instance
const prisma = new PrismaClient({ adapter })
You can learn more on how to use Prisma together with Turso in the announcement blog post.
Try it out! Let us know what you think and create a bug report if you run into any issues.
Query performance improvements
In our continued efforts to make Prisma Client faster, we identified and improved the performance of different types of queries.
Relation filters improvements
We made the following improvements to relation filters:
- Removed an unnecessary
INNER JOIN
used in relation filter queries (Big thank you to @KhooHaoYit for helping out) - Use of
LEFT JOIN
's for to-one relations. Previously, Prisma made use of sub-queries to fetch data.
Example Prisma Client query
prisma.comment.findMany({
where: {
post: {
author: {
name: "John"
}
}
}
})
Before 5.4.0
SELECT
"Comment"."id"
FROM
"Comment"
WHERE
("Comment"."id") IN (
SELECT
"t0"."id"
FROM
"Comment" AS "t0"
INNER JOIN "Post" AS "j0" ON ("j0"."id") = ("t0"."postId")
WHERE
(
("j0"."id") IN (
SELECT
"t1"."id"
FROM
"Post" AS "t1"
INNER JOIN "User" AS "j1" ON ("j1"."id") = ("t1"."userId")
WHERE
(
"j1"."name" = $ 1
AND "t1"."id" IS NOT NULL
)
)
AND "t0"."id" IS NOT NULL
)
);
After 5.4.0
SELECT
"Comment"."id"
FROM
"Comment"
LEFT JOIN "Post" AS "j1" ON ("j1"."id") = ("Comment"."postId")
LEFT JOIN "User" AS "j2" ON ("j2"."id") = ("j1"."userId")
WHERE
(
"j2"."name" = $ 1
AND ("j2"."id" IS NOT NULL)
AND ("j1"."id" IS NOT NULL)
);
If you’re interested in more details on the relation query filter improvements, you can take a look at this pull request.
Enum improvements on PostgreSQL and CockroachDB
Previously, when an enum value was used in a query, our Postgres driver would make additional queries to resolve the enum types that were used.
In this release, we’re making improvements by casting enums to TEXT
to avoid the additional roundtrips when resolving the types.
This change should have the most impact if you’re using pgBouncer
or if you’re running Prisma in a serverless environment, where our Postgres driver can’t cache enum types information.
Prisma schema
model User {
id Int @id @default(cuid())
role Role
}
enum Role {
User
Admin
}
Prisma Client query
await prisma.user.findMany({
where: {
role: "Admin"
}
})
Before 5.4.0
-- Internal driver query
SELECT t.typname, t.typtype, t.typelem, r.rngsubtype, t.typbasetype, n.nspname, t.typrelid FROM pg_catalog.pg_type t LEFT OUTER JOIN pg_catalog.pg_range r ON r.rngtypid = t.oid INNER JOIN pg_catalog.pg_namespace n ON t.typnamespace = n.oid WHERE t.oid = $1;
-- Internal driver query
SELECT enumlabel FROM pg_catalog.pg_enum WHERE enumtypid = $1 ORDER BY enumsortorder;
-- Prisma Client query
SELECT id, role FROM "User" WHERE role = $1;
After 5.4.0
-- Prisma Client query
SELECT id, role::text FROM "User" WHERE role = CAST($1::text AS "Role);
Bulk delete improvements
We optimized the deleteMany
operation by:
- Removing all
SELECT
queries used to fetch data that would be used as input for theDELETE
operation. In some cases, this also improves index usage. - Removing the transaction previously used as it’s now a single atomic operation.
Prisma Client query
await prisma.post.deleteMany({
where: {
id: {
gt: 1,
lt: 10,
}
}
})
Before 5.4.0
BEGIN
SELECT id FROM "Post" WHERE id > 1 AND id < 10;
SELECT id FROM "Post" WHERE id > 1 AND id < 10 AND id IN (<...select ids>);
DELETE FROM "Post" WHERE id IN (<...select ids>) AND id > 1 AND ...
5.3.1
Today, we are issuing the 5.3.1
patch release.
Fix in Prisma Client
5.3.0
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
In this sprint, we’ve made bug fixes and overall improvements to Prisma Client. We’ve been working on a few projects that will be announced soon. Stay tuned for the upcoming releases for updates!
Improvements and bug fixes
We made the following changes:
Prisma Client improvements
- Validation for
undefined
values in arrays inJson
fields
We added runtime validation forundefined
values in arrays inJson
fields. Prisma Client will now return an error when an array contains anundefined
value. Therefore, we encourage you to add validation that either removes the value or transforms it tonull
if you stumble on the runtime validation:// Query await prisma.user.findMany({ where: { // JSON field preferences: [undefined, '"theme": "dark"', null, ] } }) // Example error message on running the query Can not use `undefined` value within array. Use `null` or filter out `undefined` values
- Performance improvements for models with many unique fields: This release improves Prisma Client’s memory consumption for models with many
@unique
constraints. This was a regression from version 4.10.1, where in some cases, if a model had many unique constraints, Prisma Client would use up a lot of available memory. - Fixed the segmentation fault error that used to occur on ARM64 Linux binary targets
- Metrics Preview feature improvements:
- We updated the counters and gauge properties
- We fixed the bug that caused the
prisma_pool_connections_open
metric to have a negative value in some cases.
Prisma Migrate improvements
- Fixed an introspection bug for MongoDB views. Previously, if a MongoDB database contained a view,
prisma db pull
would throw an error. We resolved this, and views are now ignored. - Added the
PRISMA_SCHEMA_DISABLE_ADVISORY_LOCK
environment variable that enables you to disable advisory locking.
VS Code extension improvements
- Added support for rendering multi-line comments in tooltips when hovering on a block.
- Improved the auto-completion for composite types in other blocks.
- Added a Code Action that allows you to replace
SetDefault
withNoAction
when using MySQL and the default/foreignKeys
relation mode.
Fixes and improvements
Prisma Migrate
- Percona-XtraDB-Cluster prohibits use of GET_LOCK with pxc_strict_mode = ENFORCING
- MongoDB views should be ignored introspecting the database
- Error in Connector on MongoDB executing listIndex: "system.views"
prisma migrate deploy
:MariaDB doesn't yet support 'GET_LOCK in cluster (WSREP_ON=ON)'
Prisma Client
- Remove all special cases for Data Proxy in our tests
- Segmentation fault on ARM64 Linux
- In the metrics feature a gauge & counter are swapped
- The prisma metrics
prisma_pool_connections_open
has a bug where it goes negative - Prisma crashes with GraphQL queries of nested one-to-many relationship
- P1017 Server has closed the connection on linux_arm64
Error: socket hang up
on Linux/arm64- Panic in Query Engine with SIGABRT signal (Debian Bookworm, engineType = binary)
- Prisma 5 drops
undefined
from Arrays when using Json fields with Postgres - Suspected memory leak in Lambda function after upgrading from 4.10.1
- Error when generating - No unsupported field should reach that path
Language tools (e.g. VS Code)
- Models with multi line comments only show last line in tooltip
- Add VS Code quick fix / code action to replace
SetDefault
withNoAction
whenprovider = "mysql"
andrelationMode = "foreignKeys" | default
- Composite Types aren't offered as being auto-completable in other blocks
Credits
Huge thanks to @alencardc, @Oreilles, @christianledgard, @skyzh, @alula, @michaelpoellath, @RobertCraigie, @stephenwade for helping!
5.2.0
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Improved Prisma Client experience for Prisma Accelerate and Data Proxy
In this release, we’ve made the following improvements to Prisma Client when using Prisma Accelerate or Prisma Data Proxy:
-
Prisma Client will now automatically determine how it should connect to the database depending on the protocol in the connection string. If the connection string starts with
prisma://
, Prisma Client will try to connect to your database using Prisma Accelerate or Prisma Data Proxy. -
Prisma Studio now works with Prisma Data Proxy and Prisma Accelerate.
-
We’ve introduced a new
--no-engine
flag which will prevent a Query Engine file from being included in the generated Prisma Client. This flag will also help ensure the bundle size of your application remains small by excluding the Query Engine files from the generated Prisma Client.prisma generate --no-engine
The
--data-proxy
and--accelerate
flags have not been removed but are now aliases for the new--no-engine
flag.We recommend using the
--no-engine
flag when generating Prisma Client that uses either Accelerate or Data Proxy.
Simplified connection string override in Prisma Client
This release simplifies the API used when programmatically overriding the connection string by introducing the datasourceUrl
property in Prisma Client’s constructor. This means you do not have to use the datasource name defined in your Prisma schema.
const prisma = new PrismaClient({
datasourceUrl: "postgresql://johndoe:randompassword@localhost:5432/mydb",
})
Query performance improvements
Continuing our work from 5.1.0 we made further performance improvements around the queries Prisma executes, targeting one-to-many relation fields and nested updates.
Use LIMIT
in one-to-many relations on a single parent
In cases where there is a single parent with a one-to-many relation included (findFirst
, findUnique
, findMany({ take: 1 })
), we now utilize LIMIT
at the database level to restrict the number of related items returned instead of retrieving all related items into memory and performing a take
in memory.
For situations where you have many related objects but only need a few, you should see a dramatic improvement in speed and memory usage.
Note: we are still working on bringing this improvement to other parts of Prisma Client in upcoming releases. If multiple parent records are returned, the previous behavior is used.
Further improvements for nested writes
Thanks to our introduction of using RETURNING
in some cases in 5.1.0, we could now improve performance in nested writes by removing reload nodes. This will now result in one less query per relation traversed in a nested write. For more info, check out the pull request.
Prisma Client query
await prisma.post.update({
where: { id: 1 },
data: {
comment: {
update: {
data: {
body: "Updated comment body"
}
}
}
},
select: {
id: true,
title: true,
}
})
Before v5.2.0
SELECT "Post"."id", "Post"."title" FROM "Post" WHERE ("Post"."id" = $1 AND 1=1) LIMIT $2 OFFSET $3
SELECT "Post"."id", "Post"."userId" FROM "Post" WHERE "Post"."id" = $1 OFFSET $2
SELECT "User"."id" FROM "User" WHERE (1=1 AND "User"."id" IN ($1)) OFFSET $2
SELECT "User"."id" FROM "User" WHERE ("User"."id" = $1 AND 1=1) LIMIT $2 OFFSET $3
SELECT "User"."id", "User"."commentId" FROM "User" WHERE "User"."id" = $1 OFFSET $2
SELECT "Comment"."id" FROM "Comment" WHERE (1=1 AND "Comment"."id" IN ($1)) OFFSET $2
UPDATE "Comment" SET "body" = $1 WHERE ("Comment"."id" = $2 AND 1=1) RETURNING "Comment"."id"
SELECT "Post"."id", "Post"."title" FROM "Post" WHERE "Post"."id" = $1 LIMIT $2 OFFSET $3
5.2.0 and later
SELECT "Post"."id", "Post"."title", "Post"."userId" FROM "Post" WHERE ("Post"."id" = $1 AND 1=1) LIMIT $2 OFFSET $3
SELECT "User"."id" FROM "User" WHERE (1=1 AND "User"."id" IN ($1)) OFFSET $2
SELECT "User"."id", "User"."commentId" FROM "User" WHERE ("User"."id" = $1 AND 1=1) LIMIT $2 OFFSET $3
SELECT "Comment"."id" FROM "Comment" WHERE (1=1 AND "Comment"."id" IN ($1)) OFFSET $2
UPDATE "Comment" SET "body" = $1 WHERE ("Comment"."id" = $2 AND 1=1) RETURNING "Comment"."id"
SELECT "Post"."id", "Post"."title" FROM "Post" WHERE "Post"."id" = $1 LIMIT $2 OFFSET $3
Fixes and improvements
Prisma Client
- CFW: Avoid including Query Engine when data proxy is enabled
- Local Prisma Studio does not work with Data Proxy
- Postinstall hook always generates non Data Proxy Prisma Client
limit
is gone whenfindUnique
with include relationCannot fetch data from service: include is not a function
Error while using Next.js with Data Proxytake
key doesn't work correctly for nested query that returns one item with its nested children- Prisma Client Edge: environment variables are not working with the "new" Module Worker syntax for Cloudflare Workers
- Add documentation to "PrismaClient is unable to be run in the browser"
- Change how Data Proxy Client deals with unsupported preview features
- Custom Prisma Client output location breaks Prisma Data Proxy in NextJS
- GetPayload type error since 4.16.1 "Two different types with this name exist, but they are unrelated."
- Browser bundle: Unhandled Runtime Error when upgrading to 5.1.0 from 5.0.0
- Prisma Client:
disconnect: true
does not appear to delete the foreign key in the returned data - Prisma Client errors with "TypeError: Cannot create proxy with a non-object as target or handler" when using result client extension with no
needs
andcount
method - Upgrading from Prisma 5.0.0 -> 5.1.0 results in "TS2321: Excessive stack depth comparing types" error using
mockDeep<PrismaClient>()
- Unnecessary reads for to-one nested updates
- Better error message if
@prisma/client/edge
can not find environment variable - 5.1: Alias for old name for
<Model>CountOutputTypeDefaultArgs
does not exist - Incorrect pagination for nested m2m chunked reads
Prisma Migrate
- RustPanic on
prisma generate
when Unsupported field defined in a Composite type - Use PostgreSQL System Information Functions instead of manually joining fields
- Duplicate expression index comment whenever db pull is run
Credits
Huge thanks to @skyzh, @alula, @michaelpoellath, @RobertCraigie, @darthmaim, @Gerschtli, @andyjy, @mejiaej, @iurylippo, @mrazauskas, @coder246, @RDIL for helping!
5.1.1
Today, we are issuing the 5.1.1
patch release.
Fixes in Prisma Client
- Browser bundle: Unhandled Runtime Error when upgrading to 5.1.0 from 5.0.0
- Prisma Client:
disconnect: true
does not appear to delete the foreign key in the returned data - Prisma Client errors with "TypeError: Cannot create proxy with a non-object as target or handler" when using result client extension with no
needs
andcount
method
5.1.0
Today, we are excited to share the 5.1.0
stable release 🎉
🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release.
Highlights
After two big releases where we released Client extensions for production usage (4.16.0
) and made Prisma faster by default (5.0.0
), we have focused on some smaller issues to make the experience with these new features even better.
Community contributions
Our community has been on the roll! We appreciate everyone who helps us by opening a GitHub issue or proposing a fix via Pull Requests. In this release, we're excited to highlight multiple community contributions:
- Fix IPv6 not working for relational databases: prisma/prisma-engines#4051 by @alula
- Middlewares: Add to
PrismaAction
type, missingfindUniqueOrThrow
andfindFirstOrThrow
#17471 by @mejiaej and missinggroupBy
#19985 by @iurylippo - Better error message in currently non-supported runtimes like Browser or Vercel Edge Runtime #20163 by @andyjy
- Remove error messages for valid NixOS setups #20138 by @Gerschtli
Better performance: Fewer SQL queries on PostgreSQL & CockroachDB
In our continued and ongoing work to make Prisma faster, we identified some Prisma Client queries that led to multiple SQL statements being executed — although in specific databases, that was not necessary.
Hence we optimized our internal SQL generation for PostgreSQL and CockroachDB to generate more efficient SQL queries:
Simple create
query
In a simple create
query, RETURNING
makes the second query and the transaction statements obsolete:
Prisma Client query
prisma.user.create({
data: { name: "Original name" }
})
Before v5.1.0
BEGIN
INSERT INTO "User" ("name") VALUES ($1) RETURNING "User"."id"
SELECT "User"."id", "User"."name" FROM "User" WHERE "User"."id" = $1;
COMMIT
5.1.0 and later
-- Sends 1 statement (instead of 2) and omits the transaction
INSERT INTO "User" ("name") VALUES ($1) RETURNING "User"."id", "User"."name"
Simple update
query
For a simple update
query, RETURNING
makes both additional queries and the transaction statements obsolete:
Prisma Client query
prisma.user.update({
where: { id: 1 },
data: { name: "updated" }
})
Before v5.1.0
BEGIN
SELECT id FROM "User" WHERE "User".id = 1;
UPDATE "User" SET name = 'updated' WHERE "User".id = 1;
SELECT id, name FROM "User" WHERE "User".id = 1;
COMMIT
5.1.0 and later
-- Sends 1 statement (instead of 3) and omits the transaction
UPDATE "User" SET name = 'updated' WHERE "User".id = 1 RETURNING "User".id, "User".name;
Simple update
query, return with relation value
One SELECT
query could easily be dropped in a simple update
query that should return a relation value as well:
Prisma Client query
prisma.user.update({
where: { id: 1 },
data: { name: "updated" },
includes: { posts: true }
})
Before v5.1.0
BEGIN
SELECT id FROM "User" WHERE "User".id = 1;
UPDATE "User" SET name = 'updated' WHERE "User".id = 1;
SELECT id, name FROM "User" WHERE "User".id = 1;
SELECT id, title FROM "Post" WHERE "Post"."userId" = 1;
COMMIT
5.1.0 and later
-- Sends 3 statements (instead of 4)
BEGIN
UPDATE "User" SET name = 'updated' WHERE "User".id = 1 RETURNING "User".id;
SELECT id, name FROM "User" WHERE "User".id = 1;
SELECT id, title FROM "Post" WHERE "Post"."userId" = 1;
COMMIT
Empty update
query
An empty update
query can be optimized to skip the transaction and the second identical query by creating specific handling for this edge case in our code:
Prisma Client query
prisma.user.update({
where: { id: 1 },
data: {},
})
Before v5.1.0
BEGIN
SELECT id, name FROM "User" WHERE "User".id = 1;
SELECT id, name FROM "User" WHERE "User".id = 1;
COMMIT
5.1.0 and later
-- Sends 1 statement (instead of 2) and omits the transaction
SELECT id, name FROM "User" WHERE "User".id = 1;
Simple + relation update
query (but do not return relation value)
An update of both the model and its relation, we could drop 2 SELECT
queries that we did before without ever using their return values:
Prisma Client query
prisma.user.update({
where: { id: 1 },
data: {
name: "updated",
posts: {
update: {
where: { id: 1 },
data: {
title: "updated"
}
}
}
}
})
Before v5.1.0
BEGIN
SELECT id, name FROM "User" WHERE "User".id = 1;
UPDATE "User" SET name = 'updated' WHERE "User".id = 1 RETURNING "User".id;
SELECT "id", "postId" FROM "Post" WHERE "Post".id = 1;
UPDATE "Post" SET title = 'updated' WHERE "Post"."userId" = 1 AND "Post".id = 1;
SELECT id, name FROM "User" WHERE "User".id = 1;
COMMIT
5.1.0 and later
-- Sends 3 statements (instead of 5)
BEGIN
UPDATE "User" SET name = 'updated' WHERE "User".id = 1 RETURNING "User".id, "User".name;
SELECT "id", "postId" FROM "Post" WHERE "Post".id = 1;
UPDATE "Post" SET title = 'updated' WHERE "Post"."userId" = 1 AND "Post".id = 1;
COMMIT
In the next releases, we will continue optimizing Prisma Client queries to only run the minimal amount of SQL queries necessary.
If you notice any Prisma Client queries that are affected right now, please check the issues under our performance/queries
label. If you didn’t find one for what you’re seeing, please create a new issue. This will be super useful for us to understand all (edge) cases. Thank you!
Prisma Studio now supports directUrl
Our CLI command prisma studio
that opens Prisma Studio now also can use the directUrl
property of the datasource
block so you can make it talk to a different database than defined in url
. This makes it easier to use Studio alongside the Prisma Data Proxy and Accelerate.
Prisma Client: No more type clashes
We fixed (almost) all cases where using a specific term as a model name in your Prisma Schema would lead to a type clash due to Prisma’s generated typings. As a result of a type clash, it was not possible to use that model in your code (this was e.g. the case if you named a model Model
or ModelUpdate
).
We also deprecated the <ModelName>Args
type as part of that fix. Going forward, <ModelName>DefaultArgs
should be used instead.
Fixes and improvements
Prisma Client
- Reduce the number of generated SQL statements for Updates/Inserts
- [v2.17.0] Missing client TS types Aggregate*Args
- Reduce transactions for writes
- Incorrect Include typings when having models called
X
andXUpdate
- Model named "Check" is incorrectly typed
- Models named Query cause an internal GraphQL Parse Error
- Naming an entity "Query" leads to an error
- Type name clash when
Model
andModelUpdate
is defined in the schema - Duplicate identifier 'CheckSelect'
@prisma/internals
(previously @prisma/sdk) uses deprecated dependenciesuuid@3.4.0
viatemp-write 4.0.0
- naming a model
Datasource
breaks generated return types - Certain
model
names cause clashes in generated types - Type error on query with select field (although query runs successfully)
$extends
TS error: "Inferred type of this node exceeds the maximum length the compiler will serialize" with"declaration": true
intsconfig
- Update operation includes multiple where statements for the same fields
- Type conflict when naming a table {something} and a second table {something}Result
Type '"findUniqueOrThrow"' is not assignable to type 'PrismaAction'
- Naming a model
Promise
breaks types forPrismaPromise
- Prisma can't connect with an IPv6 host (on e.g. Fly.io)
include
not working on models ending with...Update
with unique compound index- Prisma Client: fixing type name clashes from generated client
- [Prisma Client: wrong type when using spread operator to set default values on query args](https://github.com/prisma...
5.0.0
We’re excited to share the 5.0.0
release today 🎉
Prisma 5.0.0
contains a lot of changes that improve Prisma’s performance, especially in serverless environments. If you want to learn more about the performance improvements, we wrote a blog post that sums up all the changes we made: Prisma 5: Faster by Default.
As this is a major release, it includes a few breaking changes that might affect a small group of our users. Before upgrading, we recommend that you check out our upgrade guide to understand the impact on your application.
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Here’s a summary of the changes:
- Preview features moved to General Availability
jsonProtocol
: improves communication between Prisma Client and the query engine, makes Prisma faster by default.fieldReference
: adds support for comparing columns of the same table.extendedWhereUnique
: adds support for non-unique columns insidewhere
clauses for queries that operate on unique records.
- General improvements and breaking changes
- Dependency version changes
- Minimum Node.js version change to 16.13.0
- Minimum TypeScript version change to 4.7
- Minimum PostgreSQL version change to 9.6
- Prisma Client embedded SQLite version upgrade to 3.41.2
- Main Changes
- Removal of
rejectOnNotFound
property - Removal of some array shortcuts
cockroachdb
provider is now required when connecting to a CockroachDB database- Removed
runtime/index.js
from the generated Prisma Client
- Removal of
- Other Changes
- Removal of deprecated flags in the Prisma CLI
- Removal of the
beforeExit
hook from the library engine - Removal of deprecated
prisma2
executable - Removal of deprecated
experimentalFeatures
generator property in the Prisma schema - Renamed
migration-engine
toschema-engine
- Dependency version changes
A JSON-based protocol that improves Prisma’s performance
We’re thrilled to announce that the jsonProtocol
Preview feature is now Generally Available. You can now remove the Preview feature flag from your schema after upgrading. We made the JSON-based wire protocol the default protocol used for communication between Prisma Client and the query engine.
We introduced this feature in version 4.11.0 to improve Prisma’s performance. Previously, Prisma used a GraphQL-like protocol to communicate between Prisma Client and the query engine. Applications with larger schemas had higher CPU and memory consumption compared to smaller schemas which created a performance bottleneck.
The JSON-based wire protocol improves efficiency when Prisma Client is communicating with the query engine.
Removal of array shortcuts
We took the opportunity to remove some array shortcuts to make our typings more consistent and logical. These shortcuts were a way to add a single element as a value to an array-based operator instead of wrapping a single element in an array. We will now require array values for the following:
OR
operator shortcutsin
andnotIn
operator shortcuts- PostgreSQL JSON
path
field shortcut - Scalar list shortcuts
- MongoDB Composite types list shortcuts
Here’s an example query using the OR
operator shortcut for a single element;
await prisma.user.findMany({
where: {
- OR: { email: 'alice@prisma.io' }
+ OR: [{ email: 'alice@prisma.io' }]
}
})
We recommend taking a look at the upgrade guide to learn how you can update your queries to work in Prisma 5.
Support for comparing multiple columns
We’re excited to announce that the fieldReference
Preview feature is now stable and Generally Available. This means you can use this feature without the Preview feature flag in your Prisma schema.
We first introduced this feature in 4.5.0 to add the ability to compare columns on the same table. For example, the following query returns records where the quantity
value is less than the warnQuantity
of a product:
await prisma.product.findMany({
where: {
quantity: { lte: prisma.product.fields.warnQuantity }
},
})
To learn more about this feature, refer to our documentation.
Support for filtering non-unique columns in queries for a unique record
We’re excited to announce the extendedWhereUnique
Preview feature is now Generally Available. This means you can use the feature without the Preview feature flag in the Prisma schema.
We first introduced this feature in version 4.5.0 to add support for non-unique columns inside where
clauses for queries that operate on unique records, such as findUnique
, update
, and delete
, which was previously not possible.
For example, consider the following model:
model Article {
id Int @id @default(autoincrement())
content String
version Int
}
You can filter on non-unique columns such as the version
field as follows:
await prisma.article.findUnique({
where: {
id: 5,
version: 1 // filter on the `version` field was not available before Prisma 4.5.0
},
});
To learn more about this feature, refer to our documentation.
Minimum Node.js version change to 16.13.0
The minimum version of Node.js Prisma supports is 16.13.0
. If you're using an earlier version of Node.js, you will need to upgrade your Node.js version.
Refer to our system requirements for the minimum versions Prisma requires.
Minimum TypeScript version change to 4.7
The minimum version of TypeScript Prisma supports is 4.7. If your project is using an earlier version of TypeScript, you will need to upgrade your TypeScript version.
Refer to our system requirements for the minimum versions Prisma requires.
Minimum PostgreSQL version change to 9.6
The minimum version of PostgreSQL Prisma supports is version 9.6. If you’re either using 9.4 or 9.5, you will need to update your PostgreSQL version to at least 9.6.
Refer to our system requirements for the minimum database versions Prisma requires.
Prisma Client embedded SQLite version upgrade
We upgraded the embedded version of SQLite from 3.35.4 to 3.41.2. We do not anticipate any breaking changes or changes needed in projects using SQLite. However, if you’re using SQLite, especially with raw queries that might go beyond Prisma's functionality, make sure to check the SQLite changelog.
Removal of rejectOnNotFound
property
In version 5.0.0, we removed the rejectOnNotFound
parameter from Prisma Client that was deprecated in version 4.0.0. We removed this feature to provide better type-safety using the findUniqueOrThrow
and findFirstOrThrow
methods as well have a consistent API.
If you are using the rejectOnNotFound
parameter we recommend either:
- Replacing your queries with the
findFirstOrThrow
orfindUniqueOrThrow
methods if enabled at a query-level - Using a Prisma Client extension to overload the
findFirstOrThrow
andfindUniqueOrThrow
model methods with your custom error handling if enabled at the client-level
We recommend taking a look at the upgrade guide for more information on how to adapt your application if you’re using rejectOnNotFound
.
cockroachdb
provider is now required when connecting to a CockroachDB database
Prior to adding explicit support for CockroachDB with the cockroachdb
provider in 3.9.0, it was possible to use the PostgreSQL provider when working with CockroachDB databases.
We’re now making it mandatory to use the CockroachDB connector when working with CockroachDB databases. CockroachDB and PostgreSQL have a few differences such as the available native types which impact the generated migrations.
If you were using the PostgreSQL connector to work with CockroachDB, take a look at the upgrade guide to learn how you can update your connector.
Removal of the generated runtime/index.js
file from Prisma Client
With Prisma 5, we removed the runtime/index.js
file from Prisma Client. If you were using APIs from runtime/index.js
, such as Decimal
, PrismaClientKnownRequestError
, NotFoundError
, PrismaClientUnknownRequestError
, we recommend updating your imports:
- import { Decimal } from '@prisma/client/runtime'
+ import { Prisma } from '@prisma/client'
// Usage update of Prisma C...
4.16.2
Today, we are issuing the 4.16.2
patch release.
Fixes in Prisma Client
- 4.16: (MongoDB) Generated types for list composites are incorrect
- Getting wrong types with prisma client extensions
- Prisma Client fluent API does not work with extends anymore on 4.16.1
- Prisma Client Extensions:
$allModels: { $allOperations }
sets query type tonever
- Result types are incorrectly inferred when
undefined
explicitly passed toselect
/include
4.16.1
Today, we are issuing the 4.16.1
patch release.
Fixes in Prisma Client
- Field references are not available on extended clients
- 4.16.x cannot wrap
$extend
in factory function whencompilerOptions.composite
istrue
- Prisma Schema Type inside a Type not generating a right Payload
- Query in findMany in prisma extends returns a wrong type
- 4.16.0 Count query is not returning the right type when in a transaction
- FindMany returns wrong type after extending prisma client
- Can't specify $queryRawUnsafe return type after extending prisma client