@prisma/client

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

Highlights

Introspection of Views SQL improvements (Preview)

The views Preview feature significantly improved this release: prisma db pull now reads the SQL query used to define a view and stores it in a .sql file in a views folder next to your Prisma schema.

Note: These .sql files are not yet used for creating or updating views during migrations yet. For now, we are only looking for feedback. Let us know if the introspected SQL files match the views picked up in your database and if the correct files were created in your filesystem.

We encourage you to leave feedback in this GitHub issue.

Improvements to JSON protocol (Early Preview)

In 4.11.0, we announced the jsonProtocol Preview feature which had some rough edges. This release improves the Preview feature by providing polished and helpful error messages from Prisma Client when something goes wrong. Here is an example error message:

We would appreciate it if you would try it out to help us polish the feature and move it to General Availability. Testing it requires little effort. Please also leave any feedback in this issue, or open a new one if you want to report a bug.

Prisma Client startup performance

In this release, we've improved the startup performance of Prisma Client. We're keen on improving the performance of Prisma Client. If you experience any problems with the startup performance, be sure to report them so that we can look into them.

Open Telemetry tracing and logging for Prisma Client for Data Proxy

This release adds support for Open Telemetry tracing (via the tracing Preview feature) and logging to Prisma Client for Data Proxy.

Fixes and improvements

Prisma Migrate

• Certain types of schema changes don't work with CockroachDB v22.2
• Completions: provided by engines break right at the start of a newline
• db pull fail with particular enum default value in column
• Unable to reset CockroachDB for table with foreign key relationship on v22.2.
• Introspection of SQLite views
• Changing the Column Type to Enum on a model throws an error
• Introspection of the view definition statement
• MySQL multi-value index removes the primary key on introspection

Prisma Client

• findUnique used with Promise.all returns null
• Missing PrismaPromise export after update from 4.9.0 to 4.11.0
• jsonProtocol doesn't query enum fields by default
• Prisma 4.11 breaks multilevel relation with compound primary keys (typings)
• 4.11.0: Unique constraint failed on the fields on query that worked in 4.10.1
• jsonProtocol Field/Enum is not included in the result of the findFirst/findMany function
• Too many records are returned in 4.11.0 when using nested include and @unique field is null
• Objects with computed properties returned from an extended prisma client return true for any property name when calling hasOwn or hasOwnProperty on it

Language tools (e.g. VS Code)

• Completions: suggest type block for MongoDB
• Remove datasource completions

Credits

Huge thanks to @KhooHaoYit, @rintaun, @ivan, @art049 for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, March 30 at 5 pm Berlin | 8 am San Francisco.