跳到主要内容

SQL Server 和 MongoDB 中引用操作的特殊规则

如果你正在使用引用操作,需要考虑一些数据库的特殊要求。

  • 如果关系链导致循环或多级级联路径,Microsoft SQL Server 不允许对外键执行级联引用操作。如果外键上的引用操作设置为 NO ACTION 之外的值(如果 Prisma ORM 管理引用完整性,则为 NoAction),服务器将检查循环或多级级联路径,并在执行 SQL 时返回错误。

  • 对于 MongoDB,在 Prisma ORM 中使用引用操作要求对于任何具有自引用关系或三个模型之间存在循环的数据模型,必须设置 NoAction 的引用操作以防止引用操作模拟无限循环。请注意,默认情况下,MongoDB 使用 relationMode = "prisma" 模式,这意味着 Prisma ORM 管理引用完整性

考虑到 SQL

CREATE TABLE [dbo].[Employee] (
[id] INT NOT NULL IDENTITY(1,1),
[managerId] INT,
CONSTRAINT [PK__Employee__id] PRIMARY KEY ([id])
);

ALTER TABLE [dbo].[Employee]
ADD CONSTRAINT [FK__Employee__managerId]
FOREIGN KEY ([managerId]) REFERENCES [dbo].[Employee]([id])
ON DELETE CASCADE ON UPDATE CASCADE;

运行 SQL 时,数据库将抛出以下错误

Introducing FOREIGN KEY constraint 'FK__Employee__managerId' on table 'Employee' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.

在更复杂的数据模型中,查找级联路径可能会变得复杂。因此,在 Prisma ORM 中,数据模型会在生成任何 SQL 并在迁移过程中运行 之前 进行验证,突出显示作为路径一部分的关系。这使得查找和断开这些操作链变得更加容易。

自引用关系(SQL Server 和 MongoDB)

以下模型描述了一个自引用关系,其中 Employee 可以有经理 (manager) 和下属 (managees),引用同一模型的条目。

model Employee {
id Int @id @default(autoincrement())
manager Employee? @relation(name: "management", fields: [managerId], references: [id])
managees Employee[] @relation(name: "management")
managerId Int?
}

这将导致以下错误

Error parsing attribute "@relation": A self-relation must have `onDelete` and `onUpdate` referential actions set to `NoAction` in one of the @relation attributes. (Implicit default `onDelete`: `SetNull`, and `onUpdate`: `Cascade`)

如果未定义任何操作,Prisma ORM 将根据底层标量字段是可选还是必选来使用以下默认值。

子句所有标量字段都是可选的至少一个标量字段是必选的
onDeleteSetNullNoAction
onUpdateCascadeCascade

由于上述关系中 onUpdate 的默认引用操作是 Cascade,而 onDelete 的默认引用操作是 SetNull,这会创建一个循环,解决方案是显式地将 onUpdateonDelete 的值设置为 NoAction

model Employee {
id Int @id @default(autoincrement())
manager Employee @relation(name: "management", fields: [managerId], references: [id])
manager Employee @relation(name: "management", fields: [managerId], references: [id], onDelete: NoAction, onUpdate: NoAction)
managees Employee[] @relation(name: "management")
managerId Int
}

三个表之间的循环关系(SQL Server 和 MongoDB)

以下模型描述了 ChickenEggFox 之间的循环关系,其中每个模型都引用另一个模型。

model Chicken {
id Int @id @default(autoincrement())
egg Egg @relation(fields: [eggId], references: [id])
eggId Int
predators Fox[]
}

model Egg {
id Int @id @default(autoincrement())
predator Fox @relation(fields: [predatorId], references: [id])
predatorId Int
parents Chicken[]
}

model Fox {
id Int @id @default(autoincrement())
meal Chicken @relation(fields: [mealId], references: [id])
mealId Int
foodStore Egg[]
}

这将导致作为循环一部分的每个关系字段出现三个验证错误。

第一个在 Chicken 模型中的 egg 关系字段中

Error parsing attribute "@relation": Reference causes a cycle. One of the @relation attributes in this cycle must have `onDelete` and `onUpdate` referential actions set to `NoAction`. Cycle path: Chicken.egg → Egg.predator → Fox.meal. (Implicit default `onUpdate`: `Cascade`)

第二个在 Egg 模型中的 predator 关系字段中

Error parsing attribute "@relation": Reference causes a cycle. One of the @relation attributes in this cycle must have `onDelete` and `onUpdate` referential actions set to `NoAction`. Cycle path: Egg.predator → Fox.meal → Chicken.egg. (Implicit default `onUpdate`: `Cascade`)

第三个在 Fox 模型中的 meal 关系字段中

Error parsing attribute "@relation": Reference causes a cycle. One of the @relation attributes in this cycle must have `onDelete` and `onUpdate` referential actions set to `NoAction`. Cycle path: Fox.meal → Chicken.egg → Egg.predator. (Implicit default `onUpdate`: `Cascade`)

由于关系字段是必选的,onDelete 的默认引用操作是 NoAction,但 onUpdateCascade,这会导致引用操作循环。解决方案是将任意一个关系中的 onUpdate 值设置为 NoAction

model Chicken {
id Int @id @default(autoincrement())
egg Egg @relation(fields: [eggId], references: [id])
egg Egg @relation(fields: [eggId], references: [id], onUpdate: NoAction)
eggId Int
predators Fox[]
}

model Egg {
id Int @id @default(autoincrement())
predator Fox @relation(fields: [predatorId], references: [id])
predator Fox @relation(fields: [predatorId], references: [id], onUpdate: NoAction)
predatorId Int
parents Chicken[]
}

model Fox {
id Int @id @default(autoincrement())
meal Chicken @relation(fields: [mealId], references: [id])
meal Chicken @relation(fields: [mealId], references: [id], onUpdate: NoAction)
mealId Int
foodStore Egg[]
}

两个模型之间的多级级联路径(仅限 SQL Server)

数据模型描述了同一模型之间的两条不同路径,并且两个关系都触发级联引用操作。

model User {
id Int @id @default(autoincrement())
comments Comment[]
posts Post[]
}

model Post {
id Int @id @default(autoincrement())
authorId Int
author User @relation(fields: [authorId], references: [id])
comments Comment[]
}

model Comment {
id Int @id @default(autoincrement())
writtenById Int
postId Int
writtenBy User @relation(fields: [writtenById], references: [id])
post Post @relation(fields: [postId], references: [id])
}

此数据模型的问题在于 CommentUser 有两条路径,以及两个关系中的默认 onUpdate 操作都是 Cascade。这导致两个验证错误

第一个在 writtenBy 关系中

Error parsing attribute "@relation": When any of the records in model `User` is updated or deleted, the referential actions on the relations cascade to model `Comment` through multiple paths. Please break one of these paths by setting the `onUpdate` and `onDelete` to `NoAction`. (Implicit default `onUpdate`: `Cascade`)

第二个在 post 关系中

Error parsing attribute "@relation": When any of the records in model `User` is updated or deleted, the referential actions on the relations cascade to model `Comment` through multiple paths. Please break one of these paths by setting the `onUpdate` and `onDelete` to `NoAction`. (Implicit default `onUpdate`: `Cascade`)

此错误意味着通过更新 User 模型中记录的主键,更新将通过 writtenBy 关系在 CommentUser 之间级联一次,并通过 Post 模型从 post 关系再次级联,因为 PostComment 模型相关联。

解决方法是将 writtenBypost 关系字段中的 onUpdate 引用操作设置为 NoAction,或从 Post 模型中通过更改 author 关系中的操作来实现

model Comment {
id Int @id @default(autoincrement())
writtenById Int
postId Int
writtenBy User @relation(fields: [writtenById], references: [id])
writtenBy User @relation(fields: [writtenById], references: [id], onUpdate: NoAction)
post Post @relation(fields: [postId], references: [id])
}

model Comment {
id Int @id @default(autoincrement())
writtenById Int
postId Int
writtenBy User @relation(fields: [writtenById], references: [id])
post Post @relation(fields: [postId], references: [id])
post Post @relation(fields: [postId], references: [id], onUpdate: NoAction)
}

model Post {
id Int @id @default(autoincrement())
authorId Int
author User @relation(fields: [authorId], references: [id])
author User @relation(fields: [authorId], references: [id], onUpdate: NoAction)
comments Comment[]
}