S
Steve Landis
The business classes that we create for our applications have typically used
many value type properties like Int32, DateTime, Decimal, etc. that cannot
store null values. This is a problem, because we can't expose a property as
null and can't store null back to the database unless we use some ugly
workaround. We have started using the SqlTypes namespace to get around this
and this seems acceptable in c#, but not in VB.NET, which doesn't support
the operator overloading. We are curious what techniques others have used
to get around this issue? Do you allow nulls in the database? Do you
require entry of everything in the app? Do you use the SqlTypes? Do the
same issues arise in java?
many value type properties like Int32, DateTime, Decimal, etc. that cannot
store null values. This is a problem, because we can't expose a property as
null and can't store null back to the database unless we use some ugly
workaround. We have started using the SqlTypes namespace to get around this
and this seems acceptable in c#, but not in VB.NET, which doesn't support
the operator overloading. We are curious what techniques others have used
to get around this issue? Do you allow nulls in the database? Do you
require entry of everything in the app? Do you use the SqlTypes? Do the
same issues arise in java?