include not working on models ending with ...Update with unique compound index

[dfillion]

Bug description

include typing does not work on model with a name ending by ...Update when querying with a unique compound index.

How to reproduce

Use the following Prisma schema:

model User {
  id         String       @id @default(uuid())
  userUpdate UserUpdate[]

  @@map("user")
}

model UserUpdate {
  id       String @id @default(uuid())
  tenantId String @map("tenant_id")
  user     User   @relation(fields: [userId], references: [id])
  userId   String

  @@unique([id, tenantId])
  @@map("user_update")
}

Use findUniqueOrThrow to query the user_update table using the unique compound index id_tenantId:

  const { user } = await prismaClient.userUpdate.findUniqueOrThrow({
    where: { id_tenantId: { id: 'user_id', tenantId: 'tenant_id' } },
    include: { user: true }
  });

We have the following Typescript error: TS2339: Property 'user' does not exist on type 'UserUpdate'.

If we use the unique index id, everything works fine:

  const { user } = await prismaClient.userUpdate.findUniqueOrThrow({
    where: { id: 'user_id' },
    include: { user: true }
  });

If we rename the model so it doesn't end with Update, everything works fine:

model User {
  id         String           @id @default(uuid())
  userUpdate UserUpdateTest[]

  @@map("user")
}

model UserUpdateTest {
  id       String @id @default(uuid())
  tenantId String @map("tenant_id")
  user     User   @relation(fields: [userId], references: [id])
  userId   String

  @@unique([id, tenantId])
  @@map("user_update")
}

  const { user } = await prismaClient.userUpdateTest.findUniqueOrThrow({
    where: { id_tenantId: { id: 'user_id', tenantId: 'tenant_id' } },
    include: { user: true }
  });

Expected behavior

When using include on a model with a name ending with ...Update and querying with a compound unique index, generated type includes the relation.

Prisma information

Same information linked in bug description:

model User {
  id         String       @id @default(uuid())
  userUpdate UserUpdate[]

  @@map("user")
}

model UserUpdate {
  id       String @id @default(uuid())
  tenantId String @map("tenant_id")
  user     User   @relation(fields: [userId], references: [id])
  userId   String

  @@unique([id, tenantId])
  @@map("user_update")
}

  const { user } = await prismaClient.userUpdate.findUniqueOrThrow({
    where: { id_tenantId: { id: 'user_id', tenantId: 'tenant_id' } },
    include: { user: true }
  });

Environment & setup

• OS: macOS
• Database: PostgreSQL
• Node.js version: v18.15.0

Prisma Version

"@prisma/client": "4.13.0",
"prisma": "4.13.0",

[SevInf]

This issue is now fixed and the fix will be published as a part of 5.1 release. If you'd like to verify fix earlier, you can use dev snapshot 5.1.0-dev.24. We don't recommend using it in production, but it should be enough to verify the fix.