medium10 pts · first answer countsreliabilitydeploymentdatabases
Rollback breaks after a migration
A release renamed a column and the new code uses it. The release has a bug, but rolling back breaks because old code needs the old column. What practice avoids this?
Discussion 0
Join free to post in the discussion.
Related questions
- Building SQL from user inputBackend Developer
- What atomicity guaranteesBackend Developer
- WHERE column = NULL finds nothingBackend Developer
- COUNT(*) versus COUNT(column)Backend Developer
- Column type for pricesBackend Developer
- Storing order times for two countriesBackend Developer
- Students and courses table designBackend Developer
- What a foreign key doesBackend Developer