This website uses cookies to ensure you get the best experience.
Learn more.
Which database change best supports a release where old and new application versions temporarily overlap?
Published
- Immediately drop every field used by the old version.
- Assume the application artifact contains a complete live database copy.
- A staged expand-and-contract migration preserving compatibility during overlap.
- Require all writes to bypass validation during deployment.
Comments — 0
Sign in to comment