Example: A table "Car" exists, a Column "Owner" exsist. The schema requires to have non-null-owner (lets call the column a non-null-column). The schema updates incorreclty when the entity changes from non-null to nullable, the result is a nullable entity-column but a non-null database column.
Note: This task MUST be reduced to the change from non-null-column to nullable-column. The vice-versa (from nullable to non-null) must be NOT affected by this task because:
1. From nullable to non-null is a reduction of possible values leading to a broken database or run-time-problems.
2. From nullable to non-null does not work either but is not a bug!
So this task affects only the enhancement of value-range of columns from non-null to nullable.
Affected are also relations.
Comment if you need a unit-test