6.3.0
Today, we are excited to share the 6.3.0
stable release 🎉
🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟
Highlights
A brand new Prisma Studio
In this release we've included several great improvements to Prisma Studio's developer experience. You can learn all about the changes we've made in our release blog post, but here's a short list:
Prisma Studio is back in the Console
Fans of Prisma Data Browser rejoice! The new Prisma Studio is now in the Prisma Console and is available for all PostgreSQL and MySQL databases.
A new model viewer
Previously, switching from model to model in Prisma Studio would require backing all the way out to the model view, then digging in again. With our new UI, it's easy to switch from model to model while keeping your place.
A new editing experience
If you're trying to edit a given field in a model, Prisma Studio made it quite easy. However, if you're trying to edit every field in a given row, it could get quite annoying to keep scrolling left to right. Our new edit sidebar resolves that with the ability to edit all fields for a given row at once.
Clean up at the click of a button
When editing a number of models, it can get difficult to get back to a clean slate. In the new Prisma Studio, we've added a "Close all" button that puts you back to a fresh start.
Add limit
to updateMany()
and deleteMany()
Previously, limit
has not existed as a valid option in top level updateMany()
and deleteMany()
queries. In 6.3.0 limit
is now available in these queries, bringing their features more in line with other query types.
You can use limit
like the following:
await prisma.user.deleteMany({
where: { column: 'value' },
limit: 100,
});
This will limit the number of deleted users to 100 at maximum.
Sort generator
fields deterministically
In previous version of Prisma ORM, the fields inside of a generator
block in your Prisma Schema were not deterministically sorted. This could lead to cases where prisma db pull
could lead to re-ordering of fields.
In 6.3.0, the sorting of fields in this block is now deterministic. You may see re-ordering on the first prisma db pull
after you upgrade, but it will remain consistent afterwards.
Replace NOT IN
with NOT EXISTS
for PostgreSQL relation filters
In previous versions of Prisma ORM, when using the none
or some
relation filters, the SQL queries generated used NOT IN
. In many cases this lead to performance issues as the size of the related table grew. In 6.3.0, we’ve replaced these usages of IN
with EXISTS
in order to improve query performance.
A special thank you
We'd like to extend our heartfelt thanks to @loren and his team for the collaboration and trust in our enterprise support plan. Working closely with them allowed us to address important issues like #19249 and #17303. Their insights and partnership have been invaluable in improving our product.
If your team could benefit from dedicated support and tailored solutions, learn more about our enterprise support plan.
Fixes and improvements
Prisma Client
Prisma
- Prisma interactive transaction ignores DB exception on commit (with triggers)
prisma db pull
non-deterministically sorts generator fieldsno entry found for key
error on views<->model relations- Adding
onUpdate
data to the DMMF in@prisma/generator-helper
Credits
Huge thanks to @WhyAsh5114 for their contributions to this release!