hard20 pts · first answer countsdeploymentsdatabases

Rollback blocked by a schema change

Release 2.0 renamed a column in the same deploy as the code change. It has a bug, but rolling back to 1.9 fails because 1.9 queries the old column name. How should future releases be done to keep rollback safe?

A.Never change the database schemaB.Run migrations only on weekendsC.Use expand and contract: add the new column, deploy code that works with both, backfill, and drop the old column in a later releaseD.Take a full database backup before each deploy and restore it to roll back

Discussion 0

Join free to post in the discussion.

Rollback blocked by a schema change

Discussion 0

Related questions