fix(deps): update prisma monorepo to v4 (major)
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
@prisma/client (source) | dependencies | major | ^3.14.0 -> ^4.0.0 |
prisma (source) | devDependencies | major | ^3.14.0 -> ^4.0.0 |
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
prisma/prisma
v4.6.1
Today, we are issuing the 4.6.1
patch release.
Fixes in Prisma Client
- Prisma Client regression bug after upgrading to 4.6.0:
findMany
errors withPANIC: index out of bounds: the len is 0 but the index is 0
upsert()
with nested selection errors withcalled
Option::unwrap()on a
Nonevalue
in 4.6.0
Fix in Prisma Migrate
v4.6.0
Highlights
Interactive Transactions for Prisma Data Proxy (Preview)
In 3.8.0, we disabled the interactiveTransactions
Preview feature when using the Prisma Data Proxy. This was because the API was not yet supported.
In this release, we're removing the limitation. You can now try the Preview version of interactive transactions with the Prisma Data Proxy. Re-generate Prisma Client using prisma generate --data-proxy
after enabling the Preview feature.
Note: The interactiveTransactions
Preview feature flag is still needed. We will remove this in a future version when the feature is stable.
Try it out and let us know your thoughts in our interactive transactions feedback GitHub issue.
Native database level upserts for PostgreSQL, SQLite, and CockroachDB
Prisma’s upsert is one of its most powerful and most convenient APIs. In this release, Prisma will now default to the native database upsert for PostgreSQL, SQLite, and CockroachDB whenever possible.
Prisma will use the native database upsert if:
- There are no nested queries in the
upsert
'screate
andupdate
options - The query modifies only one model
- There is only one unique field in the
upsert
'swhere
option - The unique field in the
where
option and the unique field in thecreate
option have the same value
Prisma Client's upsert
operation was implemented on a Prisma-level and did not use the native database implementations like, e.g., INSERT .. ON CONFLICT .. UPDATE SET
. This allowed Prisma to also upsert nested queries.
The Prisma-implementation came at a cost. In some scenarios, it was more likely for a transaction to roll back because of a conflict when multiple upsert
operations were being executed in parallel, and the multiple queries often took longer than the native database query would have taken.
Try it out and let us know what you think. If you run into any issues, don't hesitate to create a GitHub issue.
Relation Mode improvements (Preview)
In 4.5.0, we renamed the "Referential Integrity" Preview feature to "Relation Mode". We also changed the datasource
property name of the feature to relationMode
.
In this release, we fixed all remaining known bugs of relationMode = "prisma"
and cleaned up our documentation. You can now read about Relation mode on its own documentation page which is up to date with the implementation.
If you encounter any problems please comment on our feedback issue. We plan to make this Generally Available soon.
extendedWhereUnique
improvements (Preview)
In 4.5.0, we introduced the extendedWhereUnique
Preview feature to allow filtering for non-unique properties in unique where queries. In this release, we're adding new rules to decide when concurrent findUnique
queries get batched into a findMany
query.
Unfortunately, we forgot to adapt our findUnique
query batch optimization, which turns multiple concurrent findUnique
queries into a single findMany
query when possible — GitHub issue.
Therefore, findUnique
queries will get batched into a findMany
query if:
- All criteria of the filter must be on scalar fields (unique or non-unique) of the same model you're querying
- All criteria must use the equal's filter, whether that's via the shorthand or explicit syntax (
where: { field: <val>, field1: { equals: <val> } }
)
Conversely, suppose the filter object contains any boolean operators, relation filters, or scalar filters that are not using equals
. Prisma will fall back to executing the findUnique
queries independently.
Let us know your thoughts and share your feedback on the Preview feature in this GitHub issue.
Fixes and improvements
Prisma Client
- upsert across HTTP requests has a race condition
- Client tests for Vitess, with
relationMode=prisma
- Concurrent relation upserts conflict
upsert()
should do ON CONFLICT DO UPDATE/NOTHING in postgresql- Cannot insert Floats (≥9.223372037e18 and <1e21) or (>-1e21 and ≤-9.223372037e18)
- Always serialize float fields in exponent notation
- Postgres integer column silently overflows to bad value
- Add duration to mongo logging
- upsert(): Unique constraint on DateTime sqlite
- "Unique constraint failed on the fields" when using upsert
- using connect in interactive transaction fails
- MongoDB does not log queries with
binary
Engine - [MongoDb] Query logger produces incorrect output
- Float values around 2^63 get interpreted as invalid intergers and throw a graphql error
- referentialIntegrity/relationMode preview feature (
referentialIntegrity = "prisma"
): MakeNoAction
a synonym/alias ofRestrict
for the emulation, for all databases except PostgreSQL & SQLite. - Client: In 1:1,1:n, m:n relations using
OnDelete: SetNull
withreferentialIntegrity = "prisma"
user.delete()
should fail, but succeeds. - calling findUnique concurrently on a model with a compound unique constraint causes it to return null
- Support interactive transactions in the Data Proxy
Prisma
- Re-Introspection:
referentialIntegrity = prisma
not respected when using@@​map()
- Validation fails to detect invalid
SetNull
referential action referencing non-optional fields - Schema: add validation for datasource property referentialIntegrity & relationMode, so only one can be set.
- Create TypeScript tests for #15655
referentialIntegrity
policy is lost during re-introspection- Relation fields are removed after npx prisma db pull
- Re-introspection should not remove relations when relationMode="prisma"
Language tools (e.g. VS Code)
Design Partner Program
Are you building data-intensive applications in serverless environments using Prisma? If so, you should join our Design Partner Program to help us build the tools that best fit your workflows!
The Design Partner Program aims to help development teams solve operational, data-related challenges in serverless environments. Specifically, we’re looking to build tools that help with the following problems:
- Solutions to listen and react to database changes in real time are either brittle or too complex to build and operate.
- Coordinating workflows executed via a set of isolated functions or services spreads that coordination logic across these services instead of keeping it centralized and maintainable. This adds unnecessary overhead and clutter to your business logic.
- Optimizing the data access layer for scaling performance often involves projecting data into denormalized views, or caching. These methods come with complex logic to figure out strategies for cache invalidation or preventing to use stale data.
- Building web applications on modern Serverless platforms such as Vercel or Netlify often breaks down as soon as you need to execute on any of the topics listed above. This pushes to re-platform on a traditional infrastructure, delaying projects, and losing productivity benefits offered by Vercel or Netlify.
Submit an application through our application form to join the Prisma Design Partner Program to take advantage of new features that you won't have to build or maintain yourselves.
Prisma Data Platform
We're working on the Prisma Data Platform — a collaborative environment for connecting apps to databases. It includes the following:
- Data Browser for navigating, editing, and querying data
- Data Proxy for your database's persistent, reliable, and scalable connection pooling.
- Query Console for experimenting with queries
Try it out. Let us know what you think!
📺 Join us for another "What's new in Prisma" live stream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.
The stream takes place on YouTube on Thursday, November 10 at 5 pm Berlin | 8 am San Francisco.
Credits
Huge thanks to @cmd-johnson for helping!
v4.5.0
Major improvements
Filter for non-unique properties in unique where queries (Preview)
In this release, we are adding support for non-unique properties inside the where
statement for queries that operate on a unique record (e.g.: findUnique
, update
, delete
, etc.). This was not possible in the past, as we only allowed unique fields as filters inside the where
statement for the queries in question.
There are use cases where a query that operates on a unique record requires further filtering by non-unique properties. For example, for the following model:
model Article {
id Int @​id @​default(autoincrement())
content String
version Int
}
Let’s say that you would like to update the Article
with an id
of “5”, but only if the version
equals "1":
await prisma.article.update({
where: { id: 5, version: 1 }, // `version` field was not available before Prisma 4.5.0
data: {
content: "Incredible new story",
version: { increment: 1 },
},
});
With 4.5.0
, we are adding support to specify any number of non-unique fields in your where
statement, as long as you have at least one unique field.
To use it, enable the Preview feature flag:
generator js {
provider = "prisma-client-js"
previewFeatures = ["extendedWhereUnique"]
}
To learn more about this feature and about use cases where it can be useful, please check out our documentation. For feedback, please leave a comment on the GitHub issue.
PostgreSQL extension management (Preview)
We are excited to add support for declaring PostgreSQL extensions in the Prisma schema. The feature comes with support for introspection and migrations. This will allow you to adopt, evolve and manage which PostgreSQL database extensions are installed directly from within your Prisma schema.
💡 This feature adds support to manage PostgreSQL extensions in Prisma schema. It does not provide additional query capabilities and datatypes in Prisma Client.
To try this feature, enable the Preview feature flag:
generator client {
provider = "prisma-client-js"
previewFeatures = ["postgresqlExtensions"]
}
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
Now you will be able to use the new extensions
property in the datasource
block of your Prisma schema.
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
extensions = [hstore(schema: "myHstoreSchema"), pg_tgrm, postgis(version: "2.1")]
}
⚠ ️ To avoid noise from introspection, we currently only introspect the following allow-list:citext
,pgcrypto
,uuid-ossp
, andpostgis
. But you can add and configure any extension to your Prisma schema manually.
Please visit our documentation to learn more about this feature or leave a comment with feedback on the GitHub issue.
datasource
block renamed to relationMode
(Preview)
Change to Referential Integrity — property in To prepare Prisma Client’s emulation of relations for general availability, we are releasing several improvements to the referentialIntegrity
Preview feature.
We decided to rename the feature to Relation Mode. We think this closer reflects what this feature does and distinguishes it from integrity management on the database level. The related property in the datasource
block of the Prisma schema has also been changed from referentialIntegrity
to relationMode
.
⚠ ️ The Preview feature flag inside thegenerator
block of the Prisma schema is still calledreferentialIntegrity
.
To use it, keep using the old referentialIntegrity
Preview feature flag:
generator js {
provider = "prisma-client-js"
previewFeatures = ["referentialIntegrity"]
}
But use the new property name in the datasource
:
datasource db {
provider = "mysql"
url = env("DATABASE_URL")
relationMode = "prisma"
}
We also removed the referential action NoAction
for PostgreSQL and SQLite when using relationMode = "prisma"
as we are not planning to support the details of the database behavior.
To learn more about relationMode
, please check out the documentation or leave a comment on the GitHub issue.
Deno for Prisma Client for Data Proxy (Preview)
Deno is an alternative JavaScript runtime that can replace Node.js to run JS and TS apps. It aligns itself closely with web technologies, claims to be secure by default, and supports TypeScript out of the box.
Today we are releasing initial support for Prisma with Deno via an integration for our Prisma Client for Data Proxy. This feature was developed together with the amazing team at Deno 🦕.
To use Prisma Client in a Deno project, add the deno
Preview feature flag to your Prisma schema and define a folder as output
(this is required for Deno):
generator client {
provider = "prisma-client-js"
previewFeatures = ["deno"]
output = "../generated/client"
}
Now you can generate Prisma Client with the Data Proxy using the command npx prisma generate --data-proxy
. Then use Prisma Client in your Deno script with the following import:
import { PrismaClient } from './generated/client/deno/edge.ts'
const prisma = new PrismaClient()
async function main() {
const users = await prisma.user.findMany()
console.log({ users })
}
main()
You can also deploy an app built and configured like this on Deno Deploy, Deno’s deployment platform. Read this guide in our documentation for a full example and individual steps.
For feedback, please comment on this GitHub issue.
Fixed “Invalid string length” error in Prisma Studio and Prisma Data Platform Data Browser
Many people were having issues with an "Invalid string length" error both in Prisma Studio and Prisma Data Platform Data Browser. This issue can be resolved through this workaround. With this release, the root cause of this issue has been fixed and it should not occur again.
Updated proposal for Client Extensions: request for comments
In 4.3.0
, we shared a proposal for Prisma Client Extensions on Github. We received a lot of great feedback, which we have incorporated into a new proposal.
If you’re interested, please head over to the new proposal in GitHub and tell us what you think. Thank you!
Fixes and improvements
Prisma
- Optimistic Concurrency Control
- MySQL does not support
onDelete: setDefault
- Reformat unreachable code: Encountered impossible declaration during formatting
- Switching between
referentialIntegrity
modes makes migration history obsolete - Rename the feature to “Prisma relation mode” → relationMode
- [multiSchema] check PSL validations for enum and composite type database name clashes
- Support PostgreSQL Extensions in the Prisma Schema Language
- Support PostgreSQL Extensions in the PostgreSQL Introspection
- Support PostgreSQL Extensions in the Migration Engine
- Add TS test for datasource property
referentialIntegrity
andrelationMode
- relationMode: Change test naming
Prisma Client
- Be able to update or retrieve a single record including non-unique fields in the "where" conditions.
- Remove WhereUnique constraint from single object lookups
- Expand tests around referential actions and referential integrity
- Feature: Allow non-unique fields to be used with update
- QueryRaw: Error serializing parameter
- PrismaClientUnknownRequestError on create statement default optional value
- Problems with SQL Server deadlocks
Prisma Migrate
Language tools (e.g. VS Code)
- Custom icon for .prisma files
- Add autocompletion for property of
relationMode
(previouslyreferentialIntegrity
) in the datasource block
Credits
Huge thanks to @kt3k, @abenhamdine, @jsoref for helping!
v4.4.0
Major improvements
General improvements
In the last sprint, we focused our efforts on squashing as many bugs as we could. You can find the full list of improvements and bug fixes in the Fixes and improvements section below.
Some of the improvements we made include but are not limited to:
- Improved optimistic concurrency control (GitHub issue)
- Improved decimal precision
- Improved handling of big amounts of prepared statement placeholders:
Databases impose limits when they hit a specific number, and when a query (either generated by Prisma Client or provided by the user directly as a raw query) hits it some users ran into a misleading
Can't reach database server
error message (GitHub issue). The error message will now be more useful (P2035
error code), and Prisma Client should not cause these errors anymore.
If you notice any regression, please make sure to create a GitHub issue. We touched a lot of code in this sprint, and even though we are confident in our tests, something might have slipped through the cracks. We'd like to fix the regressions as soon as possible.
isolationLevel
for sequential transaction operations
In version 4.2.0
, we added support for setting transaction isolation levels for interactive transactions (Preview). You can now define isolation levels for sequential transaction operations: prisma.$transaction([])
.
Isolation levels describe different types of trade-offs between isolation and performance that databases can make when processing transactions. Isolation levels determine what types of data leaking can occur between transactions or what data anomalies can occur.
To set the transaction isolation level, use the isolationLevel
option in the second parameter of the API. For example:
await prisma.$transaction(
[
// sequential operations
prisma.user.create({ data: {/** args */ } }),
prisma.post.create({ data: {/** args */ } })
],
{
isolationLevel: Prisma.TransactionIsolationLevel.Serializable
}
)
Prisma Client supports the following isolation levels if they're available in your database provider:
ReadCommitted
ReadUncommitted
RepeatableRead
Serializable
Snapshot
Learn more about it in our documentation.
P2034
error code for transaction conflicts or deadlocks
New When using certain isolation levels, it is expected that a transaction can fail due to a write conflict or a deadlock, throwing an error. One way to solve these cases is by retrying the transaction.
To make this easier, we're introducing a new PrismaClientKnownRequestError
with the error code P2034
: "Transaction failed due to a write conflict or a deadlock. Please retry your transaction". You can programmatically catch the error and retry the transaction. Here's an example showing how you can retry a transaction:
import { Prisma, PrismaClient } from '@​prisma/client'
const prisma = new PrismaClient()
async function main() {
const MAX_RETRIES = 5
let retries = 0;
let result;
while (retries < MAX_RETRIES) {
try {
result = await prisma.$transaction(
[
prisma.user.deleteMany({ where: { /** args */ } }),
prisma.post.createMany({ data: { /** args */ } })
],
{
isolationLevel: Prisma.TransactionIsolationLevel.Serializable
}
)
} catch (error) {
if (error.code === 'P2034') {
retries++
continue
}
throw error
}
}
}
Fixes and improvements
Prisma Client
- Wrong types for fluent API when used along with
rejectOnNotFound
- Precision issue when persisting Decimal.js objects
- Decimals lose precision (postgres)
- Weird behavior with "in:" clause on a findMany() with orderBy + take
- decimal lose precision digits to postgres
updateMany()
causes lost-updates- Error: P1001: Can't reach database server when including large table
- Client shows contains filter on uuid data type despite not being a valid operation
- A model with relation to another model via non-null foreign key has nullable type
- Validation error when inserting data of type
List<String | DateTime>
into field of typeList<String>
- Can't reach database server when doing a large findMany query
- Maximum call stack size exceeded when creating huge amount of related rows
- Unique constraint failed during
$transaction([deleteMany, createMany])
- update will break atomicity
- Nested self referential orderby not working
- MySQL: Optimistic Concurrency Control doesn't work with UpdateMany
- Wrong type when retrieving multiple related records using fluent API
- Fluent API produces runtime error
- Column 'orderby_.....' in on clause is ambiguous
- [PostgreSQL] Cannot create or update row with large Decimal value within
numeric
range - Failed transactions trigger multipleResolves
The provided database string is invalid. Unable to parse URL. in database URL.
on invalid (?) connection string- relation query fails when thousands of records
- Unable to query records with certain values
- orderBy using self-referential relation in a nested relation fails with "table name "TableName" specified more than once"
- @updatedAt does not work with @default
- Prisma silently misses nested elements on MariaDB when it triggers a huge IN clause
createdAt @​default(now())
andupdatedAt @​updatedAt
get different times on row creation- Interactive Transactions: fatal when throwing string instead of Error() since 3.10.0
- Prisma MongoDB can not search for field with value
$foo
- groupBy crashes when using enums
- MySQL DECIMAL(X, 5) returns incorrect precision.
- "Join" performance: (Not so) huge data set throws an error
Error: The provided database string is invalid. Unable to parse URL. in database URL.
- [mongoDB]
findRaw
does not work within aninteractiveTransaction
- Filters max size is exceeded
- Prisma fails on Postgres query with findMany
- Update Restrict failed on prisma referentialIntegrity
- invalid character in $let in $lookup pipeline when using cursor and order by query
- Find many returns empty array or null
- Once instance has previously been poisoned
- Sanitize error snapshots in new test setup
- The findMany query fails silently when the array length passed through IN parameter exceeds 999
- mongodb cannot use $runCommand Raw in transaction
parent result: Some(ManyRecords { records: [Record { values: [Int(3), Int(1), DateTime(2022-08-08T12:27:55.310+00:00)], parent_id: None }], field_names: ["id", "userId", "createdAt"] }), relation: Relation { name: "post", model_a_name: "Comment", model_b_name: "Post", model_a: OnceCell((Weak)), model_b: OnceCell((Weak)), field_a: OnceCell((Weak)), field_b: OnceCell((Weak)), manifestation: Inline(InlineRelation { in_table_of_model_name: "Comment" }), internal_data_model: "#InternalDataModelWeakRef#" }
- Given exponent overflowing the maximum accepted scale (255).: TryFromIntError(())
- Once instance has previously been poisoned
- sqlite:cuid():called
Result::unwrap()
on anErr
value: FingerprintError("Could not retrieve hostname") - Calling
findUnique
concurrently with aDateTime
column causes it to returnnull
- Maximum Call Stack Size Exceeded When Inserting large Array Object
- Prisma Client is incompatible with TypeScript 4.8
- This is a non-recoverable error: When creating Item with nested query
- Given exponent overflowing the maximum accepted scale (255).: TryFromIntError(())
- Prisma 4.3.0 takes 100x more time to generate types
- Tracing:
prisma:engine
spans always get sampled when using probability based samplers - Datasource providers in
prisma init
is listing wrong values - Disconnect with large queries
N/A
error and message with large raw queries- only one @updatedAt is filled by the QE although multiple are accepted in the schema
- Insert fails if a table has a space in the name of the primary key
- Bug with throwing formatted errors
- called
Option::unwrap()
on aNone
value - Upsert error on MySQL:
Query ... is required to return data, but found no record(s)
- Add tests for mongodb's
findRaw
,aggregateRaw
andrunCommandRaw
in sequential transactions
Prisma
- sqlite: show better error when a permission denied error occurs
- Prisma v4 breaks support for empty
dbgenerated()
- invalid migration created with no schema change - Binary engine:
$disconnect
never returns if engine failed to start
Prisma Migrate
Prisma Studio
Credits
Huge thanks to @abenhamdine, @miguelgargallo, @Clansty, @panoplied, @MEnnabah, @drzamich, @AndrewSouthpaw, @kt3k for helping!
💼 We're hiring!
If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.
We're looking for a Developer Advocate (Frontend / Fullstack) and Back-end Engineer: Prisma Data Platform.
Feel free to read the job descriptions and apply using the links provided.
Prisma Data Platform
We're working on the Prisma Data Platform — a collaborative environment for connecting apps to databases. It includes the:
- Data Browser for navigating, editing, and querying data
- Data Proxy for your database's persistent, reliable, and scalable connection pooling.
- Query Console for experimenting with queries
Try it out and let us know what you think!
📺 Join us for another "What's new in Prisma" livestream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.
The stream takes place on YouTube on Thursday, September 29 at 5 pm Berlin | 8 am San Francisco.
v4.3.1
Today, we are issuing the 4.3.1
patch release.
Fixes in Prisma Client
Fixes in Prisma CLI
v4.3.0
Major improvements
Field reference support on query filters (Preview)
We're excited to announce Preview support for field references. You can enable it with the fieldReference
Preview feature flag.
Field references will allow you to compare columns against other columns. For example, given the following schema:
generator client {
provider = "prisma-client-js"
previewFeatures = ["fieldReference"]
}
model Invoice {
id Int @​id @​default(autoincrement)
paid Int
due Int
}
You can now compare one column with another after running prisma generate
, for example:
// Filter all invoices that haven't been paid yet
await prisma.invoice.findMany({
where: {
paid: {
lt: prisma.invoice.fields.due // paid < due
}
}
})
Learn more about field references in our documentation. Try it out and let us know what you think in this GitHub issue.
Count by filtered relation (Preview)
In this release, we're adding support for the ability to count by a filtered relation. You can enable this feature by adding the filteredRelationCount
Preview feature flag.
Given the following Prisma schema:
generator client {
provider = "prisma-client-js"
previewFeatures = ["filteredRelationCount"]
}
model User {
id Int @​id @​default(autoincrement())
email String @​unique
name String?
posts Post[]
}
model Post {
id Int @​id @​default(autoincrement())
title String
content String?
published Boolean @​default(false)
author User? @​relation(fields: [authorId], references: [id])
authorId Int?
}
You can now express the following query with the Preview feature after re-generating Prisma Client:
// Count all published user posts
await prisma.user.findMany({
select: {
_count: {
posts: { where: { published: true } },
},
},
})
Learn more in our documentation and let us know what you think in this issue
Multi-schema support (Preview)
In this release, we're adding very early Preview support of multi-schema support for PostgreSQL and SQL Server behind the multiSchema
Preview feature flag. With it, you can write a Prisma schema that accesses models across multiple schemas.
Read further in this GitHub issue. Try it out and let us know what you think in this GitHub issue.
Prisma CLI exit code fixes
We've made several improvements to the Prisma CLI:
-
prisma migrate dev
previously returned a successful exit code (0) whenprisma db seed
was triggered but failed due to an error. We've fixed this andprisma migrate dev
will now exit with an unsuccessful exit code (1) when seeding fails. -
prisma migrate status
previously returned a successful exit code (0) in unexpected cases. The command will now exit with an unsuccessful exit code (1) if:- An error occurs
- There's a failed or unapplied migration
- The migration history diverges from the local migration history (
/prisma/migrations
folder) - Prisma Migrate does not manage the database' migration history
-
The previous behavior when canceling a prompt by pressing Ctrl + C was returning a successful exit code (0). It now returns a non-successful,
SIGINT
, exit code (130). -
In the rare event of a Rust panic from the Prisma engine, the CLI now asks you to submit an error report and exit the process with a non-successful exit code (1). Prisma previously ended the process with a successful exit code (0).
tracing
Preview feature
Improved precision for the Before this release, you may have occasionally seen some traces that took 0μs working with the tracing
Preview feature. In this release, we've increased the precision to ensure you get accurate traces.
Let us know if you run into any issues in this GitHub issue.
prisma format
now uses a Wasm module
Initially, the prisma format
command relied on logic from the Prisma engines in form of a native binary. In an ongoing effort to make prisma
more portable and easier to maintain, we decided to shift to a Wasm module.
prisma format
now uses the same Wasm module as the one the Prisma language server uses, i.e. @prisma/prisma-fmt-wasm
, which is now visible in prisma version
command's output.
Let us know what you think. In case you run into any issues, let us know by creating a GitHub issue.
MongoDB query fixes
⚠ ️ This may affect your query results if you relied on this buggy behavior in your application.
While implementing field reference support, we noticed a few correctness bugs in our MongoDB connector that we fixed along the way:
-
mode: insensitive
alphanumeric comparisons (e.g. “a” > “Z”) didn’t work (GitHub issue) -
mode: insensitive
didn’t exclude undefined (GitHub issue) -
isEmpty: false
on lists types (e.g. String[]) returned true when a list is empty (GitHub issue) -
hasEvery
on list types wasn’t aligned with the SQL implementations (GitHub issue)
JSON filter query fixes
⚠ ️ This may affect your query results if you relied on this buggy behavior in your application. We also noticed a few correctness bugs in when filtering JSON values when used in combination with theNOT
condition. For example:
await prisma.log.findMany({
where: {
NOT: {
meta: {
string_contains: "GET"
}
}
}
})
Prisma schema
model Log {
id Int @​id @​default(autoincrement())
level Level
message String
meta Json
}
enum Level {
Info
Warn
Error
}
If you used NOT
with any of the following queries on a Json
field, double-check your queries to ensure they're returning the correct data:
string_contains
string_starts_with
string_ends_with
array_contains
array_starts_with
array_ends_with
-
gt
/gte
/lt
/lte
Prisma extension for VS Code improvements
The Prisma language server now provides Symbols in VS Code. This means you can now:
-
See the different blocks (
datasource
,generator
,model
,enum
, andtype
) of your Prisma schema in the Outline view. This makes it easier to navigate to a block in 1 click A few things to note about the improvement are that:- CMD + hover on a field whose type is an enum will show the block in a popup
- CMD + left click on a field whose type is a model or enum will take you to its definition.
-
Enable Editor sticky scroll from version
1.70
of VS Code. This means you can have sticky blocks in your Prisma schema, improving your experience when working with big schema files
Make sure to update your VS Code application to 1.70, and the Prisma extension to 4.3.0
.
We'd also like to give a big Thank you to @yume-chan for your contribution!
Prisma Studio improvements
We've made several improvements to the filter panel which includes:
-
Refined filter panel
- Reducing the contrast of the panel in dark mode
- Ability to toggle filters in the panel
-
Refined error handling for MongoDB m-n relations Prisma Studio prevents fatal errors when interacting with m-n relations by explicitly disabling creating, deleting, or editing records for m-n relations
-
Multi-row copying You can select multiple rows and copy them to your clipboard as JSON objects using CMD + C on MacOS or Ctrl + C on Windows/ Linux
Prisma Client Extensions: request for comments
For the last couple of months, we've been working on a specification for an upcoming feature — Prisma Client extensions. We're now ready to share our proposed design and we would appreciate your feedback.
Prisma Client Extensions aims to provide a type-safe way to extend your existing Prisma Client instance. With Prisma Client Extensions you can:
- Define computed fields
- Define methods for your models
- Extend your queries
- Exclude fields from a model ... and much more!
Here’s a glimpse at how that will look:
const prisma = new PrismaClient().$extend({
$result: {
User: {
fullName: (user) => {
return `${user.firstName} ${user.lastName}`
},
},
},
$model: {
User: {
signup: async ({ firstName, lastName, email, password }) => {
// validate and create the user here
return prisma.user.create({
data: { firstName, lastName, email, password }
})
},
},
},
})
const user = await prisma.user.signup({
firstName: "Alice",
lastName: "Lemon",
email: "alice@prisma.io",
password: "pri$mar0ckz"
})
console.log(user.fullName) // Alice Lemon
For further details, refer to this GitHub issue. Have a read and let us know what you think!
Fixes and improvements
Prisma Client
- Allow WHERE conditions to compare columns in same table
- Dates serialized without quotation marks in query event parameters property
- Ability to filter count in "Count Relation Feature"
- Some traces show 0μs
- [MongoDB] Alphanumeric insensitive filters don't work
- [MongoDB] Insensitive filters don't exclude undefineds
- Schema size affects runtime speed
- Prisma Client always receive engine spans even when not tracing
- Environment variables not available when using Wrangler 2
Prisma
- Undo "skip flaky referentialActions sql server test"
- Add
@prisma/prisma-fmt-wasm
to CLI and output dependency version in-v
, use instead of Formatter Engine binary - Add jest snapshots for improved
db push
output in MongoDB - OpenSSL error message appearing while using query-engine has false positives
- Calling
dmmf
raises "Schema parsing - Error while interacting with query-engine-node-api library" misleading error message when there is a schema validation error. - Unique composite indexes do not clash with a matching name on schema validation (composite types)
- CLI:
migrate status
should return a non-successful exit code (1) when a failed migration is found or an error occurs - CLI:
migrate dev
should return a non-successful exit code (1) when there is an error during seeding
Prisma Migrate
Language tools (e.g. VS Code)
Credits
Huge thanks to @abenhamdine, @drzamich, @AndrewSouthpaw, @kt3k, @lodi-g, @Gnucki, @apriil15, @givensuman for helping!
Prisma Data Platform
We're working on the Prisma Data Platform — a collaborative environment for connecting apps to databases. It includes the:
- Data Browser for navigating, editing, and querying data
- Data Proxy for your database's persistent, reliable, and scalable connection pooling.
- Query Console for experimenting with queries
Try it out and let us know what you think!
💼 We're hiring!
If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.
We're looking for a Developer Advocate (Frontend / Fullstack) and Back-end Engineer: Prisma Data Platform.
Feel free to read the job descriptions and apply using the links provided.
📺 Join us for another "What's new in Prisma" livestream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.
The stream takes place on YouTube on Thursday, September 1 at 5 pm Berlin | 8 am San Francisco.
v4.2.1
Today, we are issuing the 4.2.1
patch release.
Fix in Prisma Client
v4.2.0
Major improvements
Prisma Client tracing support (Preview)
We're excited to announce Preview support for tracing in Prisma Client!
Tracing allows you to track requests as they flow through your application. This is especially useful for debugging distributed systems where each request can span multiple services.
With tracing, you can now see how long Prisma takes and what queries are issued in each operation. You can visualize these traces as waterfall diagrams using tools such as Jaeger, Honeycomb, or DataDog.
Read more about tracing in our announcement post and learn more in our documentation on how to start working with tracing.
Try it out and let us know what you think.
Isolation levels for interactive transactions
We are improving the interactiveTransactions
Preview feature with the support for defining the isolation level of an interactive transaction.
Isolation levels describe different types of trade-offs between isolation and performance that databases can make when processing transactions. Isolation levels determine what types of data leaking can occur between transactions or what data anomalies can occur.
To set the transaction isolation level, use the isolationLevel
option in the second parameter of the API. For example:
await prisma.$transaction(
async (prisma) => {
// Your transaction...
},
{
isolationLevel: Prisma.TransactionIsolationLevel.Serializable,
maxWait: 5000,
timeout: 10000,
}
)
Prisma Client supports the following isolation levels if they're available in your database provider:
ReadCommitted
ReadUncommitted
RepeatableRead
Serializable
Snapshot
Learn more about in our documentation. Try it out, and let us know what you think in this GitHub issue.
Renaming of Prisma Client Metrics
In this release, we've renamed the metrics — counters, gauges, and histograms — returned from prisma.$metrics()
to make it a little easier to understand at a glance.
Previous | Updated |
---|---|
query_total_operations |
prisma_client_queries_total |
query_total_queries |
prisma_datasource_queries_total |
query_active_transactions |
prisma_client_queries_active |
query_total_elapsed_time_ms |
prisma_client_queries_duration_histogram_ms |
pool_wait_duration_ms |
prisma_client_queries_wait_histogram_ms |
pool_active_connections |
prisma_pool_connections_open |
pool_idle_connections |
prisma_pool_connections_idle |
pool_wait_count |
prisma_client_queries_wait |
Give Prisma Client metrics
a shot and let us know what you think in this GitHub issue
To learn more, check out our documentation.
Syntax highlighting for raw queries in Prisma Client
This release adds syntax highlighting support for raw SQL queries when using $queryRaw``
and $executeRaw``
. This is made possible using Prisma's VS Code extension.
Note: Syntax highlighting currently doesn't work with when using parentheses, ()
, $queryRaw()
, $executeRaw()
, $queryRawUnsafe()
, and $executeRawUnsafe()
.
If you are interested in having this supported, let us know in this GitHub issue.
Experimental Cloudflare Module Worker Support
We fixed a bug in this release that prevented the Prisma Edge Client from working with Cloudflare Module Workers.
We now provide experimental support with a workaround for environment variables.
Try it out and let us know how what you think! In case you run into any errors, feel free to create a bug report.
Upgrade to Prisma 4
In case you missed it, we held a livestream a few weeks ago and walked through issues you may run into while upgrading to Prisma 4 and how to fix them!
Request for feedback
Our Product teams are currently running two surveys to help close the feature gaps and improve Prisma.
If you have a use-case for geographical data (GIS) or full-text search/ indexes (FTS), we would appreciate your feedback on your needs:
- Prisma GIS User Research Survey
- Prisma Full-Text Search User Research Survey
Many thanks!
Fixes and improvements
Prisma Client
- Allow
dataproxy
to have datasource overrides - Warning during build: equals-negative-zero
- getGraphQLType throws error if object has no prototype
- Prisma Client: Log Data Proxy usage explicitly
- Cannot read property 'name' of undefined attempting to create row
- Edge client crashes when enabling debug logs in constructor
- TypeError: Cannot read properties of undefined (reading '_hasPreviewFlag')
- Large package.json log output in prisma:client:dataproxyEngine
Prisma
- Error: [libs/datamodel/connectors/dml/src/model.rs:338:29] Crash probably due to cyrillic table names
- Prisma doesn't validate composite attributes correctly
- Not letting me add Int as a type?
- Introspection crash,
libs\datamodel\connectors\dml\src\model.rs:494:29
(missing PK?) - SQL Server introspection panic
- Hi Prisma Team! Prisma Migrate just crashed.
- Primary key in model using a missing column
- Migrate just crashed sqlserver
- Prisma is trying to find column that doesn't exists
prisma db pull
onSQL Server
- Issue that occurred during
prisma db pull
Language tools (e.g. VS Code)
Prisma Studio
Credits
Huge thanks to @shian15810, @zifeo, @lodi-g, @Gnucki, @apriil15, @givensuman, @peter-gy for helping!
Prisma Data Platform
We're working on the Prisma Data Platform — a collaborative environment for connecting apps to databases. It includes the:
- Data Browser for navigating, editing, and querying data
- Data Proxy for persistent, reliable, and scalable connection pooling for your database.
- Query Console for experimenting with queries
Try it out and let us know what you think!
💼 We're hiring!
If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.
We're looking for a Developer Advocate (Frontend / Fullstack) and Back-end Engineer: Prisma Data Platform.
Feel free to read the job descriptions and apply using the links provided.
📺 Join us for another "What's new in Prisma" livestream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.
The stream takes place on YouTube on Thursday, August 11 at 5 pm Berlin | 8 am San Francisco.
v4.1.1
Today, we are issuing the 4.1.1
patch release.
Fix in Prisma Studio
v4.1.0
Upgrading to Prisma 4
In case you missed it, we held a livestream last week and walked through issues you may run into while upgrading to Prisma 4 and how to fix them!
Major improvements
Ordering by nulls first and last support (Preview)
In this release, we're adding support for choosing how to sort null values in a query.
To get started, enable the orderByNulls
Preview feature flag in your Prisma schema:
generator client {
provider = "prisma-client-js"
previewFeatures = ["orderByNulls"]
}
Next, run prisma generate
to re-generate Prisma Client. You will now have new fields you can now use to order null values:
await prisma.post.findMany({
orderBy: {
updatedAt: {
sort: 'asc',
nulls: 'last'
},
},
})
Learn more in our documentation and don't hesitate to share your feedback in this issue.
Fixed memory leaks and CPU usage in Prisma Client
In this release, we've fixed the following issues experienced when setting up and tearing down Prisma Client while running tests:
- Prisma Client now correctly releases memory on Prisma Client instances that are no longer being used. Learn more in this GitHub issue
- Reduced CPU usage spikes when disconnecting Prisma Client instances while using Prisma Client. You can learn more in this GitHub issue
These fixes will allow you to run your tests a little faster!
Prisma Studio improvements
We're refining the experience when working with Prisma studio with the following changes:
- An always visible filter panel and functionality to clear all filters at once
- Improved relationship model view with more visible buttons
Let us know what you think, and in the event, you run into any issues, please create a GitHub issue
Fixes and improvements
Prisma
- Formatter doesn't allow comments on consecutive indices
- Internal: reformatter is not idempotent
prisma format
strips comments on block level attributes- Reformatter crash in relation code
- Formatter crashes on arbitrary blocks
prisma --version
crashes ifopenssl
isn't properly installed- Rename 'getVersion' to 'getEngineVersion' in
@prisma/internals
- BigInt with a default value cause duplicates in all migrations
- Formatter: thread 'main' panicked at 'not yet implemented'
- Mongodb introspection fails with "called
Option::unwrap()
on aNone
value" - PSL should support inline
//
comments in the generator and datasource blocks - Unable to use native database types with Prisma and CockroachDB
Prisma Client
- High permanent CPU usage after calling $disconnect on a client that executed an interactive transaction before (v3.9.0+)
- Slow Tests
prisma generate
: Non-functional debounce mechanism for watch mode- Unknown error in SQLite Connector migrating from Prisma 3.x to 4.0.0 on ARM/M1 machines
- macOS 12 sometimes kills Node.js process when loading the QE library
Prisma Migrate
- migrate-cli: do not override RUST_LOG from the environment
- Incorrect migration creates on sql server when index deleted
- Float cause duplicate alter table in all migrations
- db error: ERROR: cannot drop view geography_columns because extension postgis requires it
Language tools (e.g. VS Code)
- Check when
@id
is suggested and fix - Implement a code action adding a unique constraint to a relation
- Potential pipeline
🔥 of language-tools with versioning change of@prisma/engines
- Cannot add comments to my @@unique constraints
@prisma/engines npm package
Credits
Huge thanks to @shian15810, @zifeo, @lodi-g, @Gnucki, @apriil15 for helping!
💼 We're hiring!
If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.
We're looking for a Technical Support Engineer and Back-end Engineer: Prisma Data Platform.
Feel free to read the job descriptions and apply using the links provided.
📺 Join us for another "What's new in Prisma" livestream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.
The stream takes place on YouTube on Thursday, July 19 at 5 pm Berlin | 8 am San Francisco.
v4.0.0
We're excited to share the 4.0.0
stable release today.
Prisma 4.0.0
features a variety of improvements across Prisma Migrate, Prisma schema, and Prisma Client. These changes will impact most Prisma users, particularly those who used some of our most popular Preview features around advanced index management, raw SQL queries, and filtering rows by properties of JSON.
As this is a major release, we included many breaking bug fixes and other enhancements, but we believe upgrading is worthwhile. You can learn about upgrading in our Prisma 4 Upgrade guide and the Prisma 4 Upgrade video.
Major improvements
Here's a TL;DR:
-
Preview features moved to General Availability
extendedIndexes
filterJson
improvedQueryRaw
-
Improvements to the Prisma Schema
- Defaults values for scalar lists (arrays)
- Improved default support for embedded documents in MongoDB
- Explicit unique constraints for 1:1 relations
- Removed support for usage of
references
on implicit m:n relations - Enforcing uniqueness of referenced fields in the
references
argument in 1:1 and 1:m relations for MySQL - Removal of undocumented support for the
type
alias - Removal of the
sqlite
protocol for SQLite URLs - Better grammar for string literals
-
New Prisma Client APIs
findUniqueOrThrow
findFirstOrThrow
-
General improvements
- Deprecating
rejectOnNotFound
- Fix rounding errors on big numbers in SQLite
-
DbNull
,JsonNull
, andAnyNull
are now objects - Prisma Studio updates
- Dropped support for Node 12
- New default sizes for statement cache
- Renaming of
@prisma/sdk
npm package to@prisma/internals
- Removal of the internal
schema
property from the generated Prisma Client
- Deprecating
extendedIndexes
is now Generally Available
Starting with this release, we're excited to announce that extendedIndexes
is now Generally Available!
generator client {
provider = "prisma-client-js"
- previewFeatures = ["extendedIndexes"]
}
We introduced extendedIndexes
in 3.5.0
and have constantly been shipping improvements in the subsequent releases to the configuration of indexes.
You can now configure indexes in your Prisma schema with the @@​index
attribute to define the kind of index that should be created in your database. You can configure the following indexes in your Prisma Schema:
Sort, sort order, and length
The length
argument is available on MySQL on the @id
, @@​id
, @unique
, @@​unique
, and @​@​index
fields. It allows Prisma to support indexes and constraints on String
with a TEXT
native type and Bytes
types.
The sort
argument is available for all databases on the @unique
, @@​unique
, and @@​index
fields. SQL Server also allows it on @id
and @@​id
.
datasource db {
provider = "mysql"
url = env("DATABASE_URL")
}
model Post {
title String @​db.VarChar(300)
abstract String @​db.VarChar(3000)
slug String @​unique(sort: Desc, length: 42) @​db.VarChar(3000)
author String
created_at DateTime
@​@​id([title(length: 100), abstract(length: 10)])
@​@​index([author, created_at(sort: Desc)])
}
Hash indexes for PostgreSQL
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
model A {
id Int @​id
value Int
@​@​index([value], type: Hash)
}
GIN
, GiST
, SP-GiST
and BRIN
indexes for PostgreSQL
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
model Post {
id Int @​id
title String
content String?
tags Json?
@​@​index([tags], type: Gin)
}
SQL Server index clustering
datasource db {
provider = "sqlserver"
url = env("DATABASE_URL")
}
model Post {
id Int @​default(autoincrement()) @​id(clustered: false)
title String
content String?
}
Refer to our docs to learn how you can configure indexes in your Prisma schema and the supported indexes for the different databases.
filterJson
is now Generally Available
This release moves the filterJson
Preview feature into General Availability! 🪄
generator client {
provider = "prisma-client-js"
- previewFeatures = ["filterJson"]
}
JSON filtering allows you to filter rows by the data inside a Json
type. For example:
const getUsers = await prisma.user.findMany({
where: {
petMeta: {
path: ['cats', 'fostering'],
array_contains: ['Fido'],
},
},
})
The filterJson
Preview feature has been around since May 2021, and we're excited to mark it ready for production use! Learn more in our documentation.
improvedQueryRaw
is now Generally Available
Prisma 4 now marks the improvedQueryRaw
Preview feature as Generally Available! 🤩
generator client {
provider = "prisma-client-js"
- previewFeatures = ["improvedQueryRaw"]
}
This change introduces two major improvements (both breaking, refer to the upgrade guide for a smooth upgrade) when working with raw queries with Prisma:
1. Scalar values are de-serialized as their correct JavaScript types
Raw queries now deserialize scalar values to their corresponding JavaScript types.
Note: Types are inferred from the values and not from the Prisma Schema types.
Here's an example query and response:
const res = await prisma.$queryRaw`SELECT bigint, bytes, decimal, date FROM "Table";`
console.log(res)
// [{ bigint: BigInt("123"), bytes: Buffer.from([1, 2]), decimal: new Prisma.Decimal("12.34"), date: Date("<some_date>") }]
Below is a table that recaps the serialization type-mapping for raw results:
Database Type | JavaScript Type |
---|---|
Text | String |
Int32 | Number |
Int64 | BigInt |
Float | Number |
Double | Number |
Numeric | Decimal |
Bytes | Buffer |
Json | Object |
DateTime | Date |
Date | Date |
Time | Date |
Uuid | String |
Xml | String |
2. PostgreSQL type-casts
Previously, PostgreSQL type-casts were broken. Here's an example query that used to fail:
await prisma.$queryRaw`SELECT ${1.5}::int as int`;
// Before: db error: ERROR: incorrect binary data format in bind parameter 1
// After: [{ int: 2 }]
You can now perform some type-casts in your queries as follows:
await prisma.$queryRaw`SELECT ${2020}::float4, (NOW() - ${"1 day"}::interval), ${"2022-01-01 00:00:00"}::timestamptz;`
A consequence of this fix is that some subtle implicit casts are now handled more strictly and would fail. Here's an example that used to work but won't work anymore:
await prisma.$queryRaw`SELECT LENGTH(${42});`
// ERROR: function length(integer) does not exist
// HINT: No function matches the given name and argument types. You might need to add explicit type casts.
The LENGTH
PostgreSQL function only accept text
as input. Prisma used to silently coerce 42
to text
but won’t anymore. As suggested by the hint, cast 42
to text
as follows:
await prisma.$queryRaw`SELECT LENGTH(${42}::text);`
Refer to our docs to learn more on raw query type mappings in Prisma.
4.0.0
, refer to our upgrade guide: Raw query type mapping: scalar values are now deserialized as their correct JavaScript types and Raw query mapping: PostgreSQL type-casts.
Defaults values for scalar lists (arrays)
Prisma 4 now introduces support for defining default values for scalar lists (arrays) in the Prisma schema.
You can define default scalar lists as follows:
model User {
id Int @​id @​default(autoincrement())
posts Post[]
favoriteColors String[] @​default(["red", "blue", "green"])
}
To learn more about default values for scalar lists, refer to our docs.
Improved default support for embedded documents in MongoDB
From version 4.0.0
, you can now set default values on embedded documents using the @default
attribute. Prisma will provide the specified default value on reads if a field is not defined in the database.
You can define default values for embedded documents in your Prisma schema as follows:
model Product {
id String @​id @​default(auto()) @​map("_id") @​db.ObjectId
name String @​unique
photos Photo[]
}
type Photo {
height Int @​default(200)
width Int @​default(100)
url String
}
Refer to our docs to learn more on default values for required fields on composite types.
4.0.0
.
Explicit unique constraints for 1:1 relations
From version 4.0.0
, 1:1 relations are now required to be marked with the @unique
attribute on the side of the relationship that contains the foreign key.
Previously, the relation fields were implicitly treated as unique under the hood. The field was also added explicitly when npx prisma format
was run.
model User {
id Int @​id @​default(autoincrement())
profile Profile? @​relation(fields: [profileId], references: [id])
profileId Int? @​unique // <-- include this explicitly
}
model Profile {
id Int @​id @​default(autoincrement())
user User?
}
references
on implicit m:n relations
Removed support for usage of This release removes the usage of the references
argument, which was previously optional when using m:n relations.
model Post {
id Int @​id @​default(autoincrement())
- categories Category[] @​relation("my-relation", references: [id])
+ categories Category[] @​relation("my-relation")
}
model Category {
id Int @​id @​default(autoincrement())
- posts Post[] @​relation("my-relation", references: [id])
+ posts Post[] @​relation("my-relation")
}
This is because the only valid value for references
was id
, so removing this argument clarifies what can and cannot be changed.
Refer to our docs to learn more about implicit m:n relations.
references
argument in 1:1 and 1:m relations for MySQL
Enforcing uniqueness of referenced fields in the From version 4.0.0
, Prisma will now enforce that the field on the references
side of a @relation
is unique when working with MySQL.
To fix this, add the @unique
or @id
attributes to foreign key fields in your Prisma schema.
4.0.0
, refer to our upgrade guide.
type
alias
Removal of undocumented support for the With 4.0.0
, we're deprecating the type
keyword for string aliasing. The type
keyword will now be exclusively used for defining embedded documents in MongoDB.
We encourage you to remove any usage of the type
keyword from your Prisma schema for type aliasing.
sqlite
protocol for SQLite URLs
Removal of the Starting from 4.0.0
, we are dropping support of the sqlite://
URL prefix for SQLite. We encourage you to use the file://
prefix when working with SQLite.
Better grammar for string literals
String literals in the Prisma schema now need to follow the same rules as strings in JSON. That changes mostly the escaping of some special characters.
You can find more details on the specification here:
To fix this, resolve the validation errors in your Prisma schema or run npx prisma db pull
to get the current values from the database.
findUniqueOrThrow
and findFirstOrThrow
New Prisma Client APIs: In this release, we're introducing two new APIs to Prisma Client:
-
findUniqueOrThrow
– retrieves a single record asfindUnique
but throws aRecordNotFound
exception when no record is not found -
findFirstOrThrow
– retrieves the first record in a list asfindFirst
but throws aRecordNotFound
exception when no record is found
Here's an example of usage of the APIs:
const user = await prisma.user.findUniqueOrThrow({
where: {
email: "alice@prisma.io",
},
})
user.email // You don't need to check if the user is null
The APIs will be convenient for scripts API routes where you're already handling exceptions and want to fail fast.
Note: Please use the APIs with care. If you use these APIs, add the proper guardrails to your application.
Refer to the API reference in our docs to learn how findUniqueOrThrow
and findFirstOrThrow
differ from findUnique
and findFirst
respectively.
rejectOnNotFound
Deprecating We're deprecating the rejectOnNotFound
parameter in favor of the new findUniqueOrThrow
and findFirstOrThrow
Prisma Client APIs.
We expect the new APIs to be easier to understand and more type-safe.
Refer to the findUniqueOrThrow
and findFirstOrThrow
docs to learn how you can upgrade.
Fix rounding errors on big numbers in SQLite
SQLite is a loosely-typed database. While Prisma will prevent you from inserting values larger than integers, nothing prevents SQLite from accepting big numbers. These manually inserted big numbers cause rounding errors when queried.
Prisma will now check numbers in the query's response to verify they fit within the boundaries of an integer. If a number does not fit, Prisma will throw a P2023
error:
Inconsistent column data: Conversion failed:
Value 9223372036854775807 does not fit in an INT column,
try migrating the 'int' column type to BIGINT
To learn more on rounding errors with big numbers on SQLite, refer to our docs.
DbNull
, JsonNull
, and AnyNull
are now objects
Previously, Prisma.DbNull
, Prisma.JsonNull
, and Prisma.AnyNull
used to be implemented using string constants. This meant their types overlapped with regular string data that could be stored in JSON fields.
We've now made them special objects instead that don't overlap with string types.
Before 4.0.0
DbNull
was checked as a string so you could accidentally check for a null as follows:
import { PrismaClient, Prisma } from '@​prisma/client'
const prisma = new PrismaClient()
const dbNull = "DbNull" // this string could come from anywhere!
await prisma.log.findMany({
data: {
meta: dbNull,
},
})
Expand to view the underlying Prisma schema
model Log {
id Int @​id
meta Json
}
Prisma 4 resolves this using constants guaranteed to be unique to prevent this kind of inconsistent queries.
You can now read, write, and filter JSON fields as follows:
import { PrismaClient, Prisma } from '@​prisma/client'
const prisma = new PrismaClient()
await prisma.log.create({
data: {
meta: Prisma.DbNull,
},
})
We recommend you double-check queries that use Json
after upgrading to Prisma 4. Ensure that you use the Prisma.DbNull
, Prisma.JsonNull
, and Prisma.AnyNull
constants from Prisma Client, not string literals.
Refer to the Prisma 4 upgrade guide in case you run into any type errors.
Prisma Studio updates
We've refined the experience when working with Prisma Studio with the following changes:
- Including a confirmation dialog before deleting records
- Adding a shortcut copy action on a cell – CMD + C on MacOS or Ctrl + C on Windows/ Linux
Dropped support for Node 12
The minimum version of Node.js Prisma will support is 14.17.x
. If you're using an earlier version of Node.js, you will need to update your Node.js version.
Refer to our system requirements for the minimum versions Prisma requires
New default sizes for statement cache
We had inconsistent and large default values (500 for PostgreSQL and 1000 for MySQL) for the statement_cache_size
. The new shared default value is 100.
If the new default doesn't work for you, please create an issue and use the statement_cache_size=x
parameter in your connection string to override the default value.
@prisma/sdk
npm package to @prisma/internals
Renaming of The internal package @prisma/sdk
is now available under the new, more explicit name @prisma/internals
.
We do not provide any API guarantees for @prisma/internals
as it might need to introduce breaking changes from time to time, and it does not follow semantic versioning.
This is technically not a breaking change as usage of the @prisma/sdk
package is neither documented nor supported.
If you're using @prisma/sdk
(now @prisma/internals
), it would be helpful if you could help us understand where, how, and why you are using it by giving us feedback in this GitHub discussion. Your feedback will be valuable to us in defining a better API.
schema
property from the generated Prisma Client
Removal of the internal We've removed the internal Prisma.dmmf.schema
to reduce the size of Prisma Client generated and improve boot times.
To access the schema
property, you can use the getDmmf()
method from @prisma/internals
.
Fixes and improvements
Prisma
- PSL: define the grammar of string literals
- MySQL: Update default
statement_cache_size
- You cannot define an index on fields with Native type Text of MySQL.
- Removal of undocumented support for
type
alias with Prisma 4.0.0 @unique
is added during Re-Introspection- [PSL] Do not allow
references
arg on Many2Many relations on SQL - prisma migrate dev will not allow for db level default on scalar list
- Postgres Single Quote Escaping Breaking Migrations
- [Epic]
extendedIndexes
GA - Remove preview feature
extendedIndexes
- Epic: Scalar List Defaults
- Implement scalar lists defaults proposal in PSL
- Implement scalar list defaults proposal in introspection
- Implement scalar list defaults proposal in migrations
- PANIC: called
Option::unwrap()
on aNone
value in query-engine/core/src/interpreter/query_interpreters/nested_read.rs:232:50 - Invalid
db pull
/db push
flow - Improve CLI output when using
db push
with MongoDB - DB Pull Error
- MongoDB composite index crashes
- Error: Error in migration engine. Reason: [migration-engine/core/src/commands/diff.rs:127:22] internal error: entered unreachable code: no provider, no shadow database url for migrations target
- Regression: Prisma 3.15.0 with macOS / Azure SQL Server errors at database connection
- Migrate internal duration/performance logging
- Fix CI support in prisma forks
- Allow setting the
length
prefix onUnsupported
fields on MySQL - CRDB: Handle unicode escaping in enum and string defaults in migrate/introspection
- Poor grammar and confusing language in Prisma CLI
- Datetime defaults: make sure we consume the whole expression
- @prisma/engine-core uses vulnerable
undici 5.1.1
package - getConfig/getDmmf: Clarify error messages on Rust panics
Prisma Client
- PANIC in libs/prisma-models/src/record.rs:161:30Invalid coercion encountered: ConversionFailure("Float(BigDecimal("519.05"))", "Decimal")
- Set array default
- Allow setting scalar list default values
- test(client): happy blog-env test has no assertion
- Avoid using magic string values for JsonNull/DbNull
PrismaClientInitializationError
is missing expected error code- Make the implicit unique constraints on 1:1 relations explicit
- PANIC: called
Result::unwrap()
on anErr
value: FieldNotFound { name: "upsert", model: "CcStructureUnit" } in query-engine/core/src/query_graph_builder/write/write_args_parser.rs:24:62 - Consider renaming the
@prisma/sdk
package to reduce confusion - PANIC: JSON target types only accept strings or numbers, found: {"bytes":"05010000000473436170"} in query-engine/connectors/sql-query-connector/src/filter_conversion.rs:542:22
- Cannot pass Prisma.empty to $executeRaw function
- Numerics in Postgres bigger than 2<<128 crash Prisma/Quaint
- Remove
sqlite:
for defining a sqlite url - PANIC: called
Option::unwrap()
on aNone
value in query-engine/core/src/interpreter/query_interpreters/nested_read.rs:232:50 - findMany broken with many relations to same entity
- PANIC: called
Option::unwrap()
on aNone
value in query-engine\core\src\interpreter\query_interpreters\nested_read.rs:232:50 - Large decimals cause panick
- Misleading Error for non-unique relation names
thread 'tokio-runtime-worker' panicked at 'called
Option::unwrap()on a
Nonevalue', /Users/runner/.cargo/git/checkouts/quaint-9f01e008b9a89c14/479e08a/src/connector/postgres/conversion/decimal.rs:81:39
- Implement scalar list defaults proposal in query engine and client
default(now())
on the same table sometimes yield different times
Language tools (e.g. VS Code)
Prisma Engines
Credits
Huge thanks to @shian15810, @zifeo, @ever0de, @givensuman, @peter-gy, @rushabhhere, @flatplate, @njmaeff, @tnzk, @DePasqualeOrg, @roboncode, @jacobhq for helping!
📺 Join us for another "What's new in Prisma" livestream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.
The stream takes place on YouTube on Thursday, June 30 at 5 pm Berlin | 8 am San Francisco.
📺 Learn how to upgrade in our webinar on July 12th
We're going to host a dedicated webinar with Prisma engineers to talk about the upgrade process. If you're unsure whether the breaking changes of this release affect you, be sure to not miss this livestream.
The stream takes place on YouTube on Tuesday, July 12 at 5 pm Berlin | 8 am San Francisco.
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.