Repeatable or Automatic Dependent Child Migrations

[cpursley]

Problem

Often times there are database objects (views, functions, etc) that are dependent on others. Migrating a parent means having to manually drop and update all children. This is a very tedious process fraught with potential to make major mistakes.

Solution

Something like Red Gate's Repeatable Migrations would get us half way there. But what would be really cool is a system that automatically checks for dependent objects (by querying the object's metadata), copies them into subsequent migrations and then adds the drops in front of the parent migrations. If not automated, at least some kind of walk-through in the Hasura UI that copies the dependent objects into new migration files (in the correct order) which can then be manually edited as needed.

Describe alternatives you've considered

Right now, it's all manual...