From 85ca093f01f3d2f612e62e8550822f53d949afb2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Erhan=20Alanku=C5=9F?= Date: Tue, 26 Apr 2022 17:59:19 +0300 Subject: [PATCH] Fix Typo --- entity-framework/core/modeling/data-seeding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/entity-framework/core/modeling/data-seeding.md b/entity-framework/core/modeling/data-seeding.md index 151ed05fe2..a4dc991684 100644 --- a/entity-framework/core/modeling/data-seeding.md +++ b/entity-framework/core/modeling/data-seeding.md @@ -45,7 +45,7 @@ Once the data has been added to the model, [migrations](xref:core/managing-schem > [!TIP] > If you need to apply migrations as part of an automated deployment you can [create a SQL script](xref:core/managing-schemas/migrations/applying#sql-scripts) that can be previewed before execution. -Alternatively, you can use `context.Database.EnsureCreated()` to create a new database containing the seed data, for example for a test database or when using the in-memory provider or any non-relation database. Note that if the database already exists, `EnsureCreated()` will neither update the schema nor seed data in the database. For relational databases you shouldn't call `EnsureCreated()` if you plan to use Migrations. +Alternatively, you can use `context.Database.EnsureCreated()` to create a new database containing the seed data, for example for a test database or when using the in-memory provider or any non-relational database. Note that if the database already exists, `EnsureCreated()` will neither update the schema nor seed data in the database. For relational databases you shouldn't call `EnsureCreated()` if you plan to use Migrations. ### Limitations of model seed data