Typed data sets don't support nullable types. They support nullable columns.
The typed data set generator creates non-nullable properties and related methods for handling null values. If you create a MyDate
column of type DateTime
and AllowDbNull
set to true
, the DataRow
subclass will implement a non-nullable DateTime
property named MyDate
, a SetMyDateNull()
method, and an IsMyDateNull()
method. This means that if you want to use a nullable type in your code, you have to do this:
DateTime? myDateTime = myRow.IsMyDateNull() ? null : (DateTime?) row.MyDate;
While this doesn't totally defeat the purpose of using typed data sets, it really sucks. It's frustrating that typed data sets implement nullable columns in a way that's less usable than the System.Data
extension methods, for instance.
Is particularly bad because typed data sets do use nullable types in some places - for instance, the Add<TableName>Row()
method for the table containing the nullable DateTime column described above will take a DateTime?
parameter.
Long ago, I asked about this issue on the MSDN forums, and ultimately the ADO project manager explained that nullable types were implemented at the same time as typed data sets, and his team didn't have time to fully integrate the two by .NET 2.0's ship date. And so far as I can tell, they haven't added new features to typed data sets since then.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…