Prisma

Latest version: v0.15.0

Safety actively analyzes 710445 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 31 of 44

2.0.0beta.3

Today, we are issuing the third Beta release: 2.0.0-beta.3 (short: beta.3).

Major changes
- Enums are now disallowed for SQLite
- Required 1-1 self relations are forbidden now
- The `prisma2` command is now deprecated in favor of `prisma`


Fixes and improvements

`prisma`

- [Introspection Regression "Error validating: The argument `references` must refer to a unique criteria in the related model `pages_language`. But it is referencing the following fields that are not a unique criteria: page_id"](https://github.com/prisma/prisma/issues/2182)
- [Engine freezes all requests/responses in 2.0.0-beta.2](https://github.com/prisma/prisma/issues/2143)
- [[Beta.2] Omission of relation field causes unclear rust error message at generate](https://github.com/prisma/prisma/issues/2139)
- [Custom type for id](https://github.com/prisma/prisma/issues/2137)
- [Document AWS lambda configuration to avoid timeouts](https://github.com/prisma/prisma/issues/2121)
- [raw: COALESCE/IFNULL returns `MA==`](https://github.com/prisma/prisma/issues/2107)
- [Upserting Many-To-Many fails with unique index constraint](https://github.com/prisma/prisma/issues/2094)
- [Bad cli output](https://github.com/prisma/prisma/issues/2081)
- [`relation` annotation's `field` attribute should not be able to accept scalar lists](https://github.com/prisma/prisma/issues/2065)
- [I am new to PRISMA /. i am not able to install via NPM .. can some body help ?](https://github.com/prisma/prisma/issues/2041)
- [Should we output introspection warnings to stderr when using `prisma introspect --print`?](https://github.com/prisma/prisma/issues/2038)
- [Improve Introspection warnings output for invalid names](https://github.com/prisma/prisma/issues/2036)
- [Deprecation wrapper for `prisma2` executable](https://github.com/prisma/prisma/issues/2010)
- [`generate` does not work in folders with spaces](https://github.com/prisma/prisma/issues/1973)
- [Rename CLI folder](https://github.com/prisma/prisma/issues/1953)
- [Remove enum usage from docs where sqlite is used](https://github.com/prisma/prisma/issues/1906)
- [Required 1-1-self-relations should be forbidden?](https://github.com/prisma/prisma/issues/1895)


`prisma-client-js`

- [PrismaClientUnknownRequestError - InterpretationError on nested create](https://github.com/prisma/prisma-client-js/issues/605)
- [Update Many in self-referencing relations](https://github.com/prisma/prisma-client-js/issues/589)


`migrate`

- [Add ability to define schema path for prisma migrate cli to help output](https://github.com/prisma/migrate/issues/419)
- [`--preview` is ignored when doing `prisma migrate down --preview --experimental`](https://github.com/prisma/migrate/issues/402)
- [Migrate allows you to use enums in sqlite even though sqlite doesn't support them](https://github.com/prisma/migrate/issues/377)


`vscode`

- [Auto formatting is adding fields which were already specified](https://github.com/prisma/vscode/issues/98)
- [Using env variables breaks VS Code plugin formatting funcionality](https://github.com/prisma/vscode/issues/92)
- [Error message shown in wrong location](https://github.com/prisma/vscode/issues/85)

2.0.0beta.2

Today, we are issuing the second Beta release: `2.0.0-beta.2` (short: `beta.2`).

> We want to give a huge shoutout to [Sytten](https://github.com/Sytten) who [helped us fix some issues](https://github.com/prisma/prisma-engines/pull/630) in the Rust codebase 🎊

Major improvements

Parametrized `count` queries in Prisma Client

In previous versions of Prisma Client, it was [not possible to provide any filter arguments when using `.count`](https://github.com/prisma/prisma-client-js/issues/252). With this release, you can provide the same filter arguments from `findMany`:

ts
const numberOfUsersCalledBob = await prisma.user.count({ where: { name: 'Bob' }})


Lots of bug fixes and improvements

With this release, we were able to fix a lot of nasty bugs like some schema validation issues in VS Code ([1989](https://github.com/prisma/prisma/issues/1989) and [#1970](https://github.com/prisma/prisma/issues/1970)) as well as a Prisma Migrate [bug with 1-n self-relations](https://github.com/prisma/migrate/issues/405).

Fixes and improvements per Prisma 2.0 repository

`prisma`

- [Provide log output when `.env` file is used - Closes 1155](https://github.com/prisma/prisma/issues/2134)
- [Add MariaDB integration tests closes 1791](https://github.com/prisma/prisma/issues/2124)
- [Fix "because" typo in README](https://github.com/prisma/prisma/issues/2078)
- [Add a --json flag to `version` command](https://github.com/prisma/prisma/issues/2071)
- [Running prisma version fails](https://github.com/prisma/prisma/issues/2070)
- [Schemas with incomplete relation annotations should be rejected during Client generation](https://github.com/prisma/prisma/issues/2064)
- [Fix `prisma2 generate --watch` exits when no models are defined in schema.prisma](https://github.com/prisma/prisma/issues/2056)
- [Fix link to Prisma documentation](https://github.com/prisma/prisma/issues/2028)
- [fix typo in README](https://github.com/prisma/prisma/issues/2024)
- [Fix "Getting started" links](https://github.com/prisma/prisma/issues/2022)
- [Prisma generate script throws error](https://github.com/prisma/prisma/issues/2049)
- [Running a built binary fails with weird error](https://github.com/prisma/prisma/issues/2017)
- [Validation error message for schema with missing relation scalar field (old syntax)](https://github.com/prisma/prisma/issues/1989)
- [Validation Error: error: Error validating: The relation field `Teams` uses the scalar fields tmID. The arity of those fields must be the same. The relation field is required but the scalar fields are optional.](https://github.com/prisma/prisma/issues/1970)
- [Add integration test for introspection warnings](https://github.com/prisma/prisma/issues/1969)
- [Error format for enum field declaration broken](https://github.com/prisma/prisma/issues/1968)
- [Error format for missing type on field is broken](https://github.com/prisma/prisma/issues/1967)
- [Error when disconnecting m:n relation with string-id-model](https://github.com/prisma/prisma/issues/1930)
- [Getting error on deeper includes](https://github.com/prisma/prisma/issues/1785)
- [ENV-based binary variables broken on preview022](https://github.com/prisma/prisma/issues/1722)
- [Proposal: Rename prisma binary to query-engine](https://github.com/prisma/prisma/issues/1920)
- [`prisma2 generate --watch` exits when no models are defined in schema.prisma](https://github.com/prisma/prisma/issues/1592)
- [Provide log output when `.env` file is used](https://github.com/prisma/prisma/issues/1155)


`prisma-client-js`

- [adjust README](https://github.com/prisma/prisma-client-js/issues/634)
- [Fix a typo in the generated docs](https://github.com/prisma/prisma-client-js/issues/630)
- [Error message "Error: Query engine binary for current platform "..." could not be found" could list other file from that directory to help debugging](https://github.com/prisma/prisma-client-js/issues/625)
- [Fix batching. Closes 562](https://github.com/prisma/prisma-client-js/issues/624)
- [Invalid include query results in unexpected output](https://github.com/prisma/prisma-client-js/issues/608)
- [Query batching sends queries with different selection set](https://github.com/prisma/prisma-client-js/issues/562)
- [Super long output on error in `create`](https://github.com/prisma/prisma-client-js/issues/533)


`prisma-engines`

- [Adapt test-cli to new query engine binary name](https://github.com/prisma/prisma-engines/issues/659)
- [Unify duplicated test assertion code paths](https://github.com/prisma/prisma-engines/issues/658)
- [Remove Unused Dependencies](https://github.com/prisma/prisma-engines/issues/655)
- [Upgrade quaint and adjust tests after mysql floats fix](https://github.com/prisma/prisma-engines/issues/654)
- [Fix Self Relation Rendering](https://github.com/prisma/prisma-engines/issues/653)
- [Minor opportunistic simplifications in sql schema calculator](https://github.com/prisma/prisma-engines/issues/652)
- [Fix detection of 1:1 relations for self-relations](https://github.com/prisma/prisma-engines/issues/651)
- [Datamodel parser/relation arguments validation](https://github.com/prisma/prisma-engines/issues/650)
- [Downgrade tokio to 0.2.13](https://github.com/prisma/prisma-engines/issues/648)
- [Fix for unexpected additional records during deeply nested reads.](https://github.com/prisma/prisma-engines/issues/647)
- [Bug: subquery has too many columns](https://github.com/prisma/prisma-engines/issues/646)
- [Update crates (incl. faster tokio)](https://github.com/prisma/prisma-engines/issues/645)
- [cargo fmt](https://github.com/prisma/prisma-engines/issues/644)
- [adapt arity validation for relation fields to match introspection logic](https://github.com/prisma/prisma-engines/issues/643)
- [Datamodel Parser: allow dbgenerated function for enum fields](https://github.com/prisma/prisma-engines/issues/642)
- [add readonly flag to dmmf field](https://github.com/prisma/prisma-engines/issues/641)
- [Drop relations that are referring to unsupported types](https://github.com/prisma/prisma-engines/issues/640)
- [Add dmmf subcommand to test-cli](https://github.com/prisma/prisma-engines/issues/633)
- [Ignore env errors when reformatting](https://github.com/prisma/prisma-engines/issues/630)
- [Test column types with dubious nullability properties (pg/mysql)](https://github.com/prisma/prisma-engines/issues/625)
- [improve relation validations](https://github.com/prisma/prisma-engines/issues/624)
- [prisma-fmt formatting regression](https://github.com/prisma/prisma-engines/issues/620)
- [Add support for newline in the source and generator blocks](https://github.com/prisma/prisma-engines/issues/615)
- [Investigate weirdness around nullability of timestamp fields](https://github.com/prisma/prisma-engines/issues/594)
- [Proposal: Tighten datamodel parser rules for relation](https://github.com/prisma/prisma-engines/issues/568)
- [Reenable error code and message assertions in scala tests](https://github.com/prisma/prisma-engines/issues/486)


`migrate`

- [Fix broken bug_report ISSUE_TEMPLATE markup](https://github.com/prisma/migrate/issues/394)
- [Prisma CLI cannot revert a migration](https://github.com/prisma/migrate/issues/393)

2.0.0beta.1

npm install prisma/client2.0.0-beta.1
npm install prisma/cli2.0.0-beta.1 --save-dev


Without touching the database, one way to adjust your Prisma schema to adhere to the new syntax would be as follows:

diff
model User {
id Int id default(autoincrement())
profile Profile?
}

model Profile {
id Int id default(autoincrement())
user User relation(fields: [userId], references: [id])
+ userId Int map("user") // relation scalar field (used in the `relation` attribute above)
}

model Post {
id Int id default(autoincrement())
author User relation(fields: [authorId], references: [id])
+ authorId Int map("author") // relation scalar field (used in the `relation` attribute above)
}


In this code, you introduced the `userId` and `authorId` fields on `Profile` and `Post`. These fields are your _relation scalar fields_ and represent the foreign key in your database. But because the current foreign keys in the database are called `user` and `author` and therefore don't map directly to the model fields, you need to annotate the fields with [`map`](https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-schema/data-model#mapping-column,-table-and-enum-names) to "map" them to a differently named database column.

You can then re-generate Prisma Client. Note that the `prisma2` command has been renamed to `prisma` in `2.0.0-beta.1`, so you need to invoke the `generate` command as follows:


npx prisma generate


Note that the new relation scalar field is currently _read-only_ in the generated Prisma Client API. To modify the connections in youe database, you can keep using Prisma Client's [nested write queries](https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-client/relation-queries#nested-writes).


Breaking changes

No more Preview releases

With this release the Preview period for Prisma 2.0 ends. This means that releases will not be tagged `preview` any more, but with `beta`. Today's release is called: **`2.0.0-beta.1`**.

Restructuring GitHub repositories

Since its initial release, the main repository for Prisma 2.0 has been called `prisma2`.

Because Prisma 2.0 is now the default for developers getting started with Prisma, the Prisma repositories have been renamed as follows:

- The `prisma/prisma2` repository has been renamed to [`prisma/prisma`](https://github.com/prisma/prisma/)
- The `prisma/prisma` repository has been renamed to [`prisma/prisma1`](https://github.com/prisma/prisma1/)

Renaming the `prisma2` CLI

During the Preview period, the CLI for Prisma 2.0 was invoked using the `prisma2` command. With Prisma 2.0 being the default for new developers getting started with Prisma, the command is changed to just `prisma`. The exising `prisma` command of Prisma 1 is renamed to `prisma1`.

Also note that the installation of the npm packages changes:

| Prisma version | Old CLI command | New CLI command | Old npm package name | New npm package name |
| :------------- | :-------------- | :-------------- | :------------------- | :------------------- |

0.38.0

Upgrades Prisma to v5.16 & minor updates

Adds support for [multi file Prisma schema](https://www.prisma.io/docs/orm/prisma-schema/overview/location#multi-file-prisma-schema)

Major changes

* chore(prisma): upgrade prisma to v5.16.0 (1307) steebchen
* test(schema): test multi-schema (1310) steebchen

Changes

* chore(publish-cli): switch to macos-14 (1265) steebchen
* chore(publish-cli): retry latest release command (1273) steebchen
* chore(prisma): upgrade prisma to v5.14.0 (1276) steebchen
* chore(publish-cli): fail if latest version could never be found (1279) steebchen
* chore(docs): remove vercel analytics (1280) steebchen
* chore(docs): add vercel speed insights (1281) steebchen
* chore(prisma): upgrade prisma to v5.15.0 (1288) steebchen
* chore(cli): authenticate GH API request via GitHub token (1290) steebchen
* chore(cli): fix publish-latest script (1294) steebchen
* chore(prisma): upgrade prisma to v5.15.1 (1301) steebchen
* chore(prisma): upgrade prisma to v5.16.0 (1307) steebchen
* fix(generator): adapt env var warning formatting (1291) mattn

Contributors

mattn and steebchen

----

**Full Changelog**: https://github.com/steebchen/prisma-client-go/compare/v0.37.0...v0.38.0

0.37.0

[Add .Select() and .Omit().](https://goprisma.org/docs/walkthrough/fields) Omitted fields will default to their zero value.
Upgrades prisma to v5.13.0.

Major changes

* feat(builder): add omit option (1250) steebchen
* feat(builder): add select option (1252) steebchen

Changes

* chore(prisma): upgrade prisma to v5.12.1 (1234) steebchen
* ci(integration): use macos-12 (1248) steebchen
* chore(prisma): upgrade prisma to v5.13.0 (1247) steebchen
* chore(deps): upgrade go to 1.21 (1251) steebchen
* docs(fields): add select & omit docs (1253) steebchen

Contributors

steebchen

----

**Full Changelog**: https://github.com/steebchen/prisma-client-go/compare/v0.36.0...v0.37.0

0.36.0

Page 31 of 44

Links

Releases

Has known vulnerabilities

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.