Migrations not changing on adding notNull
Is it intended behaviour for migrations not to detect and react to the addition of a
.notNull on some column ?
Currently, my use case is that have a first migration that has created the table, but now the second migraiton (adding the notNull) doesn't actually create a migration.1 Reply
I just upgraded the drizzle-kit package and this issue seems to have been resolved