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"
• Engine freezes all requests/responses in 2.0.0-beta.2
• [Beta.2] Omission of relation field causes unclear rust error message at generate
• Custom type for id
• Document AWS lambda configuration to avoid timeouts
• raw: COALESCE/IFNULL returns MA==
• Upserting Many-To-Many fails with unique index constraint
• Bad cli output
• @relation annotation's field attribute should not be able to accept scalar lists
• I am new to PRISMA /. i am not able to install via NPM .. can some body help ?
• Should we output introspection warnings to stderr when using prisma introspect --print?
• Improve Introspection warnings output for invalid names
• Deprecation wrapper for prisma2 executable
• generate does not work in folders with spaces
• Rename CLI folder
• Remove enum usage from docs where sqlite is used
• Required 1-1-self-relations should be forbidden?

prisma-client-js

• PrismaClientUnknownRequestError - InterpretationError on nested create
• Update Many in self-referencing relations

migrate

• Add ability to define schema path for prisma migrate cli to help output
• --preview is ignored when doing prisma migrate down --preview --experimental
• Migrate allows you to use enums in sqlite even though sqlite doesn't support them

vscode

• Auto formatting is adding fields which were already specified
• Using env variables breaks VS Code plugin formatting funcionality
• Error message shown in wrong location