Migrations not changing on adding notNull
Is it intended behaviour for migrations not to detect and react to the addition of a
Currently, my use case is that have a first migration that has created the table, but now the second migraiton (adding the
.notNullCurrently, my use case is that have a first migration that has created the table, but now the second migraiton (adding the
notNull