Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

is DBNull vs. DBNull.Value.Equals()

Tags:

c#

dbnull

I am curious what are the pros and cons of using if(some_value is DBNull) versus if(DBNull.Value.Equals(some_value)). Personally i prefer if(some_value is DBNull) because i find it more readable. I know Microsoft recommends using if(DBNull.Value.Equals(some_value)) according to https://msdn.microsoft.com/en-us/library/system.dbnull%28v=vs.110%29.aspx.

like image 899
mobal Avatar asked Jul 14 '16 12:07

mobal


2 Answers

I would go for the DBNull.Value.Equals way.

Why?

Beacuse is will check the type against equality. It has to look up the left hand type and match that against the right hand type which it also has to look up. After that it can compare the types, most likely by checking for reference equality.

That would be less efficient than just checking reference equality, which DBNull.Value.Equals does. Since there is just once instance of DBNull.Value, this check is very accurate and very fast.

like image 60
Patrick Hofman Avatar answered Sep 20 '22 18:09

Patrick Hofman


value is DBNull actually checks whether value is an instance of the DBNull class, while value == DBNull.Value actually performs a reference comparison between value and the only instance of the singleton class DBNull.

The value is DBNull checks whether value is an instance of DBNull, which is only possible if value == DBNull.Value, since DBNull is a singleton.

The advantage of using value == DBNull.Value is that it does a direct reference comparison which will be more efficient than determining the types for the is DBNull comparison.

like image 25
Thorsten Dittmar Avatar answered Sep 20 '22 18:09

Thorsten Dittmar