如何修复AI生成的无效Prisma关系

AI代理生成的Prisma schema关系缺少反向关系、错误的引用操作或字段类型不匹配，导致prisma validate和prisma migrate失败。

AI代理编写的Prisma schema关系看起来正确，但由于缺少反向引用、类型不匹配或多关系设置不明确，导致prisma validate失败。

症状

一个关系在一个模型上声明，但在另一个模型上没有对应的必需部分，或者外键字段类型与引用的字段不匹配。

// schema.prisma — WRONG
model User {
  id    String @id @default(cuid())
  posts Post[]
}

model Post {
  id       String @id @default(cuid())
  authorId Int    // Int, but User.id is String — type mismatch
  // Missing: author User @relation(fields: [authorId], references: [id])
}

运行prisma validate会产生：

Error: The relation field `posts` on model `User` is missing an opposite
relation field on the model `Post`.

发生原因

AI代理经常只写关系的一边而忘记添加另一边，尤其是在多对多或自引用的情况下。它还会从记忆中复制字段类型，而不检查authorId是否必须与引用的id类型完全匹配。

如何发现

prisma validate或prisma migrate dev失败并出现关系错误。
一个模型有数组字段（一对多），但引用的模型没有标量外键或@relation属性。
多对多使用了类型不匹配的显式连接表。
自引用模型（例如类别树）只有@relation(name: "...")对的一边。

如何修复

每个关系必须声明两边。外键标量类型必须与引用的字段类型完全匹配。

// schema.prisma — CORRECT
model User {
  id    String @id @default(cuid())
  posts Post[] // one-to-many: back-reference
}

model Post {
  id       String @id @default(cuid())
  authorId String                       // String, matches User.id
  author   User   @relation(fields: [authorId], references: [id], onDelete: Cascade)
}

对于自引用树：

model Category {
  id       String     @id @default(cuid())
  parentId String?
  parent   Category?  @relation("CategoryTree", fields: [parentId], references: [id])
  children Category[] @relation("CategoryTree")
}

[ ] Run "prisma validate" before "prisma migrate dev" — fix all errors first
[ ] Every @relation on model A has a matching field on model B
[ ] Foreign key scalar type matches the referenced @id type (String/Int/cuid)
[ ] Self-referential relations use a named @relation("name") on both sides
[ ] Explicit many-to-many join tables declare both foreign keys with onDelete
[ ] onDelete referential action is explicit (Cascade, Restrict, SetNull) — not left to default

修复提示

This Prisma schema fails prisma validate. Fix every relation error: add the
missing back-reference fields, ensure all foreign key scalar types exactly match
the referenced @id type, give every self-referential relation a unique name on
both sides, and set explicit onDelete actions (Cascade for required relations,
SetNull for optional). Run prisma validate after each change until it passes.

测试

# Validate schema before attempting migration
npx prisma validate && echo "Schema OK" || echo "FAIL: schema invalid"

# Also check for type mismatches (Int fk -> String id is a common error)
grep -A3 "@relation" prisma/schema.prisma

如何修复AI生成的无效Prisma关系

症状

发生原因

如何发现

如何修复

修复提示

测试

相关