When adding a new value type or numeric field a default value is added to the migration

[pomelofoundation]

When adding a new value type or numeric field a default value is added to the migration

[caleblloyd]

A non-nullable int in the DBMS must have a default value. If no default is specified, the default value is 0.

If you don't want a default value, you should define your property using the nullable int? type.

[YandyZaldivar]

In that case in my opinion there is an inconsistence. For example when the table is created the first time using non-nullable values the fields appears on the database with no default values. However if you add a migration with a new value (non-nullable) type, that field will be the only type with a default value. I think you must make this process homogenous at least. Or all value types gets the default value, even when creating the database or you remove the default values on migrations. I haven't taken a look to the behavior on SQL Server but in case of doubt you should follow that.