[Mono-bugs] [Bug 38824][Nor] Changed - we need our own TimeZone code

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by timo-mono at pokorra.de.

http://bugzilla.ximian.com/show_bug.cgi?id=38824

--- shadow/38824	2003-06-18 09:30:30.000000000 -0400
+++ shadow/38824.tmp.20064	2006-12-07 06:41:31.000000000 -0500
@@ -1,8 +1,8 @@
 Bug#: 38824
-Product: Mono/Runtime
+Product: Mono: Runtime
 Version: unspecified
 OS: unknown
 OS Details: 
 Status: REOPENED   
 Resolution: 
 Severity: Unknown
@@ -118,6 +118,32 @@
 
 ------- Additional Comments From lupus at ximian.com  2003-06-18 09:30 -------
 I added a workaround for the infinite loop in cvs.
 The complete fix is to use the timezone data from
 ftp://elsie.nci.nih.gov/pub/ directly, since libc doesn't provide the
 info we need for this function.
+
+------- Additional Comments From timo-mono at pokorra.de  2006-12-07 06:41 -------
+I am surprised that this bug is still around.
+
+This code surely shows the problem (running on CentOS/RHEL):
+
+for (int i = 1969; i < 1972; i ++)
+  Console.WriteLine(
+TimeZone.CurrentTimeZone.GetDaylightChanges(i).Start.ToString() + "
+" + TimeZone.CurrentTimeZone.GetDaylightChanges(i).End.ToString());				
+The result looks like this (running on CentOS4):
+1/1/0001 12:00:00 AM 1/1/0001 12:00:00 AM
+1/1/0001 12:00:00 AM 1/1/0001 12:00:00 AM
+10/31/1971 3:00:00 AM 1/1/0001 12:00:00 AM
+3/19/1972 2:00:00 AM 10/29/1972 3:00:00 AM
+
+Especially strange is the year 1971, which has a somewhat reasonable
+looking date for the start date, but of course it is wrong.
+
+I am suspecting that somehow this is also causing problems with
+remoting typed datasets with datetime columns, and the date is changed
+by one hour (e.g. Example: 4/28/1971 00:00:00 AM on the client side
+becomes 4/27/1971 11:00:00 PM on the server side); but going further
+into it, I realized that there is something else strange about this,
+especially when the server is in a different timezone than GMT. I will
+file another bug for that.