Prisma

Today, we are excited to share the `2.10.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%20Prisma%20release%202.10.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.10.0) about the release.**

Major improvements

This release introduces some major new features in Preview!

Support for Microsoft SQL Server (Preview)

With this release, we're introducing support for a new database: **Microsoft SQL Server** 🥳

You can start using your MS SQL Server databases today with **introspection** and query them with **Prisma Client**. Note that Prisma Migrate does _not_ support MS SQL Server yet.

An MS SQL Server database is specified in your Prisma schema via the new `sqlserver` connector. Note that while it's in _Preview_, you also need to add the additional `previewFeature` flag `microsoftSqlServer` in the generator for Prisma Client:

prisma
datasource db {
provider = "sqlserver"
}

generator client {
provider = "prisma-client-js"
previewFeatures = ["microsoftSqlServer"]
}


You can find a ready-to-run example based on MS SQL Server [here](https://github.com/prisma/prisma-examples/tree/latest/databases/sql-server).

Please [share your feedback](https://github.com/prisma/prisma/issues/4039) on how this feature works for you. We are interested in both positive and negative feedback, so we know whether this feature is already ready for production! (If you encounter any problems, please open a new issue [here](https://github.com/prisma/prisma/issues/new/choose)).

📚 **Documentation**: [Microsoft SQL Server connector](https://www.prisma.io/docs/reference/tools-and-interfaces/preview-features/sql-server)

Single-command schema changes for prototyping (Preview)

With this release, we are introducing a new command that lets you _push_ the state of your Prisma schema file to the database without using migrations: `prisma db push --preview-feature`

`push` is the first command that's introduced under the new `prisma db` namespace. The `prisma db` namespace will be used for commands that operate _directly_ against the database without e.g., saving or manipulating a migration history on your file system nor in the migrations table. It's therefore well-suited for **prototyping and local development** environments. In production environments, you'll want to be able to track and replay the changes made to your database which will be handled by the `prisma migrate` namespace.

The idea behind `prisma db push` is that you only care about the _end state_ of your database schema, but not about _how_ this end state is achieved.

Also note that the command runs `prisma generate` for you, so you're saving an extra step after having updated your Prisma schema!

Please [share your feedback](https://github.com/prisma/prisma/issues/4058) on how this feature works for you. We are interested in both positive and negative feedback, so we know whether this feature is already ready for production! (If you encounter any problems, please open a new issue [here](https://github.com/prisma/prisma/issues/new/choose)).

📚 **Documentation**: [`db push` command](https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-cli/command-reference#db-push)

Atomic number operations are now stable

In `2.6.0` we introduced case atomic number operations in Preview, in today's release we're promoting this feature to stable. This means you don't need to include the `atomicNumberOperations` feature flag in the Prisma Client generator any more:


diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["atomicNumberOperations"]
}


📚 **Documentation**: [Atomic operations on `update`](https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-client/crud/#atomic-operations-on-update)

Already existing preview features from previous releases

Just a quick reminder:

- In version [`2.1.0`](https://github.com/prisma/prisma/releases/tag/2.1.0) we introduced two preview features, namely `connectOrCreate` and `transactionApi`.

In case they're useful for you, please give them a try and [share your feedback](https://github.com/prisma/prisma/issues/3108)! These features remain in preview in this release.


🎃 Join the first Prisma Meetup online

We are excited to bring you the first [**Prisma Meetup**](https://www.youtube.com/watch?v=SepT_whwFsA) which is going to happen entirely online, so you can dial in from around the globe!

It will be streamed on Youtube this Thursday: **October 29th, 2020** at **6pm (CET, Berlin) | 10am (PDT, San Francisco)**

We have amazing speakers on board for our first Meetup:

◭ [Tammy Butow](https://tammybutow.com/) (Principal SRE [Gremlin](https://www.gremlin.com/customers/)): Database Horror Stories
◭ [Hervé Labas](https://twitter.com/hervelabas) (VP of Product [Prisma](https://www.prisma.io)): The future of Prisma and its roadmap
◭ [Tom Hutchinson](https://twitter.com/tomhut) (Head of Mobile [Rapha](https://www.rapha.cc/eu/en/)): Prisma at Rapha

You can watch the event on YouTube [here](https://www.youtube.com/watch?v=SepT_whwFsA).

Fixes and improvements

[`prisma`](https://github.com/prisma/prisma)

- [Graceful shutdown](https://github.com/prisma/prisma/issues/2917)
- [Use `.executeRaw()` with `.transaction([])`](https://github.com/prisma/prisma/issues/3150)
- [Report the database version in the migrate/introspection error reports](https://github.com/prisma/prisma/issues/3486)
- [connectOrCreate fails during upsert](https://github.com/prisma/prisma/issues/3612)
- [$connect doesn't actually connect, the first query does](https://github.com/prisma/prisma/issues/3649)
- [Log when a connection to the database is opened](https://github.com/prisma/prisma/issues/3702)
- [Allow .env in the project root with the Prisma Schema somewhere else](https://github.com/prisma/prisma/issues/3720)
- [process.on('SIGINT') callback not being called when I import prisma/client](https://github.com/prisma/prisma/issues/3773)
- [Send sql schema description with the introspection error reports](https://github.com/prisma/prisma/issues/3779)
- [Feature request: Allow `$queryRaw` and `$executeRaw` in transactions](https://github.com/prisma/prisma/issues/3828)
- [Support SQL Server in `executeRaw` and `queryRaw`](https://github.com/prisma/prisma/issues/3861)
- [Introduce stand-alone integration test package](https://github.com/prisma/prisma/issues/3864)
- [Separate test helpers into separate folder structure](https://github.com/prisma/prisma/issues/3878)
- [Stabilize `atomicNumberOperations`](https://github.com/prisma/prisma/issues/3917)
- [Introduce `prisma/engines` package](https://github.com/prisma/prisma/issues/3928)
- [Integration tests with SQL Server](https://github.com/prisma/prisma/issues/3932)
- [undefined is printed at the top of prisma/clidev](https://github.com/prisma/prisma/issues/4007)

[`prisma-client-js`](https://github.com/prisma/prisma-client-js)

- [ISO Dates with an offset is not working](https://github.com/prisma/prisma-client-js/issues/741)
- [PANIC: called `Result::unwrap()` on an `Err` value: Error("EOF while parsing a value", line: 1, column: 0)](https://github.com/prisma/prisma-client-js/issues/831)


[`migrate`](https://github.com/prisma/migrate)

- [[PostgreSQL] migrating column from jsonb[] to jsonb fails](https://github.com/prisma/migrate/issues/506)
- [Migration fails when attempting to change the column type in the absence of a working cast](https://github.com/prisma/migrate/issues/545)
- [Error: Error in migration engine. Reason: [libs\sql-schema-describer\src\postgres.rs:159:20] querying for columns: Error { kind: QueryError(Error { kind: Closed, cause: None }), original_code: None, original_message: Some("connection closed") } ](https://github.com/prisma/migrate/issues/606)


[`language-tools`](https://github.com/prisma/language-tools)

- [Warn about provider array deprecation in the VSCode plugin](https://github.com/prisma/language-tools/issues/522)
- [prisma-language-server cannot be ran as command](https://github.com/prisma/language-tools/issues/566)
- [LSP: Can't rename if the server getting position that is not the end of word.](https://github.com/prisma/language-tools/issues/576)
- [LSP: Please do best effort when the lsp-client doesn't support context option.](https://github.com/prisma/language-tools/issues/578)
- [Json should also show squiggly lines for MSSQL](https://github.com/prisma/language-tools/issues/591)


[`studio`](https://github.com/prisma/studio)

- [Studio enforces optional fields to be filled](https://github.com/prisma/studio/issues/551)
- [Reordering a column also sorts by that column](https://github.com/prisma/studio/issues/565)
- [Studio swallows all feature flags inside the `generator` block](https://github.com/prisma/studio/issues/568)


[`prisma-engines`](https://github.com/prisma/prisma-engines)

- [Query Engine: Native Types](https://github.com/prisma/prisma-engines/issues/73)
- [Introspection Engine: Native Types](https://github.com/prisma/prisma-engines/issues/74)
- [Native Types: Add support for non integer arguments](https://github.com/prisma/prisma-engines/issues/1145)
- [Proper parsing of JDBC connection strings](https://github.com/prisma/prisma-engines/issues/1155)
- [Composite key ordering in SQL Server](https://github.com/prisma/prisma-engines/issues/1209)
- [Do not use magic partial indices with SQL Server](https://github.com/prisma/prisma-engines/issues/1220)
- [Gate SQL Server from Migration Engine](https://github.com/prisma/prisma-engines/issues/1222)
- [Validator should disallow native type Text in combination with unique attribute for MySQL](https://github.com/prisma/prisma-engines/issues/1227)
- [Remove duplication in Introspection Engine tests](https://github.com/prisma/prisma-engines/issues/1236)
- [Move all preview feature flags into the generator block](https://github.com/prisma/prisma-engines/issues/1237)
- [Research: Understand compatibility of native types with PSL features](https://github.com/prisma/prisma-engines/issues/1246)
- [remove validation for optional 1:1 relations in MSSQL ](https://github.com/prisma/prisma-engines/issues/1278)
- [Remove ScalarType `Xml`](https://github.com/prisma/prisma-engines/issues/1283)
- [Implement default mapping for new scalar type `Decimal`](https://github.com/prisma/prisma-engines/issues/1285)
- [Implement default mapping for the scalar types `Bytes`](https://github.com/prisma/prisma-engines/issues/1286)

Today, we are excited to share the `2.9.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%20Prisma%20release%202.9.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.9.0) about the release.**

Improvements

In today's release, we have many bug fixes, increased test coverage, and improved error messages. The release also lays the foundations for the upcoming native database types support.

Errors thrown by Prisma Client include the version

With this release, error objects thrown by Prisma Client include the `clientVersion` field which contains the version of Prisma Client. This is useful for debugging and creating issues.

Improved error message of `prisma.$transaction`

When you use `prisma.$transaction` to group multiple calls into a single transaction, you need to pass an array of promises. Passing calls that have been awaited will now trigger a more helpful error:


Error: All elements of the array need to be Prisma Client promises. Hint: Please make sure you are not awaiting the Prisma client calls you intended to pass in the $transaction function.


Already existing preview features from previous releases

Just a quick reminder:

- In version [`2.6.0`](https://github.com/prisma/prisma/releases/tag/2.6.0) we introduced one preview feature, namely `atomicNumberOperations`.
- In version [`2.1.0`](https://github.com/prisma/prisma/releases/tag/2.1.0) we introduced two preview features, namely `connectOrCreate` and `transactionApi`.

In case they're useful for you, please give them a try and [share your feedback](https://github.com/prisma/prisma/issues/3108)! These features remain in preview in this release.

Issues closed with the release

[`prisma`](https://github.com/prisma/prisma)

- [Switch to stable actions/stale once my PR is merged](https://github.com/prisma/prisma/issues/3112)
- [`We can't release, as the e2e tests are not passing for the ${tag} npm tag!` checks wrong npm tag for passing e2e tests when promoting a patch-dev to latest](https://github.com/prisma/prisma/issues/3369)
- [Client seems to ignore Custom Binary Specification](https://github.com/prisma/prisma/issues/3499)
- [Tests / GitHub Actions check why cached download test is really slow](https://github.com/prisma/prisma/issues/3553)
- [Merge `PrismaQueryEngineError` into `PrismaClientUnknownRequestError`](https://github.com/prisma/prisma/issues/3570)
- [Incorrect SQL generated for Json field { equals: null } filter](https://github.com/prisma/prisma/issues/3579)
- [Any Client error message should include the Client version](https://github.com/prisma/prisma/issues/3662)
- [`prisma -v` should include Client version as well (if installed)](https://github.com/prisma/prisma/issues/3663)
- [\$executeRaw used in a transaction throws: All elements of the array need to be Prisma Client promises.](https://github.com/prisma/prisma/issues/3677)
- [Test forks](https://github.com/prisma/prisma/issues/3685)
- [Code coverage](https://github.com/prisma/prisma/issues/3722)
- [Consolidate integration tests](https://github.com/prisma/prisma/issues/3723)
- [Include possible block names on a wrong keyword](https://github.com/prisma/prisma/issues/3741)
- [Optional field is required in unique and where clause and doesn't accept null](https://github.com/prisma/prisma/issues/3772)
- [`prisma introspect` overwrites a 1:1 mapping as 1:many](https://github.com/prisma/prisma/issues/3775)
- [Replace ncc with esbuild in cli](https://github.com/prisma/prisma/issues/3778)
- [cli/introspect tests should exit](https://github.com/prisma/prisma/issues/3787)
- [Implement env var `FORCE_PANIC_INTROSPECTION_ENGINE`](https://github.com/prisma/prisma/issues/3788)
- [DMMF Enum value types are invalid in 2.8.0](https://github.com/prisma/prisma/issues/3804)
- [`findFirst` should have return type `Model | null`](https://github.com/prisma/prisma/issues/3863)
- [Unexpected field not found (FieldNotFound) error](https://github.com/prisma/prisma/issues/3866)
- [Non unique index should not appear in findOne where clause](https://github.com/prisma/prisma/issues/3869)

[`prisma-client-js`](https://github.com/prisma/prisma-client-js)

- [PostgreSQL `<table>WhereUniqueInput` including a column which isn't unique when composite primary key is used](https://github.com/prisma/prisma-client-js/issues/711)
- [Improve error message when object is passed to `prisma.$transaction` instead of a Prisma promise](https://github.com/prisma/prisma-client-js/issues/846)
- [Export `Sql` from prisma/client](https://github.com/prisma/prisma-client-js/issues/858)
- [Prisma and node 12.19.0](https://github.com/prisma/prisma-client-js/issues/907)

[`language-tools`](https://github.com/prisma/language-tools)

- [Quick fixes for typos in block names](https://github.com/prisma/language-tools/issues/483)
- [Include reason of publish CI in every workflow and slack notification](https://github.com/prisma/language-tools/issues/484)
- [Autocomplete stops showing after the first character](https://github.com/prisma/language-tools/issues/489)
- [Changing the datasource name doesn't break the schema](https://github.com/prisma/language-tools/issues/490)
- [Can we check for the presence of the other extension and disable one or warn the user clearly](https://github.com/prisma/language-tools/issues/491)
- [extract the possible keywords from prisma-fmt error message](https://github.com/prisma/language-tools/issues/520)
- [Remove vsce from renovate ignore list](https://github.com/prisma/language-tools/issues/532)
- [VS Code extension not formatting for v2.8.1](https://github.com/prisma/language-tools/issues/539)
- [Get preview features from prisma-fmt](https://github.com/prisma/language-tools/issues/543)
- [Enum default() autocomplete putting comments as options](https://github.com/prisma/language-tools/issues/547)

[`studio`](https://github.com/prisma/studio)

- [Navigating from relations table triggered `Error: Could not find appropriate InputType for this field type. This should never happen.`](https://github.com/prisma/studio/issues/554)
- [t.toUpperCase is not a function - prisma 2.8.0](https://github.com/prisma/studio/issues/556)
- [Studio doesn't let me save the newly created record](https://github.com/prisma/studio/issues/560)
- [Studio sometimes gets stuck on `Saving Changes`](https://github.com/prisma/studio/issues/562)

[`prisma-engines`](https://github.com/prisma/prisma-engines)

- [Supporting SQL Server in Introspection Engine](https://github.com/prisma/prisma-engines/issues/814)
- [Datamodel validator capability to prevent a foreign key on pointing to a nullable field](https://github.com/prisma/prisma-engines/issues/1123)
- [Remove explicit attached name from generated SQL on SQLite](https://github.com/prisma/prisma-engines/issues/1129)
- [Remove explicit database name from generated SQL on MySQL](https://github.com/prisma/prisma-engines/issues/1130)
- [Schema Parser should validate supplied feature flags](https://github.com/prisma/prisma-engines/issues/1154)
- [`default()` does not work in conjunction with native types](https://github.com/prisma/prisma-engines/issues/1160)
- [Postgres: serial native type and `default(autoincrement())` must not be possible at the same time](https://github.com/prisma/prisma-engines/issues/1161)
- [Implement a `debugPanic` RPC in introspection engine](https://github.com/prisma/prisma-engines/issues/1171)
- [Add arguments to Mysql native type TINYINT](https://github.com/prisma/prisma-engines/issues/1182)
- [Schema validation rejects fields with native type TinyInt and Scalar Type Boolen](https://github.com/prisma/prisma-engines/issues/1192)

Credits

Huge thanks to rahul3v for helping!

Interested in providing feedback for the upcoming version of Prisma Migrate?

We are seeking users interested in trying out upcoming versions of Prisma Migrate. This will involve trying it out, validating functionality, and sharing feedback with us.

If you're interested in participating, [fill out the following form](https://prisma103696.typeform.com/to/yssOzU8F), it won't take longer than a minute!


🎃 Join the first Prisma Meetup online

We are excited to bring you the first [**Prisma Meetup**](https://www.youtube.com/watch?v=SepT_whwFsA) which is going to happen entirely online, so you can dial in from around the globe!

The Meetup will be streamed on Youtube this Thursday: **October 29th, 2020** at **6pm (CET, Berlin) | 10am (PDT, San Francisco)**

We have amazing speakers on board for our first Meetup:

◭ [Tammy Butow](https://tammybutow.com/) (Principal SRE [Gremlin](https://www.gremlin.com/customers/)): Database Horror Stories
◭ [Hervé Labas](https://twitter.com/hervelabas) (VP of Product [Prisma](https://www.prisma.io)): The future of Prisma and its roadmap
◭ [Tom Hutchinson](https://twitter.com/tomhut) (Head of Mobile [Rapha](https://www.rapha.cc/eu/en/)): Prisma at Rapha

You can watch the event on YouTube [here](https://www.youtube.com/watch?v=SepT_whwFsA).

Today, we are issuing the `2.8.1` patch release.

Fixes

Prisma Client
- [DMMF Enum value types are invalid in 2.8.0 3804](https://github.com/prisma/prisma/issues/3804)
- [findFirst` should have return type `Model | null 3863](https://github.com/prisma/prisma/issues/3863)

Studio
- [Studio doesn't let me save the newly created record 560](https://github.com/prisma/studio/issues/560)
- [t.toUpperCase is not a function - prisma 2.8.0 556](https://github.com/prisma/studio/issues/556)
- [Navigating from relations table triggered `Error: Could not find appropriate InputType for this field type. This should never happen.` 554](https://github.com/prisma/studio/issues/554)

Today, we are excited to share the `2.8.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%20Prisma%20release%202.8.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.8.0) about the release.**

Major improvements

In today's release, we have two new features coming for you!

`findFirst`

While the `findMany` API gives you a powerful API to query your database with different [filters](https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-client/filtering), it's not ideal if you just want to query _a single item_.

On the other hand, the `findOne` API returns single items, but it only allows for filtering by _unique_ fields.

In version `2.8.0`, we introduce `findFirst` - giving you the full power of `findMany` filters while only returning the first item that matches the filter criteria.

So instead of this:

ts
const usersCalledAlice = await prisma.user.findMany({
name: "Alice"
})
const firstUserCalledAlice = usersCalledAlice[0]


You can now do this:

ts
const firstUserCalledAlice = await prisma.user.findFirst({
name: "Alice"
})


All filters available for `findMany` are also available in `findFirst`.


Case insensitive filters for PostgreSQL are now stable

In `2.5.0` we introduced case insensitive filters for PostgreSQL, in today's release we're promoting this feature to stable. This means you don't need to include the `insensitiveFilters` feature flag in the Prisma Client generator any more:


diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["insensitiveFilters"]
}


The new `mode` option you can pass to `findMany` influences the corresponding filter (e.g. `contains` or `startsWith`) but doesn't change the return type of the `findMany` query. `mode` can have two possible values:

- `default`: Uses the default filter configured on the database level. If the collation is configured as case insensitive in the database, the default mode will be case insensitive as well. In that case, there's no need to use the `insensitive` mode.
- `insensitive`: Uses the case insensitive filter (if possible).

ts
const result = await prisma.user.findMany({
where: {
email: {
equals: 'lowercaseUPPERCASE.com',
mode: 'insensitive',
},
},
})


Note that this feature will not work if you're using database collations that do not know how to convert between upper- and lowercase letters (e.g. the `C` collation).

📚 **Documentation**: [Case sensitivity](https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-client/case-sensitivity) / [Case-sensitive filtering](https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-client/filtering#case-insensitive-filtering)


Already existing preview features from previous releases

Just a quick reminder:

- In version [`2.6.0`](https://github.com/prisma/prisma/releases/tag/2.6.0) we introduced one preview feature, namely `atomicNumberOperations`.
- In version [`2.1.0`](https://github.com/prisma/prisma/releases/tag/2.1.0) we introduced two preview features, namely `connectOrCreate` and `transactionApi`.

In case they're useful for you, please give them a try and [share your feedback](https://github.com/prisma/prisma/issues/3108)! These features remain in preview in this release.

Fixes and improvements

[`prisma`](https://github.com/prisma/prisma)

- [Output prepared GitHub issue creation link after reporting error (CLI)](https://github.com/prisma/prisma/issues/2588)
- [Prisma Format should enforce opinionation for order of attributes](https://github.com/prisma/prisma/issues/3269)
- [Cursor Pagination not returning expected results](https://github.com/prisma/prisma/issues/3505)
- [Warn about syntax error in datasource url (with env var) earlier](https://github.com/prisma/prisma/issues/3509)
- [Allow setting scalar lists without `set`](https://github.com/prisma/prisma/issues/3529)
- [Investigate live reload of Prisma Client with `next dev`](https://github.com/prisma/prisma/issues/3615)
- [Output path of schema.prisma file in CLI commands that read it](https://github.com/prisma/prisma/issues/3647)
- [Environment variable to trigger crash/panic in Engines](https://github.com/prisma/prisma/issues/3648)
- [Unable to connect when connection string contains $](https://github.com/prisma/prisma/issues/3669)
- [Implement a `findFirst` API](https://github.com/prisma/prisma/issues/3676)


[`prisma-client-js`](https://github.com/prisma/prisma-client-js)

- [Running into an issue with the connectOrCreate operation. The following query should create an entity for a Winery, and assign a Tag to it.](https://github.com/prisma/prisma-client-js/issues/764)
- [Integration Tests, Errors: Writing a signed Int to an unsigned column](https://github.com/prisma/prisma-client-js/issues/820)
- [ErrorFormat 'colorless' doesn't work](https://github.com/prisma/prisma-client-js/issues/885)


[`language-tools`](https://github.com/prisma/language-tools)

- [Add option to set the `prisma-fmt` binary path in vscode options](https://github.com/prisma/language-tools/issues/235)
- [Warn about syntax error in datasource url (with env var) earlier 3509](https://github.com/prisma/language-tools/issues/448)
- [Slack notifications for failing workflows](https://github.com/prisma/language-tools/issues/471)
- [Quick Fix adding native Types preview Feature when using native types](https://github.com/prisma/language-tools/issues/472)
- [Extension panic because of comments](https://github.com/prisma/language-tools/issues/473)
- [Move e2e tests for published extension in this repo instead of in vscode-e2e-tests](https://github.com/prisma/language-tools/issues/477)
- [Prisma extension formatting failure and freeze after upgrade 2.7.1 and VS v1.49.1](https://github.com/prisma/language-tools/issues/481)
- [Add number of CI step in visible name of workflow](https://github.com/prisma/language-tools/issues/486)


[`studio`](https://github.com/prisma/studio)

- [Can't filter by null values](https://github.com/prisma/studio/issues/549)
- [Show *why* a table cell is invalid](https://github.com/prisma/studio/issues/550)
- [Improve error modals](https://github.com/prisma/studio/issues/552)


[`prisma-engines`](https://github.com/prisma/prisma-engines)

- [Add tests using Cockroach DB ](https://github.com/prisma/prisma-engines/issues/900)
- [Add tests using Yugabyte DB](https://github.com/prisma/prisma-engines/issues/901)
- [Add test cases for the DMMF command](https://github.com/prisma/prisma-engines/issues/1048)
- [Query Engine: Investigate how we could support union types](https://github.com/prisma/prisma-engines/issues/1088)
- [After upload: Download binary builds from S3 again and verify expected checksum](https://github.com/prisma/prisma-engines/issues/1104)
- [Incorrect error message on missing native Type previewFeature](https://github.com/prisma/prisma-engines/issues/1127)

❓ Are you using Prisma at work?

We'd love to know if you're using Prisma at work. Answer with a quick **yes** or **no** in our [poll](https://prisma103696.typeform.com/to/sXYraQzA), it won't take longer than a few seconds!

Credits

Huge thanks to nohns for some great contributions in this release!

Today, we are issuing the `2.7.1` patch release.

Fixes

Prisma Client JS
- [Unable to connect when connection string contains $ 3669](https://github.com/prisma/prisma/issues/3669)

Prisma Studio
- [Optional relations show up as invalid when you try to create a new record 546](https://github.com/prisma/studio/issues/546)

Today we are excited to share the `2.7.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%20Prisma%20release%202.7.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.7.0) about the release.**

Major improvements

Prisma Studio is stable 🎉

We are more than excited to share that Prisma Studio has moved out of its experimental state and is promoted to stable with today's release! Prisma Studio is the perfect companion for developers who work with databases in their daily workflows, to quickly get an overview of the state of their database as well as to view and modify the data in it. An announcement blog post will be coming soon!

To use Prisma Studio in your Prisma project, you can now run the `prisma studio` command without the previously required `--experimental` flag:


npx prisma studio


Join the [prisma-studio](https://app.slack.com/client/T0MQBS8JG/C01ACF1DJ1M) channel in the [Prisma Slack](https://slack.prisma.io/) and let us know how you like Prisma Studio! 🙌

Configure Prisma schema location via `package.json` for more flexibility

Previously, your `schema.prisma` file needed to be available at a specific location when running Prisma CLI commands or provided via the `--schema` option when invoking a Prisma CLI command.

With this release, you can configure the location of your Prisma schema via a `prisma` property in your `package.json`:

json
{
"prisma": {
"schema": "path/to/schema.prisma"
}
}


The provided location in `package.json` will be the default location of the Prisma schema file for any Prisma CLI command you invoke. Note that you can still override this default location by manually specifying the `--schema` option when invoking a Prisma CLI command.

📚 **Documentation:** [Prisma schema file location](https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-schema#prisma-schema-file-location)

Already existing preview features from previous releases

Just a quick reminder:

- In version [`2.6.0`](https://github.com/prisma/prisma/releases/tag/2.6.0) we introduced one preview feature, namely `atomicNumberOperations`.
- In version [`2.5.0`](https://github.com/prisma/prisma/releases/tag/2.5.0) we introduced one preview feature, namely `insensitiveFilters`.
- In version [`2.1.0`](https://github.com/prisma/prisma/releases/tag/2.1.0) we introduced two preview features, namely `connectOrCreate` and `transactionApi`.

In case they're useful for you, please give them a try and [share your feedback](https://github.com/prisma/prisma/issues/3108)! These features remain in preview in this release.

Feedback wanted: How does introspection work for you?

In the last few releases we improved Prisma's database introspection, most notably with ["More robust introspection by keeping manual changes in the Prisma schema file"](https://github.com/prisma/prisma/releases/tag/2.6.0) but also many smaller bug fixes. We think it is pretty stable now, and would love to hear from you, our users, how you have been using prisma introspect recently!

If you have used introspection in the past, whether it worked well or not so well with your database, [**please let us know**](https://github.com/prisma/prisma/issues/3659) by sharing your feedback on GitHub!


🌟 Help us spread the word about Prisma

To help spread the word about Prisma, we'd very much appreciate if you would **star this repo** 🌟 And if you're excited about the features in this week's release, then help us and [share it on Twitter](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20Prisma%20release%202.7.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.7.0).

Fixes and improvements

[`prisma`](https://github.com/prisma/prisma)

- [Add ability to configure custom schema location instead of requiring `--schema` arg](https://github.com/prisma/prisma/issues/3144)
- [Running `prisma init` with unknown parameter just outputs `null`](https://github.com/prisma/prisma/issues/3172)
- [Use dotenv-expand instead of dotenv package to allow variable expressions in the env file](https://github.com/prisma/prisma/issues/3310)
- [Update denylist in engines and client](https://github.com/prisma/prisma/issues/3338)
- [Engine panics when schema.prisma is empty, we could make it an error.](https://github.com/prisma/prisma/issues/3376)
- [Schema parser errors shouldn't be reported to error reporting](https://github.com/prisma/prisma/issues/3377)
- [Loss of precision on Float fields with many digits](https://github.com/prisma/prisma/issues/3479)
- [2.6.0 Broke some of my update queries](https://github.com/prisma/prisma/issues/3497)
- [Log Prisma client version being generated](https://github.com/prisma/prisma/issues/3500)
- [Broken `set` on nested update on 2.6.0](https://github.com/prisma/prisma/issues/3503)
- [Multiple many-many relationships appears to cause an introspection failure.](https://github.com/prisma/prisma/issues/3507)
- [Query validation error updating Date field](https://github.com/prisma/prisma/issues/3512)
- [Error: [libs/datamodel/core/src/dml/model.rs:166:14] We assume an internally valid datamodel before mutating. ](https://github.com/prisma/prisma/issues/3516)
- [While using PM2 on a prisma related project popus up prisma client cmd terminal on windows ](https://github.com/prisma/prisma/issues/3521)
- [Separate command and GH action workflow to run integration tests ](https://github.com/prisma/prisma/issues/3524)
- [The `introspect` command in v2.6.x does not remember `cuid()` defaults for a field and user-defined relation `name` property](https://github.com/prisma/prisma/issues/3526)
- [Do not run GitHub Action Workflows on fork of example repository](https://github.com/prisma/prisma/issues/3539)
- [Do not build binaries for FreeBSD 12 any more](https://github.com/prisma/prisma/issues/3558)
- [`introspect --force` does not work](https://github.com/prisma/prisma/issues/3591)


[`prisma-client-js`](https://github.com/prisma/prisma-client-js)

- [PANIC: invalid or out-of-range date](https://github.com/prisma/prisma-client-js/issues/849)
- [aggregateApi and sum returns null if no record](https://github.com/prisma/prisma-client-js/issues/855)


[`migrate`](https://github.com/prisma/migrate)

- [Unable to run prisma migrate with dotenv-cli](https://github.com/prisma/migrate/issues/570)
- [Error when running initial migration with a schema in DATABASE_URL](https://github.com/prisma/migrate/issues/572)


[`language-tools`](https://github.com/prisma/language-tools)

- [Add vsix bundle to releases](https://github.com/prisma/language-tools/issues/366)
- [Create a local release with .vsix file and publish from that](https://github.com/prisma/language-tools/issues/408)
- [E2E tests run on every PR should use local LSP](https://github.com/prisma/language-tools/issues/440)
- [Abnormal CPU usage](https://github.com/prisma/language-tools/issues/447)
- [Change of `client/index.d.ts` should not show a notification](https://github.com/prisma/language-tools/issues/451)
- [This version is built from commit undefined. This is for Prisma CLI ...](https://github.com/prisma/language-tools/issues/457)
- [Reorganize READMEs](https://github.com/prisma/language-tools/issues/458)


[`studio`](https://github.com/prisma/studio)

- [Stuck at "Getting things ready" when Studio is open in multiple places](https://github.com/prisma/studio/issues/454)
- [Filtering issue (not/equals/contains/startsWith) when "" empty string field Value ](https://github.com/prisma/studio/issues/528)
- [Error when opening certain relations](https://github.com/prisma/studio/issues/530)
- [Tab dirtyness should be cancelled out when it is returned to its original state](https://github.com/prisma/studio/issues/531)
- [Cannot edit a relation that is `null`](https://github.com/prisma/studio/issues/532)
- [Allow typing in partial dates in table cells](https://github.com/prisma/studio/issues/534)
- [Allow typing in partial dates in filters](https://github.com/prisma/studio/issues/535)
- [Very slow to load for large Postgres schemas](https://github.com/prisma/studio/issues/536)
- [When changing a relation, the scalar that constitutes it does not change](https://github.com/prisma/studio/issues/538)
- [Unable to change relations & relation lists in an uncommitted record](https://github.com/prisma/studio/issues/539)
- [If you type in an arbitrary id in a scalar that is part of a relation, `Save Changes` will always fail](https://github.com/prisma/studio/issues/540)
- [Oopsies: filter UI is broken](https://github.com/prisma/studio/issues/543)
- [Deleting a model with unsaved changes open in a tab might result in a fatal error](https://github.com/prisma/studio/issues/545)


[`prisma-engines`](https://github.com/prisma/prisma-engines)

- [Improve error for nonexistent column in SQLite](https://github.com/prisma/prisma-engines/issues/874)
- [Native types: allow specifying unsigned integer types on MySQL](https://github.com/prisma/prisma-engines/issues/1068)
- [Validate that prisma enums have at least one variant/value](https://github.com/prisma/prisma-engines/issues/1070)
- [Parser must error if native types are used but feature flag is not enabled](https://github.com/prisma/prisma-engines/issues/1085)
- [Trigger binary builds via square brackets in commit message](https://github.com/prisma/prisma-engines/issues/1103)

Credits

Huge thanks to bre7, rahul3v, jasonkuhrt and Weakky for helping!