Missing/extra NOT NULL constraints

gitlab.com and schema.rb have differing ideas of the NOT NULL constraints on some columns. We can freely remove a NOT NULL constraint but adding one on a large table could be a problem. We need to decide which way to jump in each case individually.

List of columns with extra NOT NULL constraint in gitlab.com but not in schema.rb. We can remove the constraint in gitlab.com easily to bring it into sync:

• ...

List of columns with extra NOT NULL constraints in schema.rb but not in gitlab.com. Can we remove the constraint in schema.rb without causing application issues?

• ...