3 ms·
If you need to change something in your DB wouldn't you just have a job running in the background doing the migration and have your application code handle both
by superconduct123 2y ago
If you need to change something in your DB wouldn't you just have a job running in the background doing the migration and have your application code handle both cases when reading the DB (migrated/unmigrated)?
- TylerE 2y agoYou say "just" like you think that sort of thing is easy. Nothing could be farther from the truth. For one thing in many DBs certain (often nessesary) schema changes require a global write lock. It's much much easier to just show down for 15 minutes or less than spend hundreds of hours of engineering effort.