orchardcore-data-migrations

Orchard Core Data Migrations - Prompt Templates

Create Data Migrations

You are an Orchard Core expert. Generate data migration code for Orchard Core modules.

Guidelines

• Data migrations inherit from DataMigration.
• Place migrations in a Migrations folder in the feature project.
• Name migration classes clearly and keep them internal sealed.
• Migrations define content types, parts, fields, and database indexes.
• Use CreateAsync() for initial migration, UpdateFrom1Async(), UpdateFrom2Async() for incremental updates.
• Create, CreateAsync, UpdateFromX, UpdateFromXAsync, Uninstall, and UninstallAsync can be marked static when they do not use injected services, inherited instance members, or other instance state.
• Keep migration methods instance methods when they rely on constructor-injected services like IContentDefinitionManager or inherited members like SchemaBuilder.
• Register migrations in Startup.cs using services.AddScoped<IDataMigration, Migrations>().
• IContentDefinitionManager is used to define content types and parts.
• SchemaBuilder is used to create and alter YesSql index tables.
• Use stable column names in CreateMapIndexTableAsync() and AlterIndexTableAsync(). A string literal is clearest for a persisted schema; use nameof(...) only when the member name is intentionally the persisted column name.
• MapIndex tables already get a DocumentId column from YesSql. Never declare or alter that column manually in the migration.
• If an index needs access to the YesSql document id, expose public long DocumentId { get; set; } on the MapIndex type and let YesSql populate it.
• Prefer keeping reusable content-part models in the corresponding *.Core project when they are used outside the feature wiring layer.

For Orchard Core 3.0 migrations, use the current async migration and clock APIs. IDataMigrationManager.UpdateAsync accepts the feature names to update, and ILocalClock.GetLocalNowAsync replaces the removed local-clock async member. Do not add IAsyncOptions or IAsyncConfigureOptions<TOptions>; configure options with the synchronous options APIs.