Type conflict when naming a table {something} and a second table {something}Result

[doflo-dfa]

Bug description

There is now a conflict when naming a table {something} and a second table {something}Result

in our case we had Credentials and CredentialsResult both of which referenced each other.

The client generation will create a typescript files that has two conflicting type interfaces named the same thing

How to reproduce

name a table {something} and a second table {something}Result

Expected behavior

That the client generation would namespace the types or that the docs would mark Result as a reserved word not to be used in the table names

Prisma information

// Add your schema.prisma
model Credential {
  id          String                @id @default(cuid())
  createdAt   DateTime              @default(now())
  updatedAt   DateTime              @updatedAt
  namespaceId String
  development Boolean?
  system      Boolean?              @default(false)
  Namespace   Namespace             @relation(fields: [namespaceId], references: [id])
  Team        Team?                 @relation(fields: [teamId], references: [id])
  User        User?                 @relation(fields: [userId], references: [id])
  results     CredentialResult[] 
  Elements    Element[]             @relation("selectedCredential")
}

model CredentialResult {
  id           String     @id @default(cuid())
  createdAt    DateTime   @default(now())
  updatedAt    DateTime   @updatedAt
  pass         Boolean
  credentialId String
  Credential   Credential @relation(fields: [credentialId], references: [id])
}

// Add your code using Prisma Client

Environment & setup

• OS: macOS
• Database: PostgreSQL
• Node.js version: v16.15.1

Prisma Version

prisma                  : 4.8.0
@prisma/client          : 4.8.0
Current platform        : darwin
Query Engine (Node-API) : libquery-engine d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/prisma/node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine        : migration-engine-cli d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/prisma/node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/prisma/node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/prisma/node_modules/@prisma/engines/prisma-fmt-darwin)
Format Wasm             : @prisma/prisma-fmt-wasm 4.8.0-61.d6e67a83f971b175a593ccc12e15c4a757f93ffe
Default Engines Hash    : d6e67a83f971b175a593ccc12e15c4a757f93ffe
Studio                  : 0.479.0
Preview Features        : filterJson

[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.