prisma/prisma
### [`v2.30.0`](https://togithub.com/prisma/prisma/releases/2.30.0)
[Compare Source](https://togithub.com/prisma/prisma/compare/2.29.1...2.30.0)
Today, we are excited to share the `2.30.0` stable release 🎉
🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v2.30.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.30.0) about the release.** 🌟
##### New features & improvements
##### Full-Text Search for PostgreSQL is now in Preview 🚀
We're excited to announce that Prisma Client now has [preview support](https://www.prisma.io/docs/about/prisma/releases#preview) for Full-Text Search on PostgreSQL.
You can give this a whirl in **2.30.0** by enabling the `fullTextSearch` preview flag:
```prisma
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
generator client {
provider = "prisma-client-js"
previewFeatures = ["fullTextSearch"]
}
model Post {
id Int @id @default(autoincrement())
title String @unique
body String
status Status
}
enum Status {
Draft
Published
}
```
After you regenerate your client, you'll see a new `search` field on your `String` fields that you can query on. Here are a few examples:
```ts
// returns all posts that contain the words cat *or* dog.
const result = await prisma.post.findMany({
where: {
body: {
search: 'cat | dog',
},
},
})
// All drafts that contain the words cat *and* dog.
const result = await prisma.posts.findMany({
where: {
status: "Draft",
body: {
search: 'cat & dog',
},
},
})
```
You can learn more about how the query format works in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/full-text-search). We would love to know your feedback! If you have any comments or run into any problems we're available in this [in this Github issue](https://togithub.com/prisma/prisma/issues/8877).
##### Validation errors for referential action cycles on Microsoft SQL Server ℹ
Microsoft SQL Server has validation rules for your schema migrations that reject schema changes that introduce *[referential action cycles](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/referential-actions/cyclic-referential-actions)*.
These scenarios tend to show up often for developers using the `referentialActions` preview feature, which will become the default. The database error you get is not really helpful, so to provide a better experience, Prisma now checks for referential cycle actions when it validates your schema file and shows you the exact location of the cycle in your schema.
To learn more, check out the [documentation](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/referential-actions/cyclic-referential-actions).
##### `prisma introspect` is being deprecated in favor of `prisma db pull` 👋🏻
The `prisma introspect` command is an alias for `prisma db pull` so they are the same command. However, `prisma db pull` is more intuitive since it *pulls* the schema from the database into your local `schema.prisma` file. This naming also works as the counterpart of `prisma db push`.
Starting with this release, you will get a warning that encourages you to use `prisma db pull` instead of `prisma introspect`.
##### Prisma Adopts Semantic Versioning (SemVer)
As previously announced, we are adjusting our release policy to adhere more strictly to [Semantic Versioning](https://semver.org/).
In the future, breaking changes in the stable development surface i.e. [General Availability](https://www.prisma.io/docs/about/releases#generally-available-ga) will only be rolled out with major version increments.
You can learn more about the change in the [announcement blog post](https://www.prisma.io/blog/prisma-adopts-semver-strictly).
##### Fixes and improvements
##### Prisma Client
- [Revisit prisma.$queryRaw("...") vs. prisma.$queryRaw template literal](https://togithub.com/prisma/prisma/issues/7142)
- [Queries that include the count of a relation that has multiple foreign keys translates to incorrect SQL](https://togithub.com/prisma/prisma/issues/7299)
- [Order by Relations with multiple references](https://togithub.com/prisma/prisma/issues/7331)
- [Prisma client crashes when counting m-n self-relation](https://togithub.com/prisma/prisma/issues/7807)
- [Prisma crashes when I use the same table for counting and `findUnique`](https://togithub.com/prisma/prisma/issues/7893)
- [Order By Relation with CursorId doesn't return result](https://togithub.com/prisma/prisma/issues/8036)
- [Shows incorrect count number by using selectRelationCount previewFeatures](https://togithub.com/prisma/prisma/issues/8050)
- [JSON number filtering bug](https://togithub.com/prisma/prisma/issues/8224)
- [MDBE: Break down the feature into concrete tasks](https://togithub.com/prisma/prisma/issues/8275)
- [FTS: Integrate into the Prisma Client](https://togithub.com/prisma/prisma/issues/8694)
- [Interactive transactions not working with `$queryRaw` and `$executeRaw` in 2.29.0](https://togithub.com/prisma/prisma/issues/8717)
- [Calling `.catch()` or `.finally()` on a prisma client model query does not fire the request in 2.29.0](https://togithub.com/prisma/prisma/issues/8718)
##### Prisma Migrate
- [CLI: Add deprecation notice to prisma introspect (renamed db pull)](https://togithub.com/prisma/prisma/issues/8078)
- [Add Default Constraint Name to PSL for SqlServer](https://togithub.com/prisma/prisma/issues/8158)
- [The server failed to resume the transaction. Desc:3600000005.](https://togithub.com/prisma/prisma/issues/8394)
- [Add DML validation to reject `Bytes` `@id` columns with SQL Server](https://togithub.com/prisma/prisma/issues/8591)
- [Better error for cyclical referential actions](https://togithub.com/prisma/prisma/issues/8682)
- [Sqlite reserved constraint names cannot be recreated](https://togithub.com/prisma/prisma/issues/8759)
##### Language tools (e.g. VS Code)
- [Autocomplete does not work for arguments after the first one in `@relation()`](https://togithub.com/prisma/language-tools/issues/814)
- [referentialActions: No auto complete for available actions](https://togithub.com/prisma/language-tools/issues/818)
##### [@prisma/engines](https://togithub.com/prisma/engines) npm package
- [Cannot find namespace 'debug' in 2.29.0](https://togithub.com/prisma/engines-wrapper/issues/128)
##### Credits
Huge thanks to [@saintmalik](https://togithub.com/saintmalik) 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"](https://www.youtube.com/watch?v=TUu4h0elhpw\&ab_channel=Prisma) livestream.
The stream takes place [on Youtube](https://www.youtube.com/watch?v=TUu4h0elhpw\&ab_channel=Prisma) on **Thursday, August 26** at **5pm Berlin | 8am San Francisco**.
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
[ ] If you want to rebase/retry this PR, check this box.
This PR contains the following updates:
2.29.1->2.30.02.29.1->2.30.0Release Notes
prisma/prisma
### [`v2.30.0`](https://togithub.com/prisma/prisma/releases/2.30.0) [Compare Source](https://togithub.com/prisma/prisma/compare/2.29.1...2.30.0) Today, we are excited to share the `2.30.0` stable release 🎉 🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v2.30.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.30.0) about the release.** 🌟 ##### New features & improvements ##### Full-Text Search for PostgreSQL is now in Preview 🚀 We're excited to announce that Prisma Client now has [preview support](https://www.prisma.io/docs/about/prisma/releases#preview) for Full-Text Search on PostgreSQL. You can give this a whirl in **2.30.0** by enabling the `fullTextSearch` preview flag: ```prisma datasource db { provider = "postgresql" url = env("DATABASE_URL") } generator client { provider = "prisma-client-js" previewFeatures = ["fullTextSearch"] } model Post { id Int @id @default(autoincrement()) title String @unique body String status Status } enum Status { Draft Published } ``` After you regenerate your client, you'll see a new `search` field on your `String` fields that you can query on. Here are a few examples: ```ts // returns all posts that contain the words cat *or* dog. const result = await prisma.post.findMany({ where: { body: { search: 'cat | dog', }, }, }) // All drafts that contain the words cat *and* dog. const result = await prisma.posts.findMany({ where: { status: "Draft", body: { search: 'cat & dog', }, }, }) ``` You can learn more about how the query format works in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/full-text-search). We would love to know your feedback! If you have any comments or run into any problems we're available in this [in this Github issue](https://togithub.com/prisma/prisma/issues/8877). ##### Validation errors for referential action cycles on Microsoft SQL Server ℹ Microsoft SQL Server has validation rules for your schema migrations that reject schema changes that introduce *[referential action cycles](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/referential-actions/cyclic-referential-actions)*. These scenarios tend to show up often for developers using the `referentialActions` preview feature, which will become the default. The database error you get is not really helpful, so to provide a better experience, Prisma now checks for referential cycle actions when it validates your schema file and shows you the exact location of the cycle in your schema. To learn more, check out the [documentation](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/referential-actions/cyclic-referential-actions). ##### `prisma introspect` is being deprecated in favor of `prisma db pull` 👋🏻 The `prisma introspect` command is an alias for `prisma db pull` so they are the same command. However, `prisma db pull` is more intuitive since it *pulls* the schema from the database into your local `schema.prisma` file. This naming also works as the counterpart of `prisma db push`. Starting with this release, you will get a warning that encourages you to use `prisma db pull` instead of `prisma introspect`. ##### Prisma Adopts Semantic Versioning (SemVer) As previously announced, we are adjusting our release policy to adhere more strictly to [Semantic Versioning](https://semver.org/). In the future, breaking changes in the stable development surface i.e. [General Availability](https://www.prisma.io/docs/about/releases#generally-available-ga) will only be rolled out with major version increments. You can learn more about the change in the [announcement blog post](https://www.prisma.io/blog/prisma-adopts-semver-strictly). ##### Fixes and improvements ##### Prisma Client - [Revisit prisma.$queryRaw("...") vs. prisma.$queryRaw template literal](https://togithub.com/prisma/prisma/issues/7142) - [Queries that include the count of a relation that has multiple foreign keys translates to incorrect SQL](https://togithub.com/prisma/prisma/issues/7299) - [Order by Relations with multiple references](https://togithub.com/prisma/prisma/issues/7331) - [Prisma client crashes when counting m-n self-relation](https://togithub.com/prisma/prisma/issues/7807) - [Prisma crashes when I use the same table for counting and `findUnique`](https://togithub.com/prisma/prisma/issues/7893) - [Order By Relation with CursorId doesn't return result](https://togithub.com/prisma/prisma/issues/8036) - [Shows incorrect count number by using selectRelationCount previewFeatures](https://togithub.com/prisma/prisma/issues/8050) - [JSON number filtering bug](https://togithub.com/prisma/prisma/issues/8224) - [MDBE: Break down the feature into concrete tasks](https://togithub.com/prisma/prisma/issues/8275) - [FTS: Integrate into the Prisma Client](https://togithub.com/prisma/prisma/issues/8694) - [Interactive transactions not working with `$queryRaw` and `$executeRaw` in 2.29.0](https://togithub.com/prisma/prisma/issues/8717) - [Calling `.catch()` or `.finally()` on a prisma client model query does not fire the request in 2.29.0](https://togithub.com/prisma/prisma/issues/8718) ##### Prisma Migrate - [CLI: Add deprecation notice to prisma introspect (renamed db pull)](https://togithub.com/prisma/prisma/issues/8078) - [Add Default Constraint Name to PSL for SqlServer](https://togithub.com/prisma/prisma/issues/8158) - [The server failed to resume the transaction. Desc:3600000005.](https://togithub.com/prisma/prisma/issues/8394) - [Add DML validation to reject `Bytes` `@id` columns with SQL Server](https://togithub.com/prisma/prisma/issues/8591) - [Better error for cyclical referential actions](https://togithub.com/prisma/prisma/issues/8682) - [Sqlite reserved constraint names cannot be recreated](https://togithub.com/prisma/prisma/issues/8759) ##### Language tools (e.g. VS Code) - [Autocomplete does not work for arguments after the first one in `@relation()`](https://togithub.com/prisma/language-tools/issues/814) - [referentialActions: No auto complete for available actions](https://togithub.com/prisma/language-tools/issues/818) ##### [@prisma/engines](https://togithub.com/prisma/engines) npm package - [Cannot find namespace 'debug' in 2.29.0](https://togithub.com/prisma/engines-wrapper/issues/128) ##### Credits Huge thanks to [@saintmalik](https://togithub.com/saintmalik) 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"](https://www.youtube.com/watch?v=TUu4h0elhpw\&ab_channel=Prisma) livestream. The stream takes place [on Youtube](https://www.youtube.com/watch?v=TUu4h0elhpw\&ab_channel=Prisma) on **Thursday, August 26** at **5pm Berlin | 8am San Francisco**.Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by WhiteSource Renovate. View repository job log here.