Propose a feature similar to Laravel’s:
php artisan schema:dump --prune
Problem
As projects grow, the number of migration files increases significantly. This causes:
- slower setup for new environments
- longer migration execution times
- large migration history that is no longer necessary once schema stabilizes
Currently, Migo runs all migrations sequentially from the beginning.
Proposed Solution
Add a command that allows dumping the current database schema into a single SQL file and optionally pruning old migrations.
Example idea:
Propose a feature similar to Laravel’s:
php artisan schema:dump --prune
Problem
As projects grow, the number of migration files increases significantly. This causes:
Currently, Migo runs all migrations sequentially from the beginning.
Proposed Solution
Add a command that allows dumping the current database schema into a single SQL file and optionally pruning old migrations.
Example idea: