⬆️ Bump @prisma/client from 2.14.0 to 2.26.0

[dependabot]

Bumps @prisma/client from 2.14.0 to 2.26.0.

Release notes

Sourced from @​prisma/client's releases.

2.26.0

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

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

Major improvements & new features

Referential Actions now enable cascading deletes and updates (Preview)

In this release we are introducing a new feature in Preview which enables fine-grained control over referential actions ON DELETE and ON UPDATE for the foreign keys supporting relations in Prisma models.

Current behavior

Until now, Prisma created a foreign key for each relation between Prisma models with the following defaults: ON DELETE CASCADE ON UPDATE CASCADE. In addition, when invoking the delete() or deleteAll() methods, Prisma Client performs runtime checks and will prevent the deletion of records on required relations if there are related objects referencing it, effectively preventing the cascade delete behavior. When using raw SQL queries for deletion, Prisma Client won't perform any checks, and deleting a referenced object will effectively cause the deletion of the referencing objects.

Example:

model User {
  id    String @id
  posts Post[]
}
model Post {
id       String @​id
authorId String
author   User   @​relation(fields: [authorId])
}

prisma.user.delete(...) and prisma.user.deleteAll() will fail if the user has posts.

Using raw SQL, e.g. using $queryRaw() to delete the user will trigger the deletion of its posts.

New behavior

⚠️ Turning on this feature could, when using delete() and deleteMany() operations, delete more data than before under certain circumstances. Make sure you read down below to understand why and anticipate these changes.

The feature can be enabled by setting the preview feature flag referentialActions in the generator block of Prisma Client in your Prisma schema file:

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

With the feature enabled, the behavior is now the following:

• It's possible to choose specific referential actions for the foreign keys in relations. Prisma Migrate, prisma db push, and introspection will set these in the database schema, e.g. @relation(... onDelete: SetNull) will set translate to ON DELETE SET NULL on the corresponding foreign key. See Syntax section below.

... (truncated)

Commits

• f2960a0 fix(deps): update engines to v2.26.0-23.9b816b3aa13cc270074f172f30d6eda8a8ce867d
• c8a179b refactor(*): Polish Node-API library implementation (#7898)
• 0389d2e fix(sdk): local dev with linked packages (#7879)
• 57a7e7f test(client): skip flaky referentialActions sql server test (#7907)
• e064efe chore(deps): update dependency @​prisma/studio-server to v0.408.0 (#7842)
• 0330e3f fix(client, mssql): multi param for prepared statements (#7880)
• e87d795 test: simple test for referentialAction cascade with and without flag (#7865)
• febfba9 fix(cli): add --datasource-provider to init command (#7671)
• c8b8825 fix(deps): update engines to v2.26.0-20.e6bd3dc12d849124a04c3a8e6bd9c194381af...
• f61657a fix(deps): update engines to v2.26.0-19.e6bd3dc12d849124a04c3a8e6bd9c194381af...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by prismabot, a new releaser for @​prisma/client since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #1818.