Continuous Delivery with Docker and Jenkins

Dropping the old column from the database

The last step is to drop the old column from the database. This migration should be performed after the rollback period when we are sure we won't need to roll back before step 4.

The rollback period can be very long since we aren't using the column from the database anymore. This task can be treated as a cleanup task, so even though it's non-backwards-compatible, there is no associated risk.

Let's add the final migration, V5__Drop_result_column.sql:

alter table CALCULATIONdrop column RESULT;

After this step, we finally completed the column renaming procedure. Note that all we did was complicate the operation a little bit, in order to stretch it in time. This reduced the risk of backwards-incompatible ...