This question comes up occasionally, but I haven't seen a satisfactory answer.
A typical pattern is (row is a DataRow):
if (row["value"] != DBNull.Value)
{
someObject.Member = row["value"];
}
My first question is which is more efficient (I've flipped the condition):
row["value"] == DBNull.Value; // Or
row["value"] is DBNull; // Or
row["value"].GetType() == typeof(DBNull) // Or... any suggestions?
This indicates that .GetType() should be faster, but maybe the compiler knows a few tricks I don't?
Second question, is it worth caching the value of row["value"] or does the compiler optimize the indexer away anyway?
For example:
object valueHolder;
if (DBNull.Value == (valueHolder = row["value"])) {}
Notes:
- row["value"] exists.
- I don't know the column index of the column (hence the column name lookup).
- I'm asking specifically about checking for DBNull and then assignment (not about premature optimization, etc.).
I benchmarked a few scenarios (time in seconds, 10,000,000 trials):
row["value"] == DBNull.Value: 00:00:01.5478995
row["value"] is DBNull: 00:00:01.6306578
row["value"].GetType() == typeof(DBNull): 00:00:02.0138757
Object.ReferenceEquals has the same performance as "=="
The most interesting result? If you mismatch the name of the column by case (for example, "Value" instead of "value", it takes roughly ten times longer (for a string):
row["Value"] == DBNull.Value: 00:00:12.2792374
The moral of the story seems to be that if you can't look up a column by its index, then ensure that the column name you feed to the indexer matches the DataColumn's name exactly.
Caching the value also appears to be nearly twice as fast:
No Caching: 00:00:03.0996622
With Caching: 00:00:01.5659920
So the most efficient method seems to be:
object temp;
string variable;
if (DBNull.Value != (temp = row["value"]))
{
variable = temp.ToString();
}
I personally favour this syntax, which uses the explicit IsDbNull method exposed by
IDataRecord
, and caches the column index to avoid a duplicate string lookup.Expanded for readability, it goes something like:
Rewritten to fit on a single line for compactness in DAL code - note that in this example we're assigning
int bar = -1
ifrow["Bar"]
is null.The inline assignment can be confusing if you don't know it's there, but it keeps the entire operation on one line, which I think enhances readability when you're populating properties from multiple columns in one block of code.
if in a DataRow the row["fieldname"] isDbNull replace it with 0 otherwise get the decimal value:
I would use the following code in C# (VB.NET is not as simple).
The code assigns the value if it is not null/DBNull, otherwise it asigns the default which could be set to the LHS value allowing the compiler to ignore the assign.
There is the troublesome case where the object could be a string. The below extension method code handles all cases. Here's how you would use it:
use like this
I've done something similar with extension methods. Here's my code:
To use it, you would do something like