Repair: update checksums after migration #618
When using checksum validation, it is tedious to update the checksum when valid changes had to be made to run migrations. This can be done manually, but as the number of databases grow it promotes disabling this useful feature due to the manual work involved.
A few examples,
We'd want validation to fail by default to determine if the change is safe. For example developers have tried to get away with changing data type after a migration, e.g.
Being able to catch and accept or reject script changes is beneficial, but accepting them appears to currently require that we manually update the schema version table.
The text was updated successfully, but these errors were encountered: