Can you elaborate a little more on "frozen CreateTable" and "so making changes to schema is actually possible"? Do you mean as opposed to making migrations? I'm trying to follow your reasoning while reviewing your code.

Can you elaborate a little more on "frozen CreateTable" and "so making changes to schema is actually possible"? Do you mean as opposed to making migrations? I'm trying to follow your reasoning while reviewing your code.

If you create a migration with operation CreateTable(model) and then remove a field, that migration will not create the field in a new database. Instead, it should create the model frozen in time, such that when its applied again - the field is created and then later dropped using a different migration. Without doing it this way, running migrations in test code isn't possible because the field you want to drop would not exist.

This is similar to how alembic migrations work - the list of fields, types, indexes etc are frozen when migration is created.

Ah gotcha, makes sense ... thanks for elaborating 👌