From c92196d0b1105d42f7559029d76899968c369ed9 Mon Sep 17 00:00:00 2001 From: Jef Date: Fri, 28 Apr 2023 20:52:58 +0200 Subject: [PATCH] Update many-to-many.md Replace the copy/paste with a meaningful sentence. --- entity-framework/core/modeling/relationships/many-to-many.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/entity-framework/core/modeling/relationships/many-to-many.md b/entity-framework/core/modeling/relationships/many-to-many.md index ea8a199a2d..d2a9c119f1 100644 --- a/entity-framework/core/modeling/relationships/many-to-many.md +++ b/entity-framework/core/modeling/relationships/many-to-many.md @@ -968,7 +968,7 @@ It's hard to imagine when it is useful to change this behavior, but it can be do --> [!code-csharp[ManyToManyWithNoCascadeDeleteConfig](../../../../samples/core/Modeling/Relationships/ManyToMany.cs?name=ManyToManyWithNoCascadeDeleteConfig)] -The result maps to a entity type schema with a timestamp set automatically when a row is inserted: +The database schema for the join table uses restricted delete behavior on the foreign key constraint: ```sql CREATE TABLE "PostTag" (