Nullable types are good, but only for types that are not nullable to begin with.
To make a type "nullable" append a question mark to the type, for example:
int? value = 5;
I would also recommend using the "as
" keyword instead of casting. You can only use the "as" keyword on nullable types, so make sure you're casting things that are already nullable (like strings) or you use nullable types as mentioned above. The reasoning for this is
- If a type is nullable, the "
as
" keyword returns null
if a value is DBNull
.
- It's ever-so-slightly faster than casting though only in certain cases. This on its own is never a good enough reason to use
as
, but coupled with the reason above it's useful.
I'd recommend doing something like this
DataRow row = ds.Tables[0].Rows[0];
string value = row as string;
In the case above, if row
comes back as DBNull
, then value
will become null
instead of throwing an exception. Be aware that if your DB query changes the columns/types being returned, using as
will cause your code to silently fail and make values simple null
instead of throwing the appropriate exception when incorrect data is returned so it is recommended that you have tests in place to validate your queries in other ways to ensure data integrity as your codebase evolves.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…