See the question and my original answer on StackOverflow

The root cause of this is related to Object-relational impedance mismatch that CodeFluent Entities tries to fix.

  • On the database side you can define a nullable column for an integral type (this is not the case here, but the implications are the same)
  • On the .NET side, you define an integral type that cannot be null.

To fix the null impedance mismatch between those worlds, CodeFluent Entities defines a 'default value' concept on the .NET side. This follows the Sentinel value pattern.

The .NET side 'default value' for this property will be the .NET value that will be equivalent to null on the database side. By default, this value is 0 for a number (and -1 for an identity number).

So, when you send a 0 to the database, it's equivalent to sending a null. In the other way, if you store a null in the database, you'll get a 0 in the .NET property.

Note that unlike most ORMs - CodeFluent Entities is not an ORM but it does contain Object to Relational mapping technology - you will not get an error or an exception because you map nullable column to non nullable .NET types, it'll work like a charm, thanks to this default value concept. It's very practical because in the end, it allows us to map non nullable .NET types to nullable database columns. You don't have to use int? to declare a nullable int column (but you can if you want, CodeFluent Entities supports it).

In your case, since the column is not nullable, you logically get an error if you send a .NET 0.

So, you can choose to not use the 'default value' concept (like in meziantou's answer), or also you can define another default value (like defaultValue="-1" for example, or -2 for an identity column), but you'll still get an error if you send this new default value from .NET.