@prisma/client

Today, we are issuing the 4.7.1 patch release.

Fixes in Prisma Client

• Enum fields are missing in select's type when clientExtensions preview feature is used
• console.log outputs incorrect value when result extensions are used
• "Field does not exist on enclosing type" error is thrown in findUniqueOrThrow
• Prisma Client Extensions: args is undefined

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

Highlights

Interactive transactions are now Generally Available

After an extensive Preview phase and lots of great feedback from our community, we're excited to announce that interactiveTransactions is now Generally Available and production ready! 🚀

Interactive transactions allow you to pass an async function into a $transaction, and execute any code you like between the individual Prisma Client queries. Once the application reaches the end of the function, the transaction is committed to the database. If your application encounters an error as the transaction is being executed, the function will throw an exception and automatically rollback the transaction.

Here are some of the feature highlights we've built:

• Support for defining transaction isolation levels — from 4.2.0
• Support for the Prisma Data Proxy — from 4.6.0

Here's an example of an interactive transaction with a Serializable isolation level:

await prisma.$transaction(
  async (prisma) => {
    // Your transaction...
  },
  {
    isolationLevel: Prisma.TransactionIsolationLevel.Serializable,
    maxWait: 5000,
    timeout: 10000,
  }
)

You can now remove the interactiveTransactions Preview feature in your schema.

Relation mode is Generally Available

This release marks relationMode="prisma" as stable for our users working with databases that don't rely on foreign keys to manage relations. 🎉

Prisma’s relation mode started as a way to support PlanetScale which does not allow you to create foreign keys for better online migration support. We transformed that into our Referential Integrity Emulation in 3.1.1 when we realised that more users could benefit from it, and then integrated it as the default mode for MongoDB, which generally does not have foreign keys. Prisma needed to use emulation to give the same guarantees.

We then realized the feature was more than just referential integrity and affected how relations work. To reflect this, we renamed the feature to relation mode and the datasource property to relationMode in 4.5.0

Index warnings for relationMode = "prisma"

In this release, we've added a warning to our Prisma schema validation that informs you that the lack of foreign keys might result in slower performance — and that you should add an @@index manually to your schema to counter that. This ensures your queries are equally fast in relation mode prisma as they are with foreign keys.

With relationMode = "prisma", no foreign keys are used, so relation fields will not benefit from the index usually created by the relational database under the hood. This can lead to slower performance when querying these fields. We recommend manually adding an index.

We also added a fix to our VS Code extension to help adding the suggested index with minimal effort:

If you are currently using the Preview feature flag to enable relation mode, you can now remove referentialIntegrity from the previewFeatures in your generator client block in your Prisma schema.

For more information, check out our updated relation mode documentation.

Prisma Client Extensions (Preview)

This release adds Preview support for Prisma Client Extensions. This feature introduces new capabilities to customize and extend Prisma Client. Today we are opening up four areas for extending Prisma Client:

• model: add custom methods or fields to your models
• client: add client-level methods to Prisma Client
• result: add custom fields to your query results
• query: create custom Prisma Client queries

Prisma Client Extensions are self-contained scripts that can tweak the behavior of models, queries, results, and the client (Prisma Client) as a whole. You can associate a single or multiple extensions with an extended client to mix and match Prisma to your needs.

Prisma Client Extensions enables many use cases such as defining virtual fields, custom validation, and custom queries.

It also enables you to share your client extensions with others and import client extensions developed by others into your project.

For example, given the following schema:

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

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

model User {
  id        Int     @id @default(autoincrement())
  email     String  @unique
  firstName String?
  lastName  String
}

You can create a computed field called fullName as follows:

import { PrismaClient } from "@prisma/client"

const prisma = new PrismaClient()
  .$extends({
    result: {
      user: {
        fullName: {
          // the dependencies
          needs: { firstName: true, lastName: true },
          compute(user) {
            // the computation logic
            return `${user.firstName} ${user.lastName}`
          },
        },
      },
    },
  })

We're excited to see what you build with them! For more information, check out our docs and let us know what you think in this GitHub issue.

Multi-schema support for PostgreSQL (Preview)

We're pleased to announce that this release adds support for multi-schema support for PostgreSQL. The ability to query and manage multiple database schemas has been a long-standing feature request from our community.

This release adds support for the following:

• Introspecting databases that organize objects in multiple database schemas
• Managing multi-schema database setups directly from Prisma schema
• Generating migrations that are database schema-aware with Prisma Migrate
• Querying across multiple database schemas with Prisma Client

If you already have a PostgreSQL database using multiple schemas, you can quickly get up and running using prisma db pull — on enabling the Preview feature and specifying the schemas in the datasource block similar to the example below.

You can get started with defining multiple schemas in your Prisma schema as follows:

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

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
  schemas  = ["base", "transactional"]
}

model User {
  id     Int     @id
  orders Order[]

  @@schema("base")
}

model Order {
  id      Int  @id
  user    User @relation(fields: [id], references: [id])
  user_id Int

  @@schema("transactional")
}

Then generate and apply the changes to your database with prisma migrate dev.

We want to thank all our users for helping us design the feature since the early proposal on GitHub up to our current Preview release.

For further details, refer to our documentation and let us know what you think in this GitHub issue.

Request for feedback

Our Product team is currently running a survey for designing Database Views support for Prisma and we would appreciate your feedback.

Fixes and improvements

Prisma Client

• RangeError: Invalid count value during npx prisma generate with DEBUG=* on integration build
• When rejectOnNotFound is used, chaining deeper into a related table still throws if it doesn't find anything
• Stabilize referentialIntegrity
• Some errors are obfuscated by interactive transactions when using binary engine
• Transaction API error: Transaction already closed: Transaction is no longer valid. Last state: 'Expired' P2028
• The error is incorrectly pointed out when using the $transaction method
• Client: using update + connect throws an error on an idempotent operation
• findFirstOrThrow / findUniqueOrThrow errors are not reported via error event
• wrong error message/header on multiple table upsert using transaction
• Args are out of sync with the action type for count when creating prisma middeware
• “Transaction API error: Transaction not found”
• Add Prisma.TransactionClient to default-index.d.ts
• RangeError: Invalid count value during prisma generate
• Prisma Client regression bug after upgrading to 4.6.0: findMany errors with PANIC: index out of bounds: the len is 0 but the index is 0
• upsert() with nested selection errors with called Option::unwrap()on aNone value in 4.6.0
• Bug(qe): errors don't get logged
• Downloading binaries of 4.6.1 fails with wrong sha256 checksum
• Calling findUnique concurrently with different key order causes one of them to return null
• No way to catch error in findUniqueOrThrow via middleware
• Test implicit m:n in relation mode prisma / Reproduction test for prisma#16390

Prisma

• [Multi Schema] Same model map different schema
• Schema: add deprecation warning for datasource property referentialIntegrity (renamed to relationMode)
• Error in migration engine. Reason: [migration-engine/connectors/sql-migration-connector/src/sql_renderer/postgres_renderer.rs:944:22] We should only be setting a changed default if there was one on the previous schema and in the next with the same enum.
• db pull with multiSchema error on schema with 2 models with the same table name but in a different schema
• Prisma 4.6.0 drops and recreates enum field when running db push even if the field has not changed
• @@map not working on postgress enums starting version 4.6.0
• relationMode: make feature GA
• Add SetDefault validation error with warnings when provider = "mysql" and relationMode = "foreignKeys" | default
• Polish relationMode validation warning messages
• Add linting/validation warnings for prisma validate & prisma format

Prisma Migrate

• What happen with prisma migrate dev
• Prisma complains when enum types are not declared in alphabetical order

Language tools (e.g. VS Code)

• Dim models that are @@ignored and fields that are @ignored
• Recommend adding indices to foreign keys when referentialIntegrity = "prisma"
• PostgreSQL only: Add autocompletion in the datasource block for extensions when postgresqlExtensions preview feature is set
• language-tools: relationMode GA - remove preview feature condition
• feat: for relationMode="prisma", for @relation: add a warning if there is no index on the field(s)
• feat: Quick Fix - relationMode : missing foreign keys' indexes

Prisma Engines

• bug(fmt): quick-fixes break with no newline after model in schema

Credits

Huge thanks to @cmd-johnson, @jsoref, @miguelgargallo for helping!

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, December 1 at 5 pm Berlin | 8 am San Francisco.