db-schema-management

EF Migrations automates schema change management by tracking entity modifications, generating migration files, and applying them to your database. Define entity changes, run `dotnet ef migrations add`, review the generated migration code, then execute `dotnet ef database update` to sync your database with the new schema.

Yes. EF Migrations supports CHECK constraints through `HasCheckConstraint()` in model configuration and PostgreSQL features like GIN/BRIN indexes and COMMENT annotations via `Fluent API`. For advanced features, integrate raw SQL within migration `Up()` and `Down()` methods.

The standard workflow is: modify your entity definitions, create a migration with `dotnet ef migrations add [MigrationName]`, verify the generated migration handles column additions or table creation correctly, then apply it with `dotnet ef database update`. Document changes in your database design files afterward.

Use a schema-document synchronization checklist after each migration: review generated migration files for accuracy, update your design documentation to reflect new tables, columns, and constraints, and verify PostgreSQL-specific properties are captured. This prevents drift between code and documentation.

Yes. EF Migrations allows manual SQL injection: use `migrationBuilder.Sql()` in the `Up()` method for custom operations and `migrationBuilder.Sql()` in `Down()` to reverse them. This enables complex transformations, data seeding, or PostgreSQL-specific DDL statements beyond EF's standard capabilities.

EF Migrations automates most operations: it generates migration files from entity changes and applies schema updates. However, you must manually review generated migrations for correctness, decide when to create snapshots, and ensure `Down()` methods properly reverse changes for rollback scenarios.