@senny No. I see no reason to switch the behaviour here.

For example, having `table1 (col1 integer null, col2 integer not null)`,
`insert into table1 (col1, col2) values (1, null);`
and
`insert into table1 (col1) values (1);`
results in same constraint error in the strict mode (and behaves differently in `non-strict` mode as I explained), but to me the former looks more explicit.