Prisma

Hey <!everyone> :v: :prisma-cool:

We just released Prisma <https://github.com/prisma/prisma/releases/tag/2.29.0|2.29.0> :prisma-rainbow:

:rocket: *Interactive Transactions are now in Preview*

Today we’re introducing Interactive Transactions – one of our most debated <https://github.com/prisma/prisma/issues/1844|feature requests>.

Interactive Transactions are a double-edged sword. While they allow you to ignore a class of errors that could otherwise occur with concurrent database access, they impose constraints on performance and scalability.

While we believe there are <https://www.prisma.io/blog/how-prisma-supports-transactions-x45s1d5l0ww1|better alternative approaches> we certainly want to ensure people who absolutely need them have the option available.

You can opt-in to Interactive Transactions by setting the `interactiveTransactions` preview feature in your Prisma Schema:

```generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["interactiveTransactions"]
}```
Note that the interactive transactions API does not support controlling isolation levels or locking for now.

You can find out more about implementing use cases with transactions in <https://www.prisma.io/docs/concepts/components/prisma-client/transactions#interactive-transactions|the docs>, and <https://github.com/prisma/prisma/issues/8664|share your feedback>.

:tada: *`namedConstraints` are now in Preview*

So far the Prisma schema could only represent the underlying database names for `@@unique` and `@@index`.
Names for primary keys and foreign keys could not be represented even when the database supported these. This could lead to problems with the names of constraints in different environments getting out of sync and generated migrations therefore failing.

You can opt-in to `namedConstraints` by setting the `namedConstraints` preview feature in your Prisma Schema:

```generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["namedConstraints"]
}```
When using `prisma db pull` these names will now automatically be pulled into your Prisma schema unless they match our default naming convention (which follows the Postgres convention).

Please check our <https://prisma.io/docs/guides/upgrade-guides/upgrading-to-use-preview-features/enabling-named-constraints|upgrade guide> before enabling the preview flag and running migrate operations for the first time.

:books: *Learn more in the release notes*
For more info and links to documentation, you can read the <https://github.com/prisma/prisma/releases/tag/2.29.0|release notes>.

:star2: *Help us spread the word about Prisma* :star2:
To help spread the word about Prisma, we’d very much appreciate if you would star the repo :star2: And if you’re excited about the features in this week’s release, then help us and share your excitement on <https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v2.29.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.29.0|Twitter>.

:newspaper: *Join us on Thursday for the “What’s new in Prisma” livestream*

<@UQT5WQX9S> and I will discuss the latest release and other news from the Prisma ecosystem in a <https://www.youtube.com/watch?v=Dt9uEq1WVvQ|livestream on YouTube> on Thursday at 5pm Berlin | 8am San Francisco.