(Prisma 5) fix: nullable to one relation filter input (BREAKING)

[Weakky]

⚠️ DO NOT MERGE BEFORE PRISMA 5

Overview

• fixes <Model>RelationFilterInput does not take nullability into account prisma#18585

DMMF changes

Given the following datamodel:

model User {
  id Int @id

  addressId Int     @unique
  address   Address @relation(fields: [addressId], references: [id])

  post Post[]
}

model Address {
  id Int @id

  user User?
}

model Post {
  id Int @id

  userId Int
  user   User @relation(fields: [userId], references: [id])
}

It changes DMMF in the following ways:

input UserRelationFilter {
  is: UserWhereInput
  isNot: UserWhereInput
}

+input UserNullableRelationFilter {
+  is: UserWhereInput | Null
+  isNot: UserWhereInput | Null
+}

input AddressWhereInput {
  AND: AddressWhereInput | [AddressWhereInput]
  OR: [AddressWhereInput]
  NOT: AddressWhereInput | [AddressWhereInput]
  id: IntFilter | Int
- user: UserRelationFilter | UserWhereInput
+ user: UserNullableRelationFilter | UserWhereInput
}

input AddressWhereUniqueInput {
  id: Int
  AND: AddressWhereInput | [AddressWhereInput]
  OR: [AddressWhereInput]
  NOT: AddressWhereInput | [AddressWhereInput]
-  user: UserRelationFilter | UserWhereInput
+  user: UserNullableRelationFilter | UserWhereInput
}

input PostWhereInput {
  AND: PostWhereInput | [PostWhereInput]
  OR: [PostWhereInput]
  NOT: PostWhereInput | [PostWhereInput]
  id: IntFilter | Int
  userId: IntFilter | Int
  user: UserRelationFilter | UserWhereInput
}

[codspeed-hq]

CodSpeed Performance Report

Merging #3969 prisma5/fix-to-one-nullable-input (a638144) will not alter performances.

Summary

🔥 0 improvements
❌ 0 regressions
✅ 11 untouched benchmarks

🆕 0 new benchmarks
⁉️ 0 dropped benchmarks

[Jolg42]

Note: someone will need to resolve the merge conflicts

[Druue]

lgtm 🌸