From def90564eff4adfeed0a8e511e4c201b040e9a5e Mon Sep 17 00:00:00 2001 From: Bader Nasser Al-Hashmi Date: Sat, 26 Aug 2017 21:05:59 +0400 Subject: [PATCH] Escape another < (#4113) --- aspnetcore/data/ef-mvc/complex-data-model.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/data/ef-mvc/complex-data-model.md b/aspnetcore/data/ef-mvc/complex-data-model.md index dc827ffd43..7fb31c7b4d 100644 --- a/aspnetcore/data/ef-mvc/complex-data-model.md +++ b/aspnetcore/data/ef-mvc/complex-data-model.md @@ -89,7 +89,7 @@ dotnet ef migrations add MaxLengthOnNames dotnet ef database update ``` -The `migrations add` command warns that data loss may occur, because the change makes the maximum length shorter for two columns. Migrations creates a file named *_MaxLengthOnNames.cs*. This file contains code in the `Up` method that will update the database to match the current data model. The `database update` command ran that code. +The `migrations add` command warns that data loss may occur, because the change makes the maximum length shorter for two columns. Migrations creates a file named *\_MaxLengthOnNames.cs*. This file contains code in the `Up` method that will update the database to match the current data model. The `database update` command ran that code. The timestamp prefixed to the migrations file name is used by Entity Framework to order the migrations. You can create multiple migrations before running the update-database command, and then all of the migrations are applied in the order in which they were created.