2.25.0

[Jolg42]

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

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

Major improvements & new features

Human-readable drift diagnostics for prisma migrate dev

Database schema drift occurs when your database schema is out of sync with your migration history, i.e. the database schema has drifted away from the source of truth.

With this release, we improve the way how the drift is printed to the console when detected in the prisma migrate dev command. While this is the only command that uses this notation in today's release, we plan to use it in other places where it would be useful for debugging in the future.

Here is an example of how the drift is presented with the new format:

[*] Changed the `Color` enum
  [+] Added variant `TRANSPARENT`
  [-] Removed variant `RED`

[*] Changed the `Cat` table
  [-] Removed column `color`
  [+] Added column `vaccinated`

[*] Changed the `Dog` table
  [-] Dropped the primary key on columns (id)
  [-] Removed column `name`
  [+] Added column `weight`
  [*] Altered column `isGoodDog` (arity changed from Nullable to Required, default changed from `None` to `Some(Value(Boolean(true)))`)
  [+] Added unique index on columns (weight)

Expand to view the resulting Prisma schema

This file is generated to prisma/schema.prisma:

// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

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

generator client {
  provider = "prisma-client-js"
}

Support for .env files in Prisma Client Go

You can now use a .env file with Prisma Client Go. This makes it easier to keep database credentials outside your Prisma schema and potentially work with multiple clients at the same time:

example/
├── .env
├── main.go
└── schema.prisma

Learn more about using the .env file in our documentation.

Breaking change

Dropping support for Node.js v10

Node.js v10 reached End of Life on April 30th 2021. Many of our dependencies have already dropped support for Node.js v10 so staying up-to-date requires us to drop Node.js v10, too.

We recommend upgrading to Node.js v14 or greater for long-term support. You can learn more about Node.js releases on this page.

Fixes and improvements

Prisma Client

• [Errors] New common error from malformed connection string
• Failed to run future: no available capacity / QueueFull
• Clean up middleware implementation
• Possible Node API performance regression with concurrency
• Dropping Node v10 support (LTS reached EndOfLife)
• Performance regression with napi for high concurrency
• In 2.24.0 createMany errors with: PANIC in query-engine/connectors/sql-query-connector/src/database/operations/write.rs:95:60called Result::unwrap()on anErr value: ScalarFieldNotFound { name: "updated_at", model: "FundMangerTeamMemberExperience" }
• test: snapshot params in Middleware tests
• Running prisma generate doesn't install prisma client 2.24.x
• Middleware + $transactions do not play well together
• Environment variable not found

Prisma Migrate

• Feature request - Migrate: When Drift Detected -> give more Details than just the rollback script
• Error: [introspection-engine\connectors\sql-introspection-connector\src\introspection_helpers.rs:188:64] called Option::unwrap() on a None value
• Generate log file with Drift detected info for troubleshooting purpose
• db push / migrate is hiding the binary download process during generate, leading to confusion
• Shadow vs. main database check does not consider the port
• Re-Introspection removes shadowDatabaseUrl from schema

Prisma Studio

• Prisma Studio not working with napi preview feature
• Crash in simple datasource only schema
• Prisma studio requires having prisma client installed when it shouldn't

Credits

Huge thanks to @82600417, @SuryaElavazhagan, @psavan1655 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" livestream.

The stream takes place on Youtube on Thursday, June 17 at 5pm Berlin | 8am San Francisco.

🌎 Prisma Day is coming

Save the date for Prisma Day 2021 and join us for two days of talks and workshops by the most exciting members of the Prisma community.

• June 29th: Workshops
• June 30th: Talks

We look forward to seeing you there!

---

This discussion was created from the release 2.25.0.

[willdoescode]

Swag

[psavan1655]

We'll be getting swags for the contribution? 😅

[Mehak-Mehta]

mega swag

[Linux249]

Hey,
found "prisma client doesn't work with serverless-next.js" in the change log under "Fixes and improvements". I think this is misleading. The issue is "solved" cause there is a workaround described inside the issue to solve the problem -> ok.
But reading your change log suggests to me that the problem would no longer exist when upgrading to 2.25.0 ... or is it me reading it wrong in general?

[janpio]

Good point, I removed that issue from the list. The list of issues in a mile stone is auto generated, so sometimes things we just close etc slip through and make it into this list.

We would of course prefer to fully support this, but seems that is not easily possible in this case - so we should at least document it properly to make it more discoverable. If you are still having this problem and the workaround does not work (or you do not want to use it), feel free to open a new issue with a good description so we can take another look.

[Linux249]

Thanks for clarifying - it's a case that only appears when deploying a NextJs + Prisma app with serverless-nextjs to AWS so imho the serverless-nextjs team should mention the workaround in their docs too - will draw their attention to it.
Btw this ticket has the same topic #6032 ;)

[ludralph]

Hi there,

To keep our discussions organized and focused on the most relevant topics, we’re reviewing and tidying up our backlog. As part of this process, we’re closing discussions that haven’t had any recent activity and appear to be outdated.

If this discussion is still important to you or unresolved, we’d love to hear from you! Feel free to reopen it or start a new one with updated details.

For more details about our priorities and vision for the future of Prisma ORM, check out our latest blog post: https://www.prisma.io/blog/prisma-orm-manifesto.

Thank you for your understanding and being part of the community!