It would be useful to have a built-in mechanism for squashing / compressing old migrations in rake-db, or at least an official guide describing a safe way to do it.
When the number of migration files grows large (e.g. 100+), it affects boot time, test suite speed, CI performance, and overall project maintainability.
See how others do it:
The AIs could probably do the hard work on merging operations, but the library at least needs to account for how to handle new gaps or the new non-0001 start or whatever approach is to be used.
It would be useful to have a built-in mechanism for squashing / compressing old migrations in rake-db, or at least an official guide describing a safe way to do it.
When the number of migration files grows large (e.g. 100+), it affects boot time, test suite speed, CI performance, and overall project maintainability.
See how others do it:
The AIs could probably do the hard work on merging operations, but the library at least needs to account for how to handle new gaps or the new non-0001 start or whatever approach is to be used.