implementation-lokstra-create-migrations

To generate SQL migration files for multiple database schemas, create migrations within a dedicated directory and configure db pools, descriptions, and folder toggles using a migration.yaml file. The tool outputs auto-versioned .up.sql and .down.sql scripts for each schema change.

The lokstra CLI handles database migration versioning by automatically assigning ordered versions to generated up and down scripts. You apply changes with `lokstra migration up`, check state with `lokstra migration status`, and reverse changes using the corresponding down scripts.

Yes, you can manage migrations for separate database pools using a per-folder migration.yaml configuration file. This setup allows you to define and organize db pools, set custom descriptions, and enable or disable specific migration folders independently.

Before creating SQL migrations with the lokstra CLI, you need a designated migrations directory in your project and an optional migration.yaml configuration file to manage multi-database setups, db pools, descriptions, and folder activation states.

The best way to track and apply ordered schema changes across different databases is using auto-versioned up and down SQL scripts managed by a CLI. This ensures consistent, reversible migrations that track schema evolution over time across multiple db pools.