hi Is there any difference between DateTime in c# and DateTime in SQL server?
views:
1595answers:
3
+11
A:
Precision and range (so, everything important ;-p)
From MSDN:
The DateTime value type represents dates and times with values ranging from 12:00:00 midnight, January 1, 0001 Anno Domini (Common Era) through 11:59:59 P.M., December 31, 9999 A.D. (C.E.)
Time values are measured in 100-nanosecond units called ticks, and a particular date is the number of ticks since 12:00 midnight, January 1, 0001 A.D. (C.E.) in the GregorianCalendar calenda
Date Range: January 1, 1753, through December 31, 9999
Accuracy: Rounded to increments of .000, .003, or .007 seconds
Marc Gravell
2009-07-25 09:05:50
excellent! I wanna to write a function in c# which gets a parameter of type string and convert it to datetime . I wanna to savethe return value of the function into DB. The function should take care of an empty string and in this case it should return null. But null can not be inserted. What 's wrong?
odiseh
2009-07-25 09:13:43
Probably simply that you need to use DBNull.Value in .NET code to represent database null.
Marc Gravell
2009-07-25 09:25:00
There's also the time zone aspect - even though DateTime doesn't have an associated time zone, it *can* know whether it's "local" or UTC.
Jon Skeet
2009-07-25 16:59:23
@Mark,@Jon : thank you very much
odiseh
2009-07-26 06:58:24
+7
A:
You can also use datetime2 of SQL Server 2008. The precision there is 100ns as well. In fact, it was introduced to match the .NET DateTime precision.
User
2009-07-25 09:14:55
+4
A:
Yes.
The C# equivalent of the SQL datetime type is SqlDateTime
So, define the SQL call (stored procs with parameter collection of course) to use SQLDateTime. On advantage is you can trap any overflow or out of range error building the command rather than at execution time from the database engine.
gbn
2009-07-25 09:20:23