daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #22577 from dotnet/Rick-Anderson-patch-5 

Update complex-data-model.md
pull/22583/head
Rick Anderson 2021-06-20 15:49:23 -07:00 committed by GitHub
parent 54f69b2ff2 dfe20b124c
commit c796949511
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aspnetcore/data/ef-rp/complex-data-model.md
View File

@ -612,7 +612,7 @@ The next section fixes this error.
With the existing database, there are two approaches to changing the database: With the existing database, there are two approaches to changing the database:
* [Drop and re-create the database](#drop). Choose this section if when using SQLite. * [Drop and re-create the database](#drop). Choose this section when using SQLite.
* [Apply the migration to the existing database](#applyexisting). The instructions in this section work for SQL Server only, ***not for SQLite***. * [Apply the migration to the existing database](#applyexisting). The instructions in this section work for SQL Server only, ***not for SQLite***.
Either choice works for SQL Server. While the apply-migration method is more complex and time-consuming, it's the preferred approach for real-world, production environments. Either choice works for SQL Server. While the apply-migration method is more complex and time-consuming, it's the preferred approach for real-world, production environments.