Jeff,

Let me make sure I've got the scenario right...it's a non-nullable bit column in your database, boolean in the Entity object?

>The entity then checks using .GetNonNullableDbValue() and crashes (casting the null to bool). I understand it SHOULD not be null, but it is. In most cases, this would be an error, but during data validation, it should just complain that the value is invalid and notify the user.

GetNonNullableDbValue contains the following code for

public static object GetNonNullableDbValue(object value, string dataType)
{
	return (value == DBNull.Value) ? mmType.GetEmptyDataValue(dataType) : value;
}

This code first checks to see if the value in the DataColumn is == DBNull.value. If it's null, this should evaluate to true, then the first condition in the ternary statement executes:

mmType.GetEmptyDataValue(dataType)

The GetEmptyDataValue() method contains a switch/case statement. For boolean values, the following case should execute:

case "System.Boolean":
{
	emptyValue = false;
	break;
}

This causes the GetEmptyDataValue() method to return false, which is subsequently returned from the GetNonNullableDbValue() method. This means the Entity object property's cast should work fine.

I'm wondering if things are working a bit different for PostGres than for SQL Server. If you can trace through your code and let me know what you're seeing, we can figure this out.

Best Regards,