dealing with null and datetime

  • Thread starter Thread starter GaryDean
  • Start date Start date
G

GaryDean

Is there any good way in which to deal with null datetimes. For instance, I
can't seem to find anything that will pass a null value in a datetime
parameter to another method. Convert.dbnull will not work for instance.
Getting nulls back and forth between C# and SQL Server is always
problematic.
 
Is there any good way in which to deal with null datetimes. For instance,
I can't seem to find anything that will pass a null value in a datetime
parameter to another method. Convert.dbnull will not work for instance.
Getting nulls back and forth between C# and SQL Server is always
problematic.
Click to expand...

Use a nullable DateTime variable e.g.

DateTime? dtmNullable = null;
 
The problem is that DateTime is a value type. Value type can not be null.
I usually set January 1, 2000 (or any other date) as a null date and check
for it as if you would check for null.

George.
 
Sorry, I did not understand.
What is "nullable DateTime variable"?

And what is "DateTime? dtmNullable = null;"?

Can you please use it in a code maybe?

Thanks
George.
 
Sorry, I did not understand.
What is "nullable DateTime variable"?
Click to expand...

It is a DateTime variable which can be null.
And what is "DateTime? dtmNullable = null;"?
Click to expand...

It is a piece of C# code which instantiates a DateTime? variable and assigns
it a null value.
 
GaryDean said:
Is there any good way in which to deal with null datetimes. For instance, I
can't seem to find anything that will pass a null value in a datetime
parameter to another method. Convert.dbnull will not work for instance.
Getting nulls back and forth between C# and SQL Server is always
problematic.
Click to expand...

I wouldn't say that it's problematic, but you always have to write the
code for it.

When you get the value from the database, you first have to check if
it's a null value or not, before you can use the value.

Then you have to decide how you represent a null value in your code. A
null value from the database comes as a DBNull object into your code,
but that is mostly not a practical way to handle it in the code.

For a DateTime value you can use a nullable DateTime to handle the value:

DateTime? createdDate;
if (reader.IsDBNull(0)) {
createdDate = null;
} else {
createdDate = reader.GetDateTime(0);
}

To use the nullable value, you can check createdDate.HasValue to see if
there is a value, and createdDate.Value to get the value.
 
Ha,
I never knew that. I guess it's something new from .NET 2.0
It turned out that even int? is nullable int.

Thanks
George.
 
I never knew that. I guess it's something new from .NET 2.0
Click to expand...

That's right. Nullable datatypes and generics are the two new features in v2
which I have found the most useful...
It turned out that even int? is nullable int.
Click to expand...

That's also right.
 
Yes, that does help get null dates in and out of methods but it seems I
still have to do the following when taking it to a database.

if (DateAcknowledged == null)
{
cmd.Parameters.Add(new SqlParameter("@DateAcknowledged",
Convert.DBNull));
}
else
{
cmd.Parameters.Add(new SqlParameter("@DateAcknowledged",
DateAcknowledged));
}
 
Yes, that does help get null dates in and out of methods but it seems I
still have to do the following when taking it to a database.

if (DateAcknowledged == null)
{
cmd.Parameters.Add(new SqlParameter("@DateAcknowledged",
Convert.DBNull));
}
else
{
cmd.Parameters.Add(new SqlParameter("@DateAcknowledged",
DateAcknowledged));
}
Click to expand...

Correct.
 
Hi Gary,

yes, for those value types such as DateTime, int, the "Nullable" wrapper in
net 2.0 does be a good way to gracefully handle them like those reference
types(string , class objects...). However, when store into Database, you
still need to use DBNull (database specific null value) depend on the
Nullable instance's value.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi George,

The nullable wrapper does be a new feature of .net framework 2.0. And the
type? syntax is the C# syntax of using nullable type:

#Introduction to .Net Framework 2.0 Nullable Types
http://www.c-sharpcorner.com/UploadFile/mosessaur/nullabletypes0822200616413
5PM/nullabletypes.aspx

#Nullable Generic Structure
http://msdn2.microsoft.com/en-US/library/b3h38hb0(VS.80).aspx


Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top