Which database change best supports a release where old and new application versions temporarily overlap?

Published
  1. Immediately drop every field used by the old version.
  2. Assume the application artifact contains a complete live database copy.
  3. A staged expand-and-contract migration preserving compatibility during overlap.
  4. Require all writes to bypass validation during deployment.

Comments — 0