From a051414707ec17dcffee9695a2041250e510bda8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Halil=20=C4=B0brahim=20Kalkan?= Date: Tue, 10 Mar 2020 13:27:32 +0300 Subject: [PATCH] Update Customizing-Application-Modules-Guide.md --- docs/en/Customizing-Application-Modules-Guide.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/en/Customizing-Application-Modules-Guide.md b/docs/en/Customizing-Application-Modules-Guide.md index c2f8795f6c..a992cf5e8e 100644 --- a/docs/en/Customizing-Application-Modules-Guide.md +++ b/docs/en/Customizing-Application-Modules-Guide.md @@ -80,4 +80,11 @@ See the [entities document](Entities.md) for more about the extra properties sys #### Creating a New Entity Maps to the Same Database Table/Collection -TODO \ No newline at end of file +While using the extra properties approach is easy to use and suitable for some scenarios, it has some drawbacks described in the [entities document](Entities.md). + +Another approach can be creating your own entity mapped to the same database table (or collection for a MongoDB database). + +`AppUser` entity in the [application startup template](Startup-Templates/Application.md) already implements this approach. [EF Core Migrations document](Entity-Framework-Core-Migrations.md) describes how to implement it and manage database migrations in such a case. It is also possible for MongoDB, while this time you won't deal with the database migration problems. + +#### Creating a New Entity with Its Own Database Table/Collection +