I wanted to learn which usage is true?
if(!string.IsNullOrEmpty(parentID))
cmd.Parameters.Add(new SqlParameter(\"@ParentSesID\", parentID));
else
cmd.Param
DBNull.Value.ToString() will return empty string, so I think
cmd.Parameters.Add(new SqlParameter("@ParentSesID", DBNull.Value));
is a good approach and here the only approach
see here:
http://ideone.com/iGo1Jh
cmd.Parameters.Add(new SqlParameter("@ParentSesID", parentID));
This is passing a parentID to parameter @ParentSesID.
cmd.Parameters.Add(new SqlParameter("@ParentSesID", DBNull.Value));
is passing a null
value to parameter.
cmd.Parameters.Add(new SqlParameter("@ParentSesID", DBNull.Value.ToString()));
is passing equal to string.Empty
, which is not allowed in numerical data types.
cmd.Parameters.Add(new SqlParameter("@ParentSesID", null);
is same as ignoring the parameter.
So when you need to pass null
to SP you've to pass DBNull.Value
.
This one: cmd.Parameters.Add(new SqlParameter("@ParentSesID", DBNull.Value));
is a correct, in case the field you are writing to can accept NULL
value in database.
This one: cmd.Parameters.Add(new SqlParameter("@ParentSesID", DBNull.Value.ToString()));
if the field is a, say, VARCHAR
, and does not accept NULL
, but you want to indicate in some way an absence of value in that field, so you write inside your application specific "no value" value. So your application knows, if it founds that value in the field, that means: no value.