@prisma/instrumentation

4.16: (MongoDB) Generated types for list composites are incorrect

Getting wrong types with prisma client extensions

Prisma Client fluent API does not work with extends anymore on 4.16.1

Prisma Client Extensions: $allModels: { $allOperations } sets query type to never

Result types are incorrectly inferred when undefined explicitly passed to select/include

Field references are not available on extended clients

4.16.x cannot wrap $extend in factory function when compilerOptions.composite is true

Prisma Schema Type inside a Type not generating a right Payload

Query in findMany in prisma extends returns a wrong type

4.16.0 Count query is not returning the right type when in a transaction

FindMany returns wrong type after extending prisma client

Can't specify $queryRawUnsafe return type after extending prisma client

Prisma Client extensions

Ordering by nulls first and last

Count by filtered relation

Result extensions components: add custom fields and methods to query result objects, for example, virtual/computed fields.

Seeding different data in different environments

Partially seeding data in some tables

The downloaded Query Engine doesn’t match the runtime/ target platform your application is running on.

The Query Engine is not copied to your final application bundle during the build step.

PostgreSQL extensions

Extended where unique

Field reference support

Order by Nulls

Partitioned tables

PostgreSQL Row Level Security

Index sort order, NULLS FIRST / NULLS LAST

CockroachDB row-level TTL

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.