Adding the Not Knoll Constraint on a Strong Migration

Not in all actually is specifically addressed on strong migrations. It's the same problem whereifyou as when you hadd a check constraint without the not valid, it's going to check all the rows. That's going to also acquire an exclusive lock for that period of time. And depending on how big the table is um, in order to go through and evaluate all those rows, that lock would be in place for a long time,. Ok?