Releasing a new version of some code is usually easier than making structural changes to a database that's in active use. Yes, and on top of that, code-only ch

Releasing a new version of some code is usually easier than making structural changes to a database that's in active use. Yes, and on top of that, code-only changes need to be internally consistent to make sense but DB schema changes almost inevitably require some corresponding code change as well to be useful. Then you have all the fun of trying to deploy both changes while keeping everything in sync and working throughout.