Update dependency prisma to ^3.15.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
prisma (source)	^3.7.0 -> ^3.15.2

---

Release Notes

prisma/prisma (prisma)

v3.15.2

Compare Source

Today, we are issuing the 3.15.2 patch release.

Fixes

In order to use the Prisma Data Proxy via Prisma Client, you need to generate it with prisma generate --data-proxy as described in our documentation. We are introducing PRISMA_GENERATE_DATAPROXY="true" as an additional way to do the same thing, but via an environment variable.

This is necessary, for example, to reliably deploy a Prisma Client for Data Proxy on Vercel Serverless Functions, where it can be hard to update the build command to run prisma generate --data-proxy. Starting with this version you can just set PRISMA_GENERATE_DATAPROXY="true" as an environment variable the Vercel project settings.

If you are unfamiliar with the Data Proxy, read how to get started.

v3.15.1

Compare Source

Today, we are issuing the 3.15.1 patch release.

Fixes

• Regression: Prisma 3.15.0 with macOS / Azure SQL Server errors at database connection

v3.15.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements

Improvements to Prisma Client for Data Proxy

In this release, we're shipping a couple of improvements to Prisma Client for Data Proxy.

The Prisma Data Proxy provides connection management and pooling for database connections for efficiently scaling database connections in serverless environments. The Prisma Client for Data Proxy provides support for connecting to the Prisma Data Proxy using HTTP.

We introduced this feature in version 3.3.0 and constantly shipped features, fixes, and improvements.

One of the changes in this release is improving the Prisma Client for the Data Proxy generation step.

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
- previewFeatures = ["dataProxy"]
}

You can generate Prisma Client for the Data Proxy it by using the --data-proxy flag:

npx prisma generate --data-proxy

We also updated how you can run Prisma Client using the Data Proxy in Cloudflare Workers and Edge environments. You can now use @prisma/client/edge instead of @prisma/client in your application.

import { PrismaClient } from '@​prisma/client/edge'

To learn more, check out our documentation.

Prisma Client Metrics is now in Preview

Metrics is a new Preview feature that allows you to monitor how Prisma Client interacts with your database. Metrics expose a set of counters, gauges, and histograms that can be labeled and piped into an external monitoring system like Prometheus or StatsD.

You can use metrics in your project to help diagnose how your application's number of idle and active connections changes with counters, gauges, and histograms.

To get started using metrics in your project, enable the Preview feature flag in your Prisma schema:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["metrics"]
}

You can then get started using metrics in your project:

import { PrismaClient } from '@​prisma/client'

const prisma = new PrismaClient()

const metrics = await prisma.$metrics.json()
console.log(metrics)

To learn more, check out the metrics documentation. Give it a try and let us know what you think.

Regression

Azure SQL on MacOS

This release includes a known regression when connecting to Azure SQL from MacOS only and will be resolved soon. Follow this issue for updates and resolution.

Fixes and improvements

migrate reset returns with a non-0 exit code if the seed script returns with a non-0 exit code

This will help user scripts know more about the success of the command, but might break existing scripts.

Prisma

• Schema validation does not accept absolute Windows style paths for SQLite database
• introspect --url throws error if existing schema file only contains generator
• prisma migrate reset always exits with 0, needs to exit with 1 on errors
• Error: Error in migration engine. Reason: [migration-engine/connectors/sql-migration-connector/src/sql_schema_differ/differ_database.rs:111:9] no entry found for key
• Error: Error in migration engine. Reason: [migration-engine/connectors/sql-migration-connector/src/sql_schema_differ/differ_database.rs:111:9] no entry found for key
• Error: Error in migration engine. Reason: [migration-engine/connectors/sql-migration-connector/src/sql_schema_differ/differ_database.rs:111:9] no entry found for key
• Would you like to create a Github issue? » Yes does nothing in terminal on Windows
• Error: [/rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/str/mod.rs:580:13] byte index 59 is not a char boundary; it is inside '....' (bytes 57..60) of 患者ID
• Schema Parsing/Validation error should include CLI version
• Prisma panic on invalid int
• Error: [/rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/core/src/str/mod.rs:584:13] byte index 47 is not a char boundary; it is inside '点' (bytes 46..49) of AirbyteRawYuriPagesAirbyteDataProperties推荐点RichText
• Introspection: Make SQL in tests more advanced so that Introspection results will include native types, not just scalar types
• Add more integration tests for CockroachDB for db and migrate commands
• MongoDB - prisma db pull
• Multi-byte character truncation bug in mongo introspection connector
• MSSQL Docker Run Migration "The Trust Settings Record was corrupted"
• Running DB Pull on Remote MSSQL database
• Error: Error in migration engine. Reason: [libs/sql-schema-describer/src/postgres.rs:1039:28] no entry found for key
• Error: [libs\sql-schema-describer\src\postgres.rs:1039:28] no entry found for key
• prisma migrate deploy error

Prisma Client

• Support Bytes on SQLite
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87
• Huge Int value in upsert causes: "PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87"
• Data Proxy Client should't need to be re-generated after modifying .env files
• Data Proxy Client stopped working in Vercel Edge Functions / Next 12.0.4
• PANIC: called Option::unwrap() on a None value in query-engine\core\src\query_document\parser.rs:250:87
• Data Proxy: prisma generate errors with Error: Error: ENOENT: no such file or directory, open '/[...]/prisma/schema.prisma' when using a custom name for the Prisma schema file
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87
• DATABASE_URL is baked in Dataproxy client proxy.js
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87
• Can't save string to Decimals list
• Sveltekit + Cloudflare adapter - "PrismaClient is unable to be run in the browser."
• TypeError: at normalizeAndValidateHeaderValue with data proxy in cloudflare workers/miniflare
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87
• Implement "CLI engine crash reporting" for Formatter Engine and getConfig and getDmmf of Query Engine
• Add test for internal engine port
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87
• DataProxy Client only works if I instantiate a normal Client first
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87
• Engine hard crashes on id values exceeding the Number.MAX_SAFE_INTEGER
• dbgenerated function cause Null constraint error in MySQL
• Expose Metrics in Prisma Client
• Improve the DX for enabling the data proxy
• Client crash on out-of-range integer update using Postgres
• Prisma Client has stopped working on Vercel Edge Functions
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87
• InvalidDatasourceError of Data Proxy Client outputs a code snippet
• A few small typos in the repo (unkown)
• Cloudflare Workers with PlanetScale db

Credits

Huge thanks to @​shian15810, @​zifeo, @​ever0de, @​rushabhhere for helping!

Prisma Day

Prisma Day is back this year, and it'll be on June 15 - 16 at the James June Sommergarten in Berlin. Join us in-person or online for talks and workshops on modern application development and databases. Come and meet and chat with the team behind the Prisma ORM and Prisma Data Platform.

💼 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 through 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, June 9 at 5 pm Berlin | 8 am San Francisco.

v3.14.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements

CockroachDB connector is now Generally Available!

We are proud to announce the CockroachDB connector is now stable and Generally Available. The connector was built in joined efforts with the team at Cockroach Labs and comes with full Prisma Client and Prisma Migrate support.

If you're upgrading from Prisma version 3.9.0+ or the PostgreSQL connector, you can now run npx prisma db pull and review the changes to your schema. To learn more about CockroachDB-specific native types we support, refer to our docs.

To learn more about the connector and how it differs from PostgreSQL, head to our documentation.

PostgreSQL GIN, GiST, SP-GiST, and BRIN indexes support (Preview)

We introduced the extendedIndexes Preview feature in version 3.5.0, and we have been adding new configuration options for indexes. We've expanded index type support with the GIN, GiST, SP-GiST, and BRIN indexes in this release.

To make use of an index type, you can update your Prisma schema by providing the type argument to the @@​index attribute:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["extendedIndexes"]
}

model Post {
  id      Int     @​id
  title   String
  content String?
  tags    Json?

  @​@​index([tags], type: Gin)
}

The following SQL will be generated in your migration when you run prisma migrate dev:

CREATE TABLE "Post" (
    "id" INTEGER NOT NULL,
    "title" TEXT NOT NULL,
    "content" TEXT,
    "tags" JSONB,
    CONSTRAINT "Post_pkey" PRIMARY KEY ("id")
);

CREATE INDEX "Post_tags_idx" ON "Post" USING GIN ("tags");

To learn more about configuring index types in your schema, refer to our documentation.

Improved queryRaw API

In this release, we made improvements to the SQL raw API. Some improvements are breaking and will be available behind the new improvedQueryRaw Preview feature flag.

The improvedQueryRaw Preview feature solves most of the issues faced when working with the raw API. We would encourage you to turn on the Preview feature flag, try out the new API, and let us know how we can make it even better.

You can enable the Preview feature in your Prisma schema as follows:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["improvedQueryRaw"]
}

Here's a list of the improvements improvedQueryRaw comes with:

1. Raw scalar values are deserialized as their correct JavaScript types

Prisma Client queries such as findMany deserialize database scalar values to their corresponding JavaScript types. For example, a DateTime value is deserialized as a JavaScript Date, and a Bytes would be deserialized as a JavaScript Buffer.

Raw queries now implement the same behavior when the improvedQueryRaw Preview feature flag is enabled.

⚠️ This change is not yet available in the SQLite connector.

The types of values from the database will be used instead of the types in the Prisma schema. 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>") }]

Here's a table that recaps the serialization type-mapping for raw results:

Database Type	Javascript Type
Text	String
Int32	Number
Float	Number
Double	Number
Int64	BigInt
Numeric	Decimal
Bytes	Buffer
Json	Object
DateTime	Date
Date	Date
Time	Date
Uuid	String
Xml	String

2. PostgreSQL type-casts

We've also fixed a lot of PostgreSQL type-casts that were broken by enabling the improvedQueryRaw Preview feature flag.

Here's an example of a 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 more type-casts in your queries:

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 under the improvedQueryRaw feature flag:

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 coerce 42 to text silently, but won’t anymore. As suggested by the hint, cast 42 to text as follows:

await prisma.$queryRaw`SELECT LENGTH(${42}::text);`

3. Query parameters are correctly sent to the database

This improvement is available without the improvedQueryRaw Preview feature flag.

Before this release, query parameters of type BigInt, Bytes, and Decimal were incorrectly sent to the database leading to instances of unexpected inserts. Passing the types as query parameters now works:

await prisma.$executeRaw`INSERT INTO "Table" ("bigint", "bytes", "decimal") VALUES (${BigInt("123")}, ${Buffer.from([1, 2, 3])}, ${new Prisma.Decimal("12.23")});`

Fixes and improvements

Prisma Client

• Improve type conversion and responses for raw queries
• Postgres parameterized interval is passed incorrectly in raw query
• queryRaw cannot handle some numbers
• Query raw run throws the following error incorrect binary data format in bind parameter 3
• BigInt becomes Number if queried with $queryRaw
• Weird behavior of raw query containing st_dwithin and radius parameter binding
• generate output with output has weird package path on Windows
• Casting error when using integers in raw query
• $queryRaw fails when passing bigint as parameter
• Decimal becomes Number if queried with $queryRaw
• $queryRaw doesn't allow for typecasts
• Raw sql Is not working as expected
• Missing $ from executeRaw in error message "Invalid `prisma.executeRaw()` invocation:"
• Parameterized ExecuteRaw breaks with Postgres Floats
• PANIC: called Result::unwrap() on an Err value: Any { .. } in query-engine/connectors/sql-query-connector/src/error.rs:58:51
• $queryRaw to Postgres failing to correctly insert/cast numeric parameters
• Compound primary key is not generated when a unique field has the same name
• referentialIntegrity = prisma: Broken query on onUpdate: Cascade | symbol ... not found | The column ... does not exist in the current database.
• Getting a "Raw query failed. Code: N/A. Message: error deserializing column 0: a Postgres value was NULL``" error when using Postgres ARRAY_AGG with a nullable column
• Planetscale not able to upsert with Prisma
• connectOrCreate deletes old relation and creates a new one
• referentialIntegrity=prisma causes P2022 (column not exist) on updating a record
• Unable to insert Buffer into Bytes pg field using $executeRaw
• CockroachDB: Figure out, test and document which versions we support
• Implement debugPanic like functionality for getConfig and getDmmf of Query Engine
• $queryRaw returning numbers for bigint fields
• Prisma returns sequence values with number type from Postgres while using queryRaw
• PANIC: called Result::unwrap() on an Err value: Any { .. } in query-engine/connectors/sql-query-connector/src/error.rs:58:51
• RQ: Properly coerce query raw input parameters in the Query Engine
• RQ: Properly coerce query raw result in the Client
• RQ: Send type-hinted query parameters for raw queries (Postgres)
• RQ: Integrate new QE result for query raw in the client
• thread 'tokio-runtime-worker' panicked at 'internal error: entered unreachable code: Relation fields should never hit the BSON conversion logic.', query-engine/connectors/mongodb-query-connector/src/value.rs:34:35
• Exception when using Decimal.js instance in an input

Prisma

• Error: Error in migration engine. Reason: [migration-engine\cli\src/main.rs:68:41] called Result::unwrap() on an Err value: Custom { kind: InvalidData, error: "stream did not contain valid UTF-8" }
• Allow creating GIN index on JSONB fields in Postgres adapter
• prisma format panics when you use a colon to declare field type (field: Type syntax)
• Better error message if using TEXT or BLOB in MySQL @​id/@​index/@​unique
• Schema validation error mentions Error parsing attribute "@​id" but it's actually about @@​id
• Support GiST Index type with Postgres
• MySQL 8 function as default not created in first migration
• Error: [introspection-engine/connectors/sql-introspection-connector/src/commenting_out_guardrails.rs:32:59] called Option::unwrap() on a None value
• Nicer error message when you try to migrate a CockroachDB database with a provider=posgresql schema
• Using --url for db pull ignored/overwrites provider=cockroachdb
• CockroachDB: support more autoincrementing integer primary key representations
• Prisma migrate always DROP DEFAULT on CockroachDB
• Allow using a custom root certificate with SQL Server
• Write basic tests for cockroachdb in prisma/prisma
• CockroachDB: re-add Oid native type
• Support Generalized Inverted Indices on CockroachDB
• Missing validation on decimal defaults
• Log error details in console when we fail to submit an error report

Prisma Migrate

• CockroachDB session settings for migrations

Language tools (e.g. VS Code)

• Autocompletion support for composite type indexes
• Add tests for new CockroachDB native types
• Completion for new CockroachDB sequences

Credits

Huge thanks to @​ever0de, @​flatplate, @​njmaeff, @​tnzk, @​DePasqualeOrg for helping!

Prisma Day

Prisma Day is back this year, and it'll be on June 15 - 16 at the JamesJune Sommergarten in Berlin. Join us in-person or online for talks and workshops on modern application development and databases. Come and meet and chat with the team behind the Prisma ORM and Prisma Data Platform.

💼 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 hiring for a number of roles: Technical Support Engineer, Back-end Engineer: Prisma Data Platform, and a Developer Advocate(Frontend/ Fullstack). You can find more jobs we're hiring for on our jobs page.

Feel free to read through 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, May 12 at 5 pm Berlin | 8 am San Francisco.

v3.13.0

Compare Source

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

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements

migrate diff and db execute are now Generally Available!

We released two new Preview CLI commands in version 3.9.0 – prisma migrate diff and prisma db execute – to enable our users to create and understand migrations and build their workflows using the commands.

We're proud to announce that the commands are now Generally Available and can now be used without the --preview-feature flag. 🎉

The prisma migrate diff command creates a diff of your database schema, Prisma schema file, or the migration history. All you have to do is feed the command with a schema from state and a schema to state to get an SQL script or human-readable diff.

In addition to prisma migrate diff, prisma db execute is used to execute SQL scripts against a database. You can directly execute prisma migrate diff's output using prisma db execute --stdin.

Both commands are non-interactive, so it's possible to build many new workflows such as forward and backward migrations with some automation tooling. Take a look at our documentation to learn some of the popular workflows these commands unlock:

• Fixing failed migrations
• Squashing migrations
• Generating down migrations
• Command reference for migrate diff and db execute

Let us know what tools, automation, and scripts you build using these commands.

SQL Server index clustering (Preview)

In version 3.5.0, we introduced the extendedIndexes Preview feature which we have constantly been adding new configuration options for indexes. In this release, we added support for enabling or disabling index/constraint clustering in SQL Server.

By default, indexes will be clustered by default. You can update this in your schema as follows to disable index clustering:

datasource db {
  provider = "sqlserver"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["extendedIndexes"]
}

model Post {
  id      Int     @​default(autoincrement()) @​id(clustered: false)
  title   String
  content String?
}

The following SQL will be generated in your migration when you run prisma migrate dev

CREATE TABLE [Post] (
  id INT NOT NULL,
  [title] VARCHAR(255) NOT NULL,
  [content] NVARCHAR(1000),
  CONSTRAINT [Post_pkey] PRIMARY KEY NONCLUSTERED (id)
)

If you've enabled the extendedIndexes Preview feature, this is potentially a breaking change. Refer to our documentation to learn how you can upgrade from a previous version.

Updated native types for CockroachDB (Preview)

We have revamped the native types available in the CockroachDB connector. We initially re-used the PostgreSQL native types because they were close enough, but we have now adapted our list of the supported native types to match what CockroachDB supports.

If you are already using CockroachDB in your project, you can run prisma db pull to update all the native types in your Prisma schema. Refer to our documentation for the complete list of all CockroachDB native types.

OpenSSL 3.0 Support

We're excited to announce that version 3.13.0 now supports OpenSSL 3.0. Operating systems such as Ubuntu 22.04 default to OpenSSL 3.0, and when running prisma generate, you would run into the following error:

Error: Unknown binaryTarget debian-openssl-3.0.x

If you've run into a similar error, bump up to the latest Prisma version and give it another try!

Fixes and improvements

Prisma Client

• Support OpenSSL 3.0
• Create a test factory for newer and cleaner tests
• Invalid Binary Target for OpenSSL V3 on CentOS Stream 9
• thread 'tokio-runtime-worker' panicked at 'not yet implemented'

Prisma

• prisma init needs CockroachDB in the providers list
• db execute: confusing error message when doing DROP DATABASE "test-doesnotexists;" says that Database postgres.public does not exist
• [Diff] Always error if path to Sqlite db is wrong or db does not exist
• CockroachDB: Change the integer native types to the idiomatic ones
• CockroachDB: use idiomatic native types
• Prisma migrate diff just crashed.
• prisma init --datasource-provider=cockroachdb --url ... sets provider to postgresql
• MongoDB: Add spinner to Introspection
• Remove --preview-feature flag for Primitives (migrate diff and db execute)
• "reportFailedMessage" is never displayed in case a panic error fails to be submitted to the reporting service
• Support defining index clustering
• MongoDB: Invalid relation does not throw validation error

Language tools (e.g. VS Code)

• Rework auto completion tests
• Internal: For PR / branches it would be great to have an easy way to test the VS Code extension

Prisma Engines

• Moving to NAPI-rs v2

Credits

Huge thanks to @​ever0de, @​jacobhq, @​dkantereivin, @​CommanderRoot 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 Senior Software Engineer (Prisma Data Platform).

Feel free to read through 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, April 28 at 5 pm Berlin | 8 am San Francisco.

v3.12.0

Compare Source

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

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements and new features

MongoDB is now Generally Available

If you’ve been using MongoDB since it was in Preview, we'd like to say: Thank you! Your testing and feedback has been essential during the preview phase, and our MongoDB support is much better because of it.

Today we’re proud to announce that MongoDB is now stable and production-ready. After upgrading to 3.12.0, you can remove the MongoDB preview flag in your schema:

 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
 }

 generator client {
   provider        = "prisma-client-js"
-  previewFeatures = ["mongoDb"]
 }

We’ve been working hard towards this day ever since we launched MongoDB in Preview in July 2021.

Here are some of the feature highlights we developed over this period:

• Expressive and type-safe operations for querying MongoDB embedded documents
• Thorough introspection support for using Prisma with existing MongoDB databases
• Declarative index management right from your Prisma Schema with db push
• Powerful raw query APIs to help you incrementally migrate to Prisma

You can learn about these features in the release blog post, and more, in our freshly brewed MongoDB Guide. For newcomers to Prisma with MongoDB, we recommend you check out our Getting Started Guide.

To celebrate this milestone, we invite you to join Prisma’s MongoDB Launch Week starting on April 25th. Enjoy a jam-packed week of exclusive workshops with plenty of opportunities to win free MongoDB Atlas credits and swag. It’s free to sign-up and available anywhere you have an internet connection.

🚨 Please be aware that we made a few breaking changes to tie up loose ends before General Availability:

• @db.Array replaced with @db.ObjectId
• Removed Decimal support

We made some changes in the 3.11.1 patch release in case you missed it.

Index support on composite type fields

We also added support for adding indexes on embedded document fields in MongoDB. This means that you can now define a normal, unique, or full-text index in your schema.

type Address {
  street String
  number Int
}

model User {
  id      Int     @​id
  email   String
  address Address

  @​@​index([email, address.number])  /// normal index
  @​@​unique([email, address.street])  /// unique index
  @​@​fulltext([email, address.street]) /// full-text index
}

Note: Prisma Client does not yet fully support the feature for now. This will be rolled out in a future release.

Improved Connection Pooling Resiliency

In 3.12.0, we busted a ghost that has been bugging teams since the early days of the Prisma ORM. Under certain amounts of load, some people reported that the connection pool would sometimes drop connections or deadlock and not recover.

After many sightings and a lot of head-scratching, we were finally able to reproduce the issue. This allowed us to narrow down the problem to one of our dependencies and fix the problem.

To read the nitty gritty details of the problem and our solution, check out this issue.

Fixes and improvements

Prisma Client

• Bundling fails on 2.21.0
• "Timed out fetching a new connection from the pool" message is misleading
• I get "Can't resolve '_http_common'" when I use NestJS with monorepo (webpack)
• Broken on Next.js 10.2.0 which uses Webpack 5 when running a custom server to support HTTPS locally
• Timed out fetching a new connection from the pool
• Multiple prisma with nx workspaces and nestjs
• Prisma Client (Binary): upgrade to undici@4
• issue with connection pool ?
• Prisma does not recover from PrismaClientInitializationError
• Connection pool timeout errors when using higher connection_limit
• DB connection retry not happening
• Prisma does not recover from DB being down on start up
• Prisma client never recovers from P1001
• new PrismaClient() can not find schema.prisma file when use with pnpm workspace
• Prisma client cannot find datamodel path ("schema.prisma")
• Interactive Transaction concurrent writes cause Prisma to hang
• MongoDB: improve error message Inconsistent column data: Malformed ObjectID by including the field(s) in the message
• Unable to establish a connection once database recovers
• Composite Type should disallow null on a required contains one
• Prisma 3.9.x+ multiple clients being generated, and in the wrong Yarn 1 workspace
• MongoDB: Inconsistent column data: Failed to convert ... error on invalid data in properties does not mention affected field (and other useful information)
• MongoDB findRaw doesn't seem to work
• errorFormat:"minimal" or other options not working
• Interactive transactions are not logging DB queries
• Count action ends up being called aggregate when checking in middleware
• MongoDB logging QueryEvent type params is undefined
• MDBGA: Finish refactoring MongoDB queries to use boolean expressions
• Re-evaluate and -confirm supported native types on MongoDB
• Allow to filter by undefined fields in MongoDB
• MongoDB GA: Remove Preview Feature checks and Preview mentions

Prisma

• Connection issues never seem to go away(how to deploy prisma live reliably) [MySQL, TypeGraphQL, EBS]
• Error: [libs/datamodel/connectors/dml/src/model.rs:222:92] called Option::unwrap() on a None value
• Error: [libs\sql-schema-describer\src\lib.rs:171:32] Column id not found in Table videos
• Prisma Migrate shows warning when editing rolled-back migration
• Prisma client not attempting to reconnect on "Can't reach database server"
• Error: Error in migration engine. Reason: [libs\sql-schema-describer\src\walkers.rs:592:14] STATE ERROR BOOP
• Error report
• MongoDB type inference mismatch
• Error: [libs\datamodel\core\src\transform\dml_to_ast\mod.rs:74:59] called Option::unwrap() on a None value
• Cannot use prisma db push on MongoDB with @unique id
• CockroachDB: Remove the Json native type
• Error: [libs/datamodel/connectors/dml/src/model.rs:363:66] called Option::unwrap() on a None value
• Error: [libs/datamodel/core/src/transform/dml_to_ast/mod.rs:74:59] called Option::unwrap() on a None value
• Can migrate diff correctly resolve relative SQLite file path from schema?
• Introspection: MongoDB: Warnings mention Native Types instead of PSL types (e.g. Document instead of Json)
• MongoDB: Mixed data comments should mention PSL types instead of Mongo Native Types (Int32 => Int)
• Composite Indices: Support in the PSL
• Composite Indices: MongoDB Introspection Connector
• Composite Indices: MongoDB Migration Connector
• [MDB] Validate valid field / key names in the datamodel
• Introspecting indexes on embedded documents leads to validation error
• [Mongo] Improve native type validations in composite types
• [Mongo] Too generic error messages in composite types

Prisma Migrate

• Unique/Index keeps getting recreated
• Introspected CockroachDB schema has different field type than original Prisma schema that was migrated

Language tools (e.g. VS Code)

• prisma-fmt panic when @db.Array() is added in a MongoDB schema
• Embedded many-to-many relations do not suggest valid values in references
• @​relation auto completion: fields and references are still suggested when already present (when trailing comma is missing)
• Native type Array() is still auto suggested

Prisma Engines

• [Composites] Implement updateMany write operation
• [Composites] Implement deleteMany write operation
• Remove decimal support from MongoDB
• Investigate intermittently failing cockroachdb test suite on buildkite
• [MongoDB] Having filters don't work without selection

Credits

Huge thanks to @​ever0de, @​chronotc, @​hayes, @​maddhruv, @​jasimon, @​codesee-maps[bot], @​andyrichardson, @​xnerhu, @​Josh-a-e, @​dusandz for helping!

💼 We're hiring!

If you're interested in joining our growing team to help empower developers build data-intensive applications, Prisma is the place for you.

We're looking for a Developer Success Engineer and Back-end Engineer: Prisma Data Platform.

Feel free to read through 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, April 7 at 5 pm Berlin | 8 am San Francisco.

v3.11.1

Compare Source

Today, we are issuing the 3.11.1 patch release.

MongoDB (Preview)

Breaking: Filters no longer return undefined fields by default

In 3.11.1, we've changed what data is returned when filtering MongoDB documents on undefined fields. The new rule is that undefined fields are excluded by default unless explicitly filtered for. This allows you to query for undefined and null values separately.

Let's take a look at a concrete example. Given the following Prisma schema:

model Address {
    id     Int    @​id @​map("_id")
    city   String
    street String? // Note that street is optional
}

For Mongo, optional fields can either be null or undefined (absent). The following documents are all valid for the schema above:

{ "_id": 1, "city": "San Fransisco", "street": "Market st." }
{ "_id": 2, "city": "Seattle", "street": null }
{ "_id": 3, "city": "Chicago" }

Prior to 3.11.1, if you queried for where: { street: null }, you'd get _id: 2 and _id: 3. In 3.11.1, you'll only get _id: 2. The ability to also query for the missing fields has also been added. For details, refer to the new isSet below to learn more.

There are a few exceptions to this new default:

• A having filter on an aggregated field will return undefined fields. This is because aggregation on undefined fields yields null, not undefined, thus matching the filter.
• Filters on undefined to-many relations (e.g., the backing array of a many-to-many is undefined) will currently include those relations in the result set.

New isSet filter operation

To compensate for missing fields on documents no longer being returned by the filters above, we’ve added a new isSet: bool filter. This filter can be used to include fields that are undefined on documents.

Using the example above, to include the undefined fields, you can use an OR:

await prisma.address.findMany({
  where: {
    OR: [
      { street: { isSet: false } },
      { street: null }
    ]
  }
})

The isSet operation has been added to all scalar and embedded fields that are optional.

New unset operation

In 3.11.1, you can also remove a field with the unset operation.

Using the example above, let's write a query to remove the street field:

await prisma.address.update({
  where: {
    id: 10,
  },
  data: {
    street: {
      unset: true,
    },
  },
})

This effectively sets the street field to undefined in the database.

New updateMany operation

We now support updating embedded documents that match specific criteria.

For example, given the following schema:

model Product {
  id          Int  @​id @​map("_id")
  name        String  @​unique
  photos      Photo[]
}

type Photo {
  height Int    @​default(200)
  width  Int    @​default(100)
  url    String
}

Let's update the photo with a url of 1.jpg to 2.png:

const product = prisma.product.update({
  where: {
    id: 10,
  },
  data: {
    photos: {
      updateMany: {
        where: {
          url: '1.jpg',
        },
        data: {
          url: '2.png',
        },
      },
    },
  },
})

New deleteMany operation

Similar to updateMany, you can also remove embeds that match specific criteria.

Using the Prisma Schema above, let's delete all photos with a height of 100:

const product = prisma.product.update({
  where: {
    id: 10,
  },
  data: {
    photos: {
      deleteMany: {
        where: {
          height: 100,
        },
      },
    },
  },
})

v3.11.0

Compare Source

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

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements and new features

Experimental support for Embedded Document Filters

In the previous release, we added embedded document support for creates, updates, and deletes. In version 3.11.0, we’re adding the ability to filter embedded documents.

Given the following schema:

datasource db {
  provider = "mongodb"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["mongoDb"]
}

model Product {
  id     String  @​id @​default(auto()) @​map("_id") @​db.ObjectId
  photos Photo[]
}

model Order {
  id              String   @​id @​default(auto()) @​map("_id") @​db.ObjectId
  shippingAddress Address
  billingAddress  Address?
}

type Photo {
  height Int
  width  Int
  url    String
}

type Address {
  street String
  city   String
  zip    String
}

You can now filter within an embedded document:

// find all orders with the same shipping address
const orders = await prisma.order.findMany({
  where: {
    shippingAddress: {
      equals: {
        street: "555 Candy Cane Lane",
        city: "Wonderland",
        zip: "52337",
      },  
    },
  },
})

You can also filter on a "contains many" relationship:

// find all products that don't have photos
const product = prisma.product.findMany({
  where: {
    photos: {
      isEmpty: true
    }
  },
})

This scratches the surface of what's possible. For a complete list of available operations, have a look at our documentation. Please share your feedback in this issue.

Ordering by embedded documents is in Preview

In addition to filtering, Prisma version 3.11.0 now supports sorting by an embedded document.

Using the example schema above, you can sort orders by their zip code:

// sort orders by zip code in ascending order
const orders = await prisma.order.findMany({
  orderBy: {
    shippingAddress: {
      zip: "asc",
    },
  },
})

Learn more about this feature in our documentation and don’t hesitate to reach out in this issue.

MongoDB query logging support

In this release, we’ve added the ability to log MongoDB queries. You can enable query logging in the PrismaClient constructor:

const prisma = new PrismaClient({
  log: [
    {
      emit: 'event',
      level: 'query',
    },
  ]
})

prisma.$on('query', (e) => console.log(e.query))

After enabling query logging, you'll start to see logs that resemble this in your console:

db.User.deleteMany({ _id: ( $in: [ “62261e0b18139c6099ba7097”, ], }, }) 
db.User.deleteMany({ _id: ( $in: [ “6226277a960695

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/generates/whip).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzMi4yMDIuNCIsInVwZGF0ZWRJblZlciI6IjM3LjguMSIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->