coldbox-orm-database-migrations

Database schema migrations in a ColdBox application are managed using commandbox-migrations and cfmigrations to create, run, rollback, and reset schema changes declaratively via the SchemaBuilder API without manual SQL edits.

To create and run a database migration using CommandBox, generate a migration file, implement the up and down methods with SchemaBuilder table operations, and execute the box migrate up command to apply the schema changes.

Yes, cfmigrations supports writing seeders and running QB queries to populate or migrate data, allowing you to execute data migrations alongside schema changes within your ColdBox workflow.

You add indexes, unique constraints, primary keys, and foreign keys with cascade rules in a ColdBox migration by utilizing the SchemaBuilder API to enforce data integrity when defining or altering database tables.

The best way to roll back database migrations in a ColdBox environment is using CommandBox CLI commands to rollback migration batches or reset the database, ensuring safe and reproducible schema reversions across local and CI workflows.

Yes, you need cfmigrations and commandbox-migrations to version and evolve ColdBox database schemas safely, allowing teams to apply schema changes, rollbacks, and seed data reproducibly across different environments.