Migrations: Default value not scaffolded for non nullable fields causing error

[suhasj]

Consider a database with tables and user data. Now if I change my model to add a property, say DateTime which is non nullable. Running migrations generates the necessary code but doesn't set a default value for the column. This causes to throw an ugly EF exception when applying the migrations that there is no default value set.

This seems to have worked in EF 6.0 where a default value was set for the column

[rowanmiller]

We didn't scaffold the code in EF6 but would add the value in later in the process. I think it would be better to scaffold it though.