Embed Notice

@katafrakt @petecorey Fair points. Has someone formulated principles for how a schema migration should look for data migration to be separate?

Some schema migrations are just schema migrations and some data migrations are just data migrations, but often you're migrating the data so that it fits in the new schema.

I suppose it's like decoupling your frontend from your API or your API from your database schema, you'd have to have a concept of versioning, backwards compatibility, deprecation and breaking changes to your schema. So far I have gotten away with treating the API and schema as tightly coupled, the migration making sure they're always in lockstep.