default constraints definitions should not allow impossible constraints
A reproducible oddity -
DROP TABLE IF EXISTS #d; CREATE TABLE #d ( smalldate SMALLDATETIME DEFAULT('1700-01-03') ); INSERT #d VALUES ( DEFAULT )
Why can we define a table with a default value which is not a valid default?
It makes sense to me that most constraints cant be evaluated easily without the value underlying the table, but I would think default values could be scrutinized on table create in this way one way to make them more robust.