Scenario
- Developing a migration
- Have a migration with a single ID for "source.keys"
- [... do some stuff ...]
- Update existing migration and add another value to source.keys
- Rollback migration data
- Import new configuration
- Run migration
Expected behavior
- Migration will make necessary changes to internal table schema to accommodate new requirements
Observed behavior
- Migration fails completely with unhandled SQL error
Column not found: 1054 Unknown column 'sourceid2' in 'field list'
Proposed resolution(s)
- Catch the exception and suggest a resolution. Possibilities:
- drop the migration table (and allow to be re-created with the correct sourceid columns)
- update existing table by adding or removing sourceidN column(s)
- update existing migration records with new key value(s))
- Provide tools to manually implement the suggested resolution
- Perform the resolution automatically