What are migrations in EF Core?

Migrations in Entity Framework Core (EF Core) are a set of commands and techniques used to manage changes to the database schema over time. They allow developers to evolve the database schema alongside the application code in a systematic way. Here’s a detailed explanation of what migrations are and how they work:

Purpose of Migrations

1. Schema Evolution: Migrations help track changes to the data model (entities and their relationships) in the application and apply those changes to the database schema. This is essential for keeping the database in sync with the code.

2. Version Control: Migrations provide a versioning system for the database schema, allowing you to apply, revert, or update changes in a controlled manner. This is similar to source control for your application code.

3. Data Loss Prevention: By managing changes carefully, migrations help prevent data loss that might occur if changes to the database were made manually without considering the existing data.

How Migrations Work

1. Creating a Migration: When you make changes to your data model (like adding or modifying entities), you create a migration using the EF Core CLI or Package Manager Console. This generates a class file that contains the code to apply the changes to the database schema.

   Example command:

   
   dotnet ef migrations add AddProductTable
   

2. Migration Class: Each migration class typically contains two methods:

   • Up(): Defines the operations to apply the migration, such as creating or altering tables, adding columns, etc.
   • Down(): Defines the operations to revert the migration, allowing you to roll back changes if necessary.

   Example migration class:

   
   public partial class AddProductTable : Migration
   {
       protected override void Up(MigrationBuilder migrationBuilder)
       {
           migrationBuilder.CreateTable(
               name: "Products",
               columns: table => new
               {
                   ProductId = table.Column<int>(nullable: false)
                       .Annotation("SqlServer:Identity", "1, 1"),
                   Name = table.Column<string>(nullable: false),
                   Price = table.Column<decimal>(nullable: false)
               },
               constraints: table =>
               {
                   table.PrimaryKey("PK_Products", x => x.ProductId);
               });
       }
   
       protected override void Down(MigrationBuilder migrationBuilder)
       {
           migrationBuilder.DropTable(
               name: "Products");
       }
   }
   

3. Applying Migrations: After creating a migration, you apply it to the database using the following command:

   
   dotnet ef database update
   

4. Managing Migrations: You can list all migrations, revert to a specific migration, or remove a migration if needed. EF Core keeps track of which migrations have been applied to the database in a special table called __EFMigrationsHistory.

Key Features of Migrations

• Automatic Generation: EF Core can automatically generate migration code based on the differences between the current model and the database schema using the command:

  
  dotnet ef migrations add MigrationName
  

• Custom Code: You can also write custom code in the migration methods if you need to perform more complex schema changes or data transformations.

• Data Seeding: Migrations can also include code to insert or modify seed data, which is useful for populating the database with initial data.

Summary

Migrations in EF Core are a powerful feature that simplifies the process of managing database schema changes over time. They provide a structured way to evolve the database in tandem with application code, support versioning of the schema, and help prevent data loss during updates. Using migrations ensures that developers can maintain a reliable and consistent database environment throughout the application's lifecycle.