How should you verify a schema change before release?
Measure existing data compatibility first. Order schema, writer and reader changes and preserve temporary compatibility with the old application. Plan recovery separately for deletion or transformation.
How to check it
- Check nullability, uniqueness and type assumptions against real records.
- Run the migration in isolation from the same starting schema.
- Test new and old readers, RLS policies and failure behavior.
Concrete example
Example: adding a required field can break an old writer. Add a compatible field, populate it and update the writer before enforcing the requirement after verification.
Avoid a false conclusion
A build or migration file does not prove data compatibility. Verify the actual target project and recovery boundaries separately.
Reference
VCT Editorial